Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial
Home / Reference / CLI flags

--cloud

cli never mined documented JSON

A Claude Code CLI flag, read out of the shipped bundle. No mined inventory carries it: everything below comes from what this site has written about it.

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.

Anthropic's own wording. Read off CLI reference, captured 2026-09-26.

First seen — never in a mined build
Last seen — never in a mined build
Builds0 / 149on this box, as of v2.1.308
Written about v2.1.166 first named in a changelog, 5 Jun 2026

In the changelogs

99

Releases whose published page names --cloud.

  1. v2.1.305
    Groundwork for resuming a cloud session with --resume

    Code that would let --resume pick up a cloud session alongside --cloud is present but cannot be reached in this build

    found in this entry's text

  2. v2.1.305
    Cloud sessions can open a sign-in screen when sign-in fails

    If sign-in fails when starting a --cloud session, Claude Code can now show a sign-in screen and carry on instead of only printing an error

    found in this entry's text

  3. v2.1.304
    /login accepts an argument and drops its cloud-session workaround

    The cloud-session tip for /login is gone, and /login now reads an argument and reports when it does not recognise it

    found in this entry's text

  4. v2.1.304
    Clearer message when a folder can't be used for cloud sessions

    The message for a folder that can't be bound to cloud sessions now covers home folders, hidden folders and repositories rooted there

    found in this entry's text

  5. v2.1.304
    Sharing MCP servers with cloud sessions now has a "Not now" answer

    The prompt offering your MCP servers to claude --cloud sessions adds "Not now", which asks again once you add an MCP server

    found in this entry's text

  6. v2.1.302
    New and reworded messages for cloud sessions and missing start folders

    Claude Code now explains how to open another cloud session and says plainly when a server's start folder no longer exists

    found in this entry's text

  7. v2.1.299
    Internal rework of how --cloud sessions are started

    The code that starts cloud sessions with --cloud was reorganised, with no change you can see

    found in this entry's text

  8. v2.1.296
    Cloud session creation is prepared to limit built-in tools, but nothing is limited yet

    Creating a session with --remote can now pass a built-in tool restriction, though in this version no restriction is ever sent

    found in this entry's text

  9. v2.1.295
    The --cloud form is now suggested in one more case

    Claude Code now uses the --cloud form in its hint text when an environment query is present, not only when a pool is

    found in this entry's text

  10. v2.1.295
    --cloud without a description can take the task from your prompt

    Claude Code now accepts --cloud with no description in more cases, using the starting prompt as the task

    found in this entry's text

  11. v2.1.293
    Sending local hooks to cloud sessions now depends on an account setting

    Hooks from your computer are only offered to a claude --cloud session when the feature is switched on for your account

    found in this entry's text

  12. v2.1.292
    Clearer error when remote sign-in setup fails, plus a plugin publish name

    A failed sign-in setup with --remote now logs the real error, and a plugin_publish plugin operation name has been added

    found in this entry's text

  13. v2.1.290
    Exiting a cloud session now shows how to continue it with --cloud

    When you leave a cloud session, the hint now shows claude --cloud <id> instead of the local claude --resume command

    found in this entry's text

  14. v2.1.290
    Cloud sessions now say which local hooks they will not receive

    When work moves to a cloud session, Claude Code withholds hooks from files the cloud session could change and tells you which ones

    found in this entry's text

  15. v2.1.290
    Cloud sessions ask for hook consent first and word hook-change warnings differently

    Cloud sessions now ask for consent before recording the hooks they use, and the warnings about edited hooks are reworded

    found in this entry's text

  16. v2.1.288
    Errors for conflicting cloud session options can name a different option

    Errors about conflicting --cloud or --environment options no longer always name --environment or always start with Error:

    found in this entry's text

  17. v2.1.288
    Shorter reasons when a hook is not sent to a cloud session

    With claude --cloud, notices about hooks held back are shorter and give a cause, with a warning when a changed guard hook blocks tool calls

    found in this entry's text, named in this entry

  18. v2.1.287
    Claude Code recognises --cloud used with --attach-serve when loading settings

    Starting with --cloud or --remote plus --attach-serve, and without -p, now changes how some settings sources are treated

    found in this entry's text

  19. v2.1.287
    Hooks in cloud sessions start in an empty folder unless marked to run on your device

    In cloud sessions hooks start in an empty folder; mark one "cloud": "device" in your user settings to run it in the project

    found in this entry's text

  20. v2.1.287
    Shorter warnings about hooks in claude --cloud sessions

    Warnings about outdated, local-only or edited hooks in claude --cloud sessions are now shorter

    found in this entry's text

  21. v2.1.287
    CLAUDE.md nested loading and an --environment error message reworked

    The code that loads nested CLAUDE.md files was simplified, and the error for combining --environment with --cloud is now built in parts

    found in this entry's text

  22. v2.1.287
    Cloud hook error now tells you how to fix it with CLAUDE_CODE_TMPDIR

    When a cloud session cannot store a verified hook copy safely, the error now explains what is blocked and suggests setting CLAUDE_CODE_TMPDIR

    found in this entry's text

  23. v2.1.287
    --cloud stops early when it would need a keyboard it can't read

    If --cloud would open a session in your terminal but there is no keyboard to read from, Claude Code now exits with an error before creating it

    found in this entry's text

  24. v2.1.286
    Clearer wording on which permission rules claude --cloud sends

    The claude --cloud settings-sync text now says it sends your portable permission rules and shows on each launch whether they were sent

    found in this entry's text, named in this entry

  25. v2.1.285
    Directory sync for cloud sessions and its environment variables removed

    The directory-sync machinery for cloud sessions is gone, and its CLAUDE_CODE_DIR_SYNC_* and CLAUDE_CODE_DISABLE_DIR_SYNC variables no longer do anything

    found in this entry's text

  26. v2.1.285
    Starting a cloud session no longer offers to sync your folder

    Launching with --cloud no longer runs the folder sync offer, local-change check or upload planning, and a new warning covers failed look-ups

    found in this entry's text

  27. v2.1.284
    Cloud file sync can be paused from Anthropic's side without ending your session

    If Anthropic switches cloud file sync off, sync pauses for the session instead of ending it, and picks up again once it is back on

    found in this entry's text

  28. v2.1.284
    Cloud-session attach and folder sync get new remote switches

    Joining an existing cloud session, trusted-device enrollment and the folder sync offer can now be turned on by two new remote switches, off by default

    found in this entry's text

  29. v2.1.284
    Staying connected to a cloud session from --cloud can be switched on by a new remote setting

    Staying attached to a cloud session started with --cloud can now also be turned on remotely, and the offer to sync files hangs on its own switch

    found in this entry's text

  30. v2.1.284
    Creating a cloud session no longer treats upload-only folder sync consent differently

    claude --cloud no longer lets an upload-only folder sync consent block git directory sync

    found in this entry's text

  31. v2.1.284
    Cloud directory sync can now be switched off from Anthropic's side

    Directory sync for --cloud sessions now treats a specific server refusal as sync switched off by Anthropic and stops quietly

    found in this entry's text

  32. v2.1.284
    claude --cloud explains what uploads when some files were withheld from sync

    When a cloud session cannot start and files were withheld from sync, claude --cloud now explains what the no-sync fallback would upload

    found in this entry's text

  33. v2.1.284
    Cloud file sync signs files per device and explains when that fails

    Cloud file sync now signs synced files with a key for this computer, and stops with a clear message if that cannot be set up

    found in this entry's text

  34. v2.1.284
    Cloud folder sync now signs uploads from your device and can be switched off by Anthropic

    Folder sync for cloud sessions now signs uploads as the bound device, and stops with a message if this computer can't or Anthropic switches it off

    found in this entry's text

  35. v2.1.283
    Cloud file sync is turned off for organizations with limited data retention

    Organizations under zero or limited data retention no longer get local-to-cloud file sync in cloud sessions and now see a notice explaining why

    found in this entry's text

  36. v2.1.283
    Cloud sessions can ask to use the MCP servers on your machine

    Claude Code now asks before cloud sessions started with claude --cloud may call MCP servers configured on your machine

    found in this entry's text, named in this entry

  37. v2.1.283
    Cloud file sync explains when an organization's policy forbids it

    Organizations whose data retention policy forbids file sync now get a clear message, and cloud sessions continue without syncing

    found in this entry's text

  38. v2.1.283
    Cloud session folder sync handles full storage and unrestorable targets differently

    Folder sync for claude --cloud now keeps a turn in the cloud when its store is full and refuses a restore with no base to start from

    found in this entry's text

  39. v2.1.282
    Consent prompt before keeping an attached folder in sync with a cloud session

    Attaching a folder to a cloud session now asks whether to keep that folder in two-way sync with the session

    found in this entry's text

  40. v2.1.282
    claude --cloud refuses repositories that could steer file sync's git

    Cloud file sync now refuses repos with a symbolic link inside .git, or git settings forced by a settings file in the repo

    found in this entry's text

  41. v2.1.282
    Cloud file sync's skip message now names linked worktrees only on Windows and WSL

    The message for checkouts that cloud file sync skips now lists linked worktrees only on Windows or WSL, alongside submodules and separate git folders

    found in this entry's text

  42. v2.1.282
    Cloud directory sync tells Claude that your file wins where both created the same path

    In synced cloud sessions, Claude is now told your file replaces any file it made at the same path, and three "still waiting" notes were removed

    found in this entry's text

  43. v2.1.282
    Cloud uploads from a branch with no commits now check your staged files first

    Uploading to a cloud session from a branch with no commits now fails early unless the staged files are empty or match an existing branch

    found in this entry's text

  44. v2.1.282
    Cloud folder sync stops sooner when earlier saved work is refused

    When a cloud session restores its own earlier work and the server refuses or cannot serve it, sync now gives up at once

    found in this entry's text

  45. v2.1.281
    Hidden claude -p --cloud headless cloud-print path added, but compiled off

    Code for a headless claude -p --cloud run is added, but the switch that enables it returns false, so no one can use it in 2.1.281

    found in this entry's text

  46. v2.1.281
    Directory sync (claude --cloud): chained 'link' bundles, need/answer tracking and restoring an earlier environment

    Cloud directory sync can now send each turn as a chained link and restore an earlier environment's work

    found in this entry's text

  47. v2.1.281
    --cloud no longer refuses a plain string prompt

    Starting a --cloud session no longer refuses a prompt given as plain text

    found in this entry's text

  48. v2.1.281
    claude -p --cloud stays compiled off; a new check excludes stream-json and SDK-URL runs

    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

    found in this entry's text

  49. v2.1.281
    Error messages for the dark-launched --cloud print mode

    The not-yet-launched --cloud print mode has fixed messages for timeouts, failed starts, archived sessions, pending questions and Ctrl-C

    found in this entry's text

  50. v2.1.281
    Directory sync link-chain shipping on the cloud worker depends on a laptop env var

    --cloud directory sync can send each turn's changes as linked bundles, but only when the laptop sets CLAUDE_CODE_DIR_SYNC_CHAIN

    found in this entry's text

  51. v2.1.281
    Cloud session bundle-upload failure now explains why and how to upload without file sync

    Cloud sessions now say why the local upload failed and how to start with CLAUDE_CODE_DIR_SYNC_ENGINE=none instead

    found in this entry's text

  52. v2.1.281
    Cloud (--cloud) fallback messages refactored

    The hints shown when claude --cloud falls back now depend on the sync mode and say what gets uploaded and what stays local

    found in this entry's text

  53. v2.1.281
    Cloud file sync: new refusals for config-linked project directories, reworded protected-commit message, exit telemetry

    claude --cloud file sync now explains refusals for project folders tied to Claude Code's configuration and rewords the protected-commit refusal

    found in this entry's text

  54. v2.1.281
    File sync: skip reason for files blocked by host config, and a --cloud hint that says only commits upload

    File sync now reports files skipped because of host config, and the --cloud fallback hint says only commits will upload

    found in this entry's text

  55. v2.1.280
    New device-binding error messages for Claude account registration

    New error messages explain device-binding failures, including concrete steps to re-register a removed device

    found in this entry's text, named in this entry

  56. v2.1.280
    Windows-specific env vars added to the host-passthrough allowlist

    More environment variables, including Windows-specific ones, now pass through to Claude Code

    found in this entry's text

  57. v2.1.280
    Cloud directory sync gains a reread list parameter

    claude --cloud directory sync gains a new 'reread' parameter for its container-snapshot sync

    found in this entry's text

  58. v2.1.277
    Directory-sync install tracking reworked to fold/dedupe re-sent installs

    Directory-sync install tracking for claude --cloud now dedupes re-sent installs that haven't materially changed

    found in this entry's text

  59. v2.1.275
    New 'cloud_session_default' telemetry path and 'violin_wood_gate' flag for --remote session creation

    Cloud/remote session creation now tracks whether the session type was defaulted, with a new telemetry event

    found in this entry's text

  60. v2.1.268
    New artifact wake-subscription failure reason: session_device_bound

    New error explains why artifact wake subscriptions fail on desktop-bound cloud sessions

    found in this entry's text

  61. v2.1.268
    Remote-control bridge: distinguishes org-policy denial and logs it before exiting

    Remote Control now logs and distinguishes org-policy denials before exiting

    found in this entry's text

  62. v2.1.265
    New --attach-serve CLI flag to attach a headless client to an existing cloud session

    New --attach-serve flag connects a headless client to an already-running cloud session instead of starting a new one

    found in this entry's text

  63. v2.1.259
    '--cloud <session-id>' reattach picker referenced as upcoming

    Resume, continue and login inside a cloud session now point you at claude --cloud with a session id, and note a picker is not built yet.

    found in this entry's text, named in this entry

  64. v2.1.259
    Cloud device-hooks bridge gains a "muted" state

    The cloud device-hooks bridge gains a muted phase that unregisters from the cloud session and restores registration on unmute.

    found in this entry's text, named in this entry

  65. v2.1.248
    Cloud sessions are told which files a sync changed underneath them

    Cloud sessions are told which files a sync changed so Claude re-reads them before editing.

    named in this entry, found in this entry's text

  66. v2.1.248
    Cloud sessions consider the running process environment when offering hooks

    Cloud sessions include the running process environment when deciding which hooks this machine offers.

    found in this entry's text

  67. v2.1.247
    Cloud sessions can report which worker generation they are on

    Cloud sessions track which worker generation they're on and re-register only after a worker restart.

    named in this entry, found in this entry's text

  68. v2.1.247
    A saved "yes" for device hooks and cloud plugins is ignored if the session could have edited it

    A saved yes to forwarding hooks and plugins is ignored if the cloud session could have edited that file.

    found in this entry's text

  69. v2.1.247
    File sync is not offered when the repository layout is unsupported

    File sync is no longer offered for repository layouts it cannot actually handle.

    named in this entry, found in this entry's text

  70. v2.1.247
    Stricter vetting of hooks forwarded to a cloud session

    Hooks forwarded to a cloud session are vetted harder, and refused if their program lives somewhere the session can write.

    found in this entry's text

  71. v2.1.247
    Better explanation when a cloud checkout follows a branch change

    When your cloud checkout's branch moves, Claude is now told who moved it and whether its commits followed.

    named in this entry, found in this entry's text

  72. v2.1.246
    --no-home-settings replaced by --forward-home-settings <true|false>

    The hidden --no-home-settings flag becomes --forward-home-settings true or false, so you can force it on.

    found in this entry's text

  73. v2.1.246
    Cloud sessions wait for the first file upload before sending your message

    Cloud sessions hold your first message until your project files have actually uploaded.

    named in this entry, found in this entry's text

  74. v2.1.246
    Cloud sessions explain which of your hooks cannot be pinned

    Cloud sessions now tell you which of your hooks couldn't be pinned and were skipped.

    named in this entry, found in this entry's text

  75. v2.1.246
    Forwarding your home settings to a cloud session now records explicit consent

    Forwarding your home settings to a cloud session now records your consent separately from permission.

    named in this entry, found in this entry's text

  76. v2.1.246
    Cloud sessions started from your home directory cannot bind a device

    Starting a cloud session in your home directory now blocks device linking and tells you to use a project folder.

    named in this entry, found in this entry's text

  77. v2.1.242
    /cloud-plugins and a matching opt-in for sending this machine's settings to cloud sessions

    You now decide separately whether cloud sessions may use your plugins and your local settings.

    found in this entry's text

  78. v2.1.242
    --print with --cloud can message an existing cloud session

    You can now use --print with --cloud to message an existing cloud session.

    named in this entry, found in this entry's text

  79. v2.1.242
    Cloud-hosted sessions now refuse local CLI options instead of quietly dropping them

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

    named in this entry, found in this entry's text

  80. v2.1.242
    Cloud sessions report queued commands dropped by an interrupt

    Headless cloud clients now see a cancelled status for each queued command an interrupt dropped.

    named in this entry, found in this entry's text

  81. v2.1.242
    Consent screen explaining what forwarding your hooks to a cloud session means

    A consent screen explains what letting cloud sessions run your local hooks means.

    found in this entry's text

  82. v2.1.242
    Hooks running on your machine on behalf of a cloud session, switched off in this build

    Cloud sessions could trigger hooks that run on your own machine, but the path is hard-disabled.

    found in this entry's text

  83. v2.1.242
    A headless client for cloud sessions appears in the bundle

    A full headless client for driving cloud sessions over stream-json is in the bundle.

    found in this entry's text

  84. v2.1.239
    Command-line flag parsing rewritten around an explicit table of value-taking flags

    Flags that take values no longer swallow or drop their arguments, and -- is handled.

    found in this entry's text

  85. v2.1.238
    claude --cloud explains when your local changes cannot be uploaded

    claude --cloud now says why your local changes could not be uploaded and points you at --ref.

    named in this entry, found in this entry's text

  86. v2.1.236
    A wire format for forwarding your local hooks into a cloud session, with nothing sending it

    Your local hooks could be registered with a cloud session, but nothing sends the messages yet.

    named in this entry, found in this entry's text

  87. v2.1.232
    --project no longer starts a cloud session

    Passing --project alone won't start a cloud session; --ref and --on-branch now need --cloud or --environment.

    named in this entry, found in this entry's text

  88. v2.1.232
    Headless cloud sessions wired up but unreachable

    Running --cloud without a terminal is wired up but unreachable in this build.

    named in this entry, found in this entry's text

  89. v2.1.229
    Whitespace-only prompts are rejected for --cloud and --environment

    Whitespace-only prompts on --cloud and --environment are rejected instead of sent empty.

    named in this entry, found in this entry's text

  90. v2.1.224
    --teleport and --cloud show up in claude --help

    --teleport and --cloud now show up in claude --help.

    named in this entry, found in this entry's text

  91. v2.1.224
    Clearer error when --bg and --environment are combined

    Combining --bg and --environment now explains they are different backends and shows the right command.

    found in this entry's text

  92. v2.1.224
    Flag-conflict error names the flag you actually used

    The cloud-session conflict error now blames --environment, the flag you actually typed.

    found in this entry's text

  93. v2.1.224
    cloud CLI: piped stdin no longer silently overrides a task description

    Piped input no longer silently overrides a task description you passed to --cloud.

    named in this entry, found in this entry's text

  94. v2.1.221
    --cloud and --remote pre-parsing

    The --cloud and --remote flags no longer get special early handling and go straight to the normal parser.

    named in this entry, found in this entry's text

  95. v2.1.221
    --cloud reattach hint spelled out in the error

    The --cloud conflict error now spells out how to pass a session id and where to find one.

    named in this entry, found in this entry's text

  96. v2.1.181

    found in this entry's text

  97. v2.1.172
  98. v2.1.166
  99. v2.1.166

    found in this entry's text

First cited

25

The earliest release whose published evidence quoted --cloud was v2.1.166, 5 Jun 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.

ReleaseDateThe span that was quoted
v2.1.1665 Jun 2026Error: --cloud cannot be combined with
v2.1.2247 Aug 2026--cloud [description|session_id|url]
v2.1.2247 Aug 2026Error: --environment with --cloud <description> cannot also take piped stdin. Pass the task as the description, or drop --cloud.
v2.1.22912 Aug 2026Error: non-interactive --cloud <session_id> requires a prompt (positional or stdin).
v2.1.24224 Aug 2026"Don't send this machine's settings (CLAUDE.md, rules, output styles, preferences, portable permission rules) into the cloud session this launch creates or attaches to. Requires --cloud or --environment."
v2.1.24224 Aug 2026A host driving a cloud-hosted session through the headless `--cloud` client also receives 'cancelled' (and only that state) after its interrupt with cancel_queued:true

19 further spans in the ledger name it. The list above is the earliest first and stops at 6.

Presence across releases

0

The miner has never read a build containing this name. It is here because a changelog entry of ours names it, which is evidence that it existed and not evidence of which releases carried it. The inventory starts at v2.1.138 and everything older than that was never mined.

Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the CLI flag does. All CLI flags.

Feedback