[BUG] Cowork scheduled task (create_trigger) does not attach connected MCP tools (Slack/Notion/Google Calendar) to the session it spawns — task fires on schedule, produces no output, eventually abandoned

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?

What's Wrong?

I asked Claude (in a Cowork chat session) to create a recurring scheduled task using the create_trigger tool. The task's job is to search Slack, read a Notion page, update that Notion page, and send a Slack DM — using the Slack, Notion, and Google Calendar connectors already connected and working in that same chat session.

The scheduled task fires reliably on its cron schedule. But every single firing — 3 manual test fires and 2 real scheduled weekday fires, 5 total — has produced zero output: no Slack message sent, no Notion page edit, nothing. The first few sat in ROUTINE_RUN_STATUS_PENDING for 10+ minutes each with no result. The most recent one eventually resolved to ROUTINE_RUN_STATUS_ABANDONED — timed out with no output and no error message, even though the automation's own instructions explicitly said "if anything fails, DM me to explain what went wrong" (which itself would require the missing Slack access).

What Should Happen?

A scheduled task created via create_trigger should have access to the same MCP connectors (Slack, Notion, Google Calendar, etc.) that were connected and available in the session that created it — or, at minimum, create_trigger should surface a clear error/warning at creation time if it cannot wire up the tools the prompt will need, rather than silently creating a trigger that will fire, do nothing, and eventually time out with no notification to the user.

Error Messages/Logs

No error was ever surfaced to the user or to the calling chat session. The only observable signal is the last_run.status field on the trigger, which progressed from absent → ROUTINE_RUN_STATUS_PENDING (for 10+ minutes) → ROUTINE_RUN_STATUS_ABANDONED, with the associated background session_id never producing any tool output visible from the parent session.

Affected trigger ID: trig_01KqnF9KUeE18kG2v3d3zQd4 Affected fire/session pairs:

fired 2026-08-27T10:43:40Z → session cse_01LKUmKdQJUEhc7NXQpkSDmz (manual test)
fired 2026-08-27T11:10:44Z → session cse_01AzUt3aSozfQwx1LZ2hLQ5u (manual test)
fired 2026-08-27T15:18:26Z → session cse_01VknkFcEKMo5TnvkDtT2xb1 (real scheduled run)
fired 2026-08-27T15:22:45Z → session cse_01NPpkdfyEkJrdzLHbEGkLd9 (manual test)
fired 2026-08-28T15:02:55Z → session cse_01GaTxSKmFLFNYDPh7mccMSZ (real scheduled run — final observed status: ROUTINE_RUN_STATUS_ABANDONED)

Steps to Reproduce

1. In a Cowork chat session, connect the Slack, Notion, and Google Calendar connectors (Settings → Connectors, or via the in-chat connector suggestion flow).
2. In the same session, ask Claude to create a recurring scheduled task (via create_trigger) whose prompt requires those connectors — e.g., "search Slack for X and update this Notion page."
3. Fire the trigger manually (fire_trigger) or wait for its scheduled cron time.
4. Observe: the trigger's last_run.status goes to ROUTINE_RUN_STATUS_PENDING and stays there for 10+ minutes, eventually resolving to ROUTINE_RUN_STATUS_ABANDONED. No Slack message is sent, no Notion edit is made, no error is surfaced to the user.
5. Compare the trigger's stored job_config (via list_triggers) against one created through a different path that has working connector access — the failing one is missing mcp_connections / session_context.allowed_tools wiring.

Claude Model

Sonnet (default)

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

Claude Code CLI version: 2.1.220

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_