Cloud-hosted sessions now refuse local CLI options instead of…

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.

Read from

Names in the bundle--cloud

Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Added since 11 Sep 2026 A small documentation edit on Environment variables touched a line naming --cloud after this was published. | `CCR_FORCE_BUNDLE` | Set to `1` to force [`claude --cloud`](/docs/en/claude-code-on-the-web#send-local-repositories-without-github) to bundle and upload your local repository instead of cloning from its remote | env-vars see the edit

Confirmed since 11 Sep 2026 Anthropic's documentation has since written up --cloud, on Use Claude Code on the web. `--cloud` works with a single repository at a time. The task runs in the cloud while you continue working locally. The older `--remote` spelling still works as a deprecated alias for `--cloud`. claude-code-on-the-web see the edit

How sure we are

One source agreesOne thing we can check says the same as this entry.

Anthropic's documentation agreesAnthropic's documentation has since written up --cloud, on Use Claude Code on the web.

See this entry in the whole of v2.1.242 →

The build it came inv2.1.242

24 Aug 2026 · 396 entries, this one is #139.

Use it now52
You'll notice190
Nothing to try yet65
Under the hood89

Either side of it

v2.1.241Older
v2.1.243Newer

Open the release →

Names in this entry

cli--cloud
With a task description, create a new cloud session. With a session ID (session_... or cse_...) or a claude.ai/code URL, queue a message into that existing session instead, with -p. See send a follow-up message.
cli--dangerously-skip-permissions
Skip permission prompts. Equivalent to --permission-mode bypassPermissions. See permission modes for what this does and does not skip. For sessions started with --bg, the mode persists when the supervisor restarts the session
cli--permission-mode
Begin in a specified permission mode. Accepts default, acceptEdits, plan, auto, dontAsk, bypassPermissions, or manual as an alias for default. The manual alias selects the permission mode the UI labels Manual and requires Claude Code v2.1.200 or later; claude --help lists it in place of default, and both values work. Overrides defaultMode from settings files. Without this flag or --dangerously-skip-permissions, a new session starts in the permission mode described in which permission mode a session starts in. For -p, that's default when nothing is configured
settingbypassPermissions
Peer-machine isolation prompts now survive bypass permissions mode and are never auto-approved.
settingdefaultMode
Saying yes to the auto-mode prompt now actually saves auto as your default permission mode.
cli--disallowed-tools
Deny rules. A bare tool name removes the matching tools from Claude's context: "Edit" removes Edit, "" removes every tool, and "mcp__" removes every MCP tool. A scoped rule such as Bash(rm *) leaves the tool available and denies only calls that match as written. A rule naming EndConversation can't remove it while any other tool remains
cli--tools
Restrict which built-in tools Claude can use. Use "" to disable all, "default" for the default set, or tool names like "Bash,Edit,Read". On macOS, Linux, and WSL, the default set leaves out Glob and Grep, as described under Glob tool behavior. If you name one of the task-tracking tools here, Claude Code also opts the session in. The flag doesn't affect MCP tools; to deny those too, use --disallowedTools "mcp__*". A list that omits EndConversation doesn't remove it; "" removes it only when no MCP tools remain
cli--disable-slash-commands
Disable all skills and commands for this session
cli--safe-mode
Start with all customizations disabled to troubleshoot a broken configuration: CLAUDE.md, skills, plugins, hooks, MCP servers, custom commands and agents, output styles, workflows, custom themes, custom keybindings, status line and file-suggestion commands, LSP servers, and auto memory do not load. Authentication, model selection, built-in tools, and permissions work normally, which differs from --bare. Managed settings policy still applies, including policy-configured hooks, status line, and file-suggestion commands; managed plugins, managed skills, managed CLAUDE.md, and policy-configured MCP servers do not. Useful for checking whether a customization is what triggers automatic model fallback. Sets CLAUDE_CODE_SAFE_MODE
cli--strict-mcp-config
Only use MCP servers from --mcp-config, ignoring all other MCP configurations. See Exclusive control with managed-mcp.json for what the flag does under a managed MCP file
cli--settings
Path to a settings JSON file or an inline JSON string. Values you set here override the same keys in your settings.json files for this session. Keys you omit keep their file-based values. The file must be a regular file no larger than 2 MiB. See settings precedence
cli--mcp-config
Load MCP servers from JSON files or strings (space-separated). When you pass this flag with -p, Claude Code waits for still-pending servers to connect before running the first turn, up to the MCP_TIMEOUT startup timeout, 30 seconds by default; a server with a cached tool list skips the wait and connects on first use. The wait requires Claude Code v2.1.221 or later
cli--bare
Minimal mode: skip auto-discovery of hooks, skills, custom commands, subagents, installed plugins, MCP servers, auto memory, and CLAUDE.md so scripted calls start faster. Skills in a directory you pass with --add-dir still load. Claude has access to Bash, file read, and file edit tools. Sets CLAUDE_CODE_SIMPLE. See bare mode

Is this right?