Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.242 Home All releases ←olderv2.1.241 v2.1.243newer→
Claude Code v2.1.242

Cloud-hosted sessions now refuse local CLI options instead of quietly dropping them

You'll notice
Useful3 Signal3
Cloud Sessions not in their notes

Running with --cloud now tells you which local CLI options were ignored or refused, and why.

--cloud
What

When a run targets a cloud-hosted session (the agent runs in a cloud container rather than on your machine), each CLI option is now either forwarded, ignored with a visible notice, or refused with a reason. Refusals are grouped as bypass, tool_restriction, sdk_mcp, then unsupported. This applies on the --cloud path with no separate flag.

Details
  • Refused as bypass: --dangerously-skip-permissions, --permission-mode bypassPermissions, or a settings file whose defaultMode is bypassPermissions.
  • Refused as tool restrictions: --disallowed-tools, --tools (unless it resolves to just "default"), --disable-slash-commands, --safe-mode, --strict-mcp-config, and --settings/--managed-settings carrying deny or ask rules.
  • Refused as sdk_mcp: in-process SDK MCP servers declared in --mcp-config. Refused as unsupported: --json-schema and --bare.
  • --settings, --managed-settings and --mcp-config that only express preferences are ignored, with a notice telling you so.
Evidence

bypassPermissions is not available in a cloud-hosted session

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.242 →