Preflight Checklist
What's Wrong?
When creating a new Cowork scheduled task that uses different MCP connectors than existing scheduled tasks, the MCP connectors of the already-existing scheduled tasks get disabled. The existing tasks then fail on their next run because their required connectors are no longer available.
This is related to but distinct from #36327 — that issue describes scheduled tasks not inheriting connected MCPs at all. This issue describes a specific trigger: creating a new scheduled task causes previously working MCP connectors to be disabled in other scheduled tasks.
What Should Happen?
Creating a new scheduled task should have no effect on the MCP connector state of existing scheduled tasks. Each scheduled task should persistently retain the connectors it was configured with, regardless of what other tasks are created or modified.
Error Messages/Logs
No explicit error is shown in the UI. The scheduled task silently fails or reports that the required MCP connector is not connected, even though it was previously configured and working.
Steps to Reproduce
- Create scheduled task A that uses MCP connector X. Verify it runs successfully with that connector.
- Create a new scheduled task B that uses a different MCP connector Y.
- Open scheduled task A and check its connectors — MCP connector X is now disabled.
- Run scheduled task A — it fails because connector X is no longer available.
Claude Model
Opus
Is this a regression?
I don't know
Last Working Version
No response
Claude Code Version
1.1.9493
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
This makes Cowork scheduled tasks unreliable in any multi-task setup where different tasks use different MCP connectors. The workaround is to manually re-enable the connectors for each affected task after creating a new one — but this is easy to miss and breaks automation.
Preflight Checklist
What's Wrong?
When creating a new Cowork scheduled task that uses different MCP connectors than existing scheduled tasks, the MCP connectors of the already-existing scheduled tasks get disabled. The existing tasks then fail on their next run because their required connectors are no longer available.
This is related to but distinct from #36327 — that issue describes scheduled tasks not inheriting connected MCPs at all. This issue describes a specific trigger: creating a new scheduled task causes previously working MCP connectors to be disabled in other scheduled tasks.
What Should Happen?
Creating a new scheduled task should have no effect on the MCP connector state of existing scheduled tasks. Each scheduled task should persistently retain the connectors it was configured with, regardless of what other tasks are created or modified.
Error Messages/Logs
No explicit error is shown in the UI. The scheduled task silently fails or reports that the required MCP connector is not connected, even though it was previously configured and working.Steps to Reproduce
Claude Model
Opus
Is this a regression?
I don't know
Last Working Version
No response
Claude Code Version
1.1.9493
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
This makes Cowork scheduled tasks unreliable in any multi-task setup where different tasks use different MCP connectors. The workaround is to manually re-enable the connectors for each affected task after creating a new one — but this is easy to miss and breaks automation.