Allow scheduled tasks to enable/disable connectors per run

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

In the Claude desktop app (Code tab), set_session_connector_enabled is blocked in unattended sessions (scheduled-task runs and remote-dispatched sessions). The error is: "This tool is unavailable in unattended sessions."
So any connector a scheduled task needs has to stay enabled by default. Its tool definitions then load into every session, including ones that never use it.

My setup: one custom connector exposes 113 tools, and it's only needed by two scheduled jobs. With it on, a new session starts at a ~104K-token baseline before I type anything.

Problem is, I have a lot of tools, and my context for every session is extremely high and untenable, but if I keep any of these tools off, then the scheduled jobs that depend on them don't work.
It's impossible for me to turn on and off the 100+ tools that I have and keep it so that they are available for sessions that I need them, but otherwise, for general sessions, keep them off.

Proposed Solution

Problem

In the Claude desktop app (Code tab), set_session_connector_enabled is blocked in unattended sessions (scheduled-task runs and remote-dispatched sessions). The error is: "This tool is unavailable in unattended sessions."

So any connector a scheduled task needs has to stay enabled by default. Its tool definitions then load into every session, including ones that never use it.

My setup: one custom connector exposes 113 tools, and it's only needed by two scheduled jobs. With it on, a new session starts at a ~104K-token baseline before I type anything.

Request

Either of these would solve it:

1. Per-task connectors: let a scheduled task declare the connectors it needs, and enable them for that run only, without changing the default for other sessions.
2. Session-scoped toggle: allow set_session_connector_enabled in unattended runs, scoped to that session only, so it doesn't change the default for new sessions.

Option 1 is cleaner. It would also fix a side effect of today's toggle: enabling a connector in one session changes the default for every new session.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_