Related to the claude -p / --print connector bugs fixed around v2.1.79–2.1.83 (#36587, #36716, #36060; #36833 was closed/locked as a duplicate). Those covered connectors being entirely unavailable in CLI print mode. This is a different surface and symptom the fix does not cover: scheduled cloud routines / cowork (headless cloud sessions).
Environment: a scheduled cloud routine (headless) with a claude.ai MCP connector attached, compared against the same connector + account in interactive Claude Code / web / desktop.
Expected: the routine session exposes the connector's full toolset (same as interactive), so a scheduled job can read and act via the connector.
Actual: the connector reports as Connected, but only a fixed ~6-tool subset is registered — and it's the wrong subset. The read/write tools the job needs (read channel history, search, post a message) are absent; only lower-value tools (reactions, emoji search, member list, file read) appear. The same connector exposes its full toolset in interactive Claude Code, web, and desktop. Only the headless routine runtime strips it — partial, silent tool filtering, not total unavailability.
Also: setting an explicit per-connector tool allow-list in the routine config had no effect — requested tools still didn't appear, suggesting that field is ignored/unsupported for routines.
Impact: there's no laptop-independent way to run a scheduled, connector-backed task — the cloud routine can't (wrong tools), and interactive sessions need a human online, defeating the point of scheduling.
Ask: expose the connector's full toolset to headless/routine sessions, matching interactive. If the reduced subset is intentional, please explain the rationale — documenting the reduced list alone does not help: if the required tools aren't present there's nothing to opt into, and the feature can't be used for connector-backed automation at all.
Related to the
claude -p/--printconnector bugs fixed around v2.1.79–2.1.83 (#36587, #36716, #36060; #36833 was closed/locked as a duplicate). Those covered connectors being entirely unavailable in CLI print mode. This is a different surface and symptom the fix does not cover: scheduled cloud routines / cowork (headless cloud sessions).Environment: a scheduled cloud routine (headless) with a claude.ai MCP connector attached, compared against the same connector + account in interactive Claude Code / web / desktop.
Expected: the routine session exposes the connector's full toolset (same as interactive), so a scheduled job can read and act via the connector.
Actual: the connector reports as Connected, but only a fixed ~6-tool subset is registered — and it's the wrong subset. The read/write tools the job needs (read channel history, search, post a message) are absent; only lower-value tools (reactions, emoji search, member list, file read) appear. The same connector exposes its full toolset in interactive Claude Code, web, and desktop. Only the headless routine runtime strips it — partial, silent tool filtering, not total unavailability.
Also: setting an explicit per-connector tool allow-list in the routine config had no effect — requested tools still didn't appear, suggesting that field is ignored/unsupported for routines.
Impact: there's no laptop-independent way to run a scheduled, connector-backed task — the cloud routine can't (wrong tools), and interactive sessions need a human online, defeating the point of scheduling.
Ask: expose the connector's full toolset to headless/routine sessions, matching interactive. If the reduced subset is intentional, please explain the rationale — documenting the reduced list alone does not help: if the required tools aren't present there's nothing to opt into, and the feature can't be used for connector-backed automation at all.