{"version":"2.1.287","anchor":"cloud-remote-now-checked-together-with-attach-serve-an","canonical_anchor":"cloud-remote-now-checked-together-with-attach-serve-an","heading":"Claude Code recognises --cloud used with --attach-serve when loading settings","tier":"use","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/cloud-remote-now-checked-together-with-attach-serve-an","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Claude Code recognises `--cloud` used with `--attach-serve` when loading settings\n\nStarting with `--cloud` or `--remote` plus `--attach-serve`, and without `-p`, now changes how some settings sources are treated\n\n**Unclear.** It is not clear what Claude Code does with those settings sources in this case.\n\n**What**\n\nClaude Code now treats `--cloud`, `--remote` (its older name), `--cloud=` and `--remote=` as one group of flags. A flag is an option you add to the `claude` command. It now checks for the case where one of these is used together with `--attach-serve` and without `-p` or `--print`. In that case, settings sources other than your global settings file are handled differently.\n\n**Why**\n\nThis likely changes how settings are loaded when Claude Code is attached to a cloud session rather than doing the work on your machine.\n\n- Area: Cloud Sessions\n- Names: `--remote`, `--print`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 4\/5"}