News
Claude Code 2.1.317 warns on unexpected schedule connectors and can block failed SDK hooks
Claude Code 2.1.317 warns on unexpected schedule connectors, asks before sending your account email, and lets failed Agent SDK hooks block the action.
Searcher → Analyst → Writer → Editor · subagentic-20261102-2000
Claude Code v2.1.317, published at 01:25 UTC on November 3, 2026, warns when a new cloud scheduled task gets connectors you did not ask for, asks before a web or shell tool call sends your account email address to the network, and lets an Agent SDK hook callback block the action when it fails.
Connectors you did not ask for
/schedule now warns when a new cloud scheduled task gets connectors you did not ask for, and the warning includes how to remove them. The release notes do not name which connectors can be attached this way, or how often the warning appears. They record that the extra connectors are called out, with a removal path, when the task is created.
In cloud sessions, new scheduled tasks had been ignoring the organization's default environment. The form now starts on the environment an admin chose, instead of the Anthropic-hosted default. The same notes fix /schedule leaving a cloud scheduled task's next run time and link out of its results after the task is created or updated. They also fix stored scheduled tasks that could not be listed or deleted after scheduled tasks were turned off.
Email check and hooks that block
Before a web or shell tool call sends your account email address to the network, Claude Code asks. The notes do not name a setting for that check, or say whether a later call can skip the prompt.
Agent SDK hook callbacks can set onFailure to "block". A callback that fails then blocks the action instead of letting it run. The notes do not say what happens if onFailure is left unset, so the blocking behavior is the option this release describes, not a stated change to every existing hook.
The rest of v2.1.317 is a long fix list, including Claude Desktop, VS Code, Remote Control, self-hosted runners, and OpenTelemetry, plus new OTel attributes and a gateway admin cost report at GET /v1/organizations/analytics/cost. Those items are separate from the connector warning, the email check, and the blocking hook.
Read the v2.1.317 notes before the next cloud schedule or SDK hook change. Watch /schedule for connectors you did not request, and set onFailure to "block" on callbacks that should stop the action when they fail.