What
The CLI now advertises dedicated subcommands for background sessions: attach, logs, stop (alias kill), respawn with --all, and rm.
Details
respawn --allrestarts every running background session.- All appear in help output on this build.
Usage
claude respawn --allEvidence
Restart every running background session
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
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
A small documentation edit on Self-hosted environments reference touched a line naming logs after this was published.
| `--host-config-snapshot <mode>` | `SELF_HOSTED_RUNNER_HOST_CONFIG_SNAPSHOT` | `disk` | Where the runner keeps the startup snapshot of the [host config directory](#environment-variable-only-settings) that it seeds each session from. `disk…self-hosted-environments-reference see the edit
Confirmed since
Anthropic's documentation has since written up respawn, on Claude Code changelog.
* Fixed a respawned in-process teammate picking up tools or a system prompt from a same-named agent file in a folder you have not trustedchangelog see the edit
Confirmed since
Anthropic's documentation has since written up stop, on Use Claude Science on a corporate network.
The `[network] ca_bundle` key in `config.toml` points at a PEM file whose certificates Claude Science adds to its default trust for sign-in, the Claude API, Anthropic-hosted connectors, update checks, and [cloud storage](/docs/claude-scien…claude-science/corporate-networks see the edit
Confirmed since
Anthropic's documentation has since written up logs, on Command line settings.
claude-science serve starts Claude Science and opens the web app in your browser at a single-use login link. Everyday use is that one command. The others manage the running program: they mint login links, report status, follow logs, instal…claude-science/command-line-settings see the edit
Added since
A small documentation edit on Customize Claude Tag touched a line naming attach after this was published.
The Configure page also shows the channel's resolved access. Its **Tools and access** tab lists the channel's resolved connections and any allowed domains. Members can see those lists but not change them there. The same tab's **Plugins** c…claude-tag/admins/customize see the edit
Confirmed since
Anthropic's documentation has since written up attach, on Give Claude access to your tools.
A Datadog API key, for example, makes the API reachable, and a Datadog plugin tells Claude which endpoints answer which questions. Sessions in covered channels pick up attached plugins automatically, with nothing to install or enable. Chan…claude-tag/admins/add-connections see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
A small documentation edit on Orchestrate subagents at scale with dynamic workflows touched a line naming stop after this was published.