{"version":"2.1.242","anchor":"cloud-hosted-sessions-now-refuse-local-cli-options-instead-o","canonical_anchor":"cloud-hosted-sessions-now-refuse-local-cli-options-instead-o","heading":"Cloud-hosted sessions now refuse local CLI options instead of quietly dropping them","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/cloud-hosted-sessions-now-refuse-local-cli-options-instead-o","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Cloud-hosted sessions now refuse local CLI options instead of quietly dropping them\n\nRunning with --cloud now tells you which local CLI options were ignored or refused, and why.\n\n**What**\n\nWhen 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.\n\n**Details**\n\n- Refused as bypass: `--dangerously-skip-permissions`, `--permission-mode bypassPermissions`, or a settings file whose defaultMode is bypassPermissions.\n- 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.\n- Refused as sdk_mcp: in-process SDK MCP servers declared in `--mcp-config`. Refused as unsupported: `--json-schema` and `--bare`.\n- `--settings`, `--managed-settings` and `--mcp-config` that only express preferences are ignored, with a notice telling you so.\n\n**Evidence**\n\n`bypassPermissions is not available in a cloud-hosted session`\n\n- Area: Cloud Sessions\n- Names: `--cloud`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}