{"version":"2.1.281","anchor":"claude-p-cloud-stays-compiled-off-a-new-check-excludes","canonical_anchor":"claude-p-cloud-stays-compiled-off-a-new-check-excludes","heading":"claude -p --cloud stays compiled off; a new check excludes stream-json and SDK-URL runs","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/claude-p-cloud-stays-compiled-off-a-new-check-excludes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### `claude -p --cloud` stays compiled off; a new check excludes stream-json and SDK-URL runs\n\n`claude -p --cloud` stays switched off in this build, and a new check would keep it away from stream-json output and SDK-URL runs\n\n**What**\n\nThere is a new check that decides whether `--cloud` can run in print mode. `--cloud` sends a task to a cloud session, and print mode is `-p`, where Claude Code answers once and exits instead of opening its interactive screen. The check allows print mode only when every one of these is true:\n\n- `-p` (print) is set\n\n- the run is not an init-only run\n\n- no SDK URL is set, meaning Claude Code is not being driven by another program over a connection\n\n- the output format is not `stream-json`\n\nThe switch around this check is hard-coded to false in this build, so the whole cloud print path stays off. Nothing changes for you in this version.\n\n**Why**\n\nThis shows the limits cloud print is expected to have if it is turned on: it would work for plain `-p` runs but not for runs that stream JSON output or are controlled through an SDK URL."}