[BUG] Cowork ECONNRESET on macOS - Unable to connect to API (Max plan)
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report
- [x] I am using the latest version of Claude Desktop
Environment
- Device: Mac Mini
- macOS version: Tahoe 26.3
- Claude Desktop: Latest version 1.1.4498 (24f768)
- Subscription: Max plan
- Chip: M4
What's Wrong?
Cowork consistently fails with "API Error: Unable to connect to API (ECONNRESET)" on every task. Regular Chat mode works perfectly. Only Cowork is affected.
Steps to Reproduce
- Open Claude Desktop (latest version, Max plan)
- Switch to Cowork tab
- Select a folder and start any task (e.g., "How many screenshots are inside this folder?")
- Task shows "Working on it..." for ~5 minutes
- Fails with: "API Error: Unable to connect to API (ECONNRESET)"
Expected Behavior
Cowork should connect to the API and complete the task.
Troubleshooting Already Attempted
- Confirmed host can reach API:
curl -I https://api.anthropic.comreturns HTTP/2 404 (cf-ray: 9d506213eea15989-DEL) ✅ - No VPN or proxy active
- Deleted local-agent-mode-sessions folder
- Cleared cache and restarted
- Restarted Mac
- Reinstalled/updated Claude Desktop
- Regular Chat mode works perfectly — only Cowork is broken
Additional Context
This has been happening since I subscribed to Max. I have never been able to use Cowork successfully.
What Should Happen?
Cowork should start successfully, connect to the Claude API, and complete the task. The task should return results within seconds, the same way regular Chat mode works without any issues.
<img width="1226" height="953" alt="Image" src="https://github.com/user-attachments/assets/f2e49e38-8c5c-4733-b456-4b16065a2b53" />
Error Messages/Logs
API Error: Unable to connect to API (ECONNRESET)
Steps to Reproduce
Enter this:
1. Open Claude Desktop (latest version) on macOS Mac Mini
2. Log in with Max plan subscription
3. Switch to the "Cowork" tab
4. Click "Work in a Folder" and select any local folder
5. Type a simple task like "How many screenshots are inside this folder?"
6. Press Enter
7. Cowork shows "Working on it..." with spinning indicator
8. Wait ~5 minutes
9. Task fails with: "API Error: Unable to connect to API (ECONNRESET)"
10. Try again with a new task — same result every time
Note: Regular Chat mode works perfectly on the same machine, same network, same session. Only Cowork is affected. Host can reach API confirmed via:
curl -I https://api.anthropic.com → HTTP/2 404 (success, cf-ray: 9d506213eea15989-DEL)
Claude Model
Sonnet (default)
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
Claude 1.1.4498 (24f768) 2026-02-26T19:47:09.000Z
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_
18 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Same problem
Same problem
same problem
Same problem
Same problem
Same Problem
Same Problem
same problem
Same problem
Same problem
Same problem
I have updated the app and no longer have this error. 🚀
Claude 1.1.6679 (f8f4ff) 2026-03-13T18:26:03.000Z
Hi Jamilnyc, I found my version is '2.1.84 (Claude Code)', why the begging number of your version is '1'?
@emmett2020 This issue is about Claude Cowork, the desktop application. My version of the desktop application is
Claude 1.1.6679 (f8f4ff) 2026-03-13T18:26:03.000Z. I can see this by going to the menu: Claude > About Claude.<img width="308" height="351" alt="Image" src="https://github.com/user-attachments/assets/c80a3c03-7597-4c3b-9db5-c14a6ac2cadb" />
This is different from Claude Code, the CLI application. For that I use
claude --versionand I have2.1.86 (Claude Code).Got it, thank you!
Hey folks, we believe this is fixed in 1.1.9134
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.