An entry is only as true as the day it was written.
Flags move on the server after a release ships. Anthropic's own notes land days later and their documentation later still. Sometimes an entry turns out to be wrong and gets corrected by hand. All of that is recorded against the entry it happened to, and this is the whole of it in the order it happened.
Nothing here replaces an entry. Every line links to the page its release published, still saying what that release said, because a correction is added and dated rather than swapped in.
| When | Entry | What happened |
|---|---|---|
v2.1.277backgrounding |
Documentation arrivedA small documentation edit on Tools reference touched a line naming backgrounding after this was published.
the line in the docsSetting [`CLAUDE_CODE_DISABLE_BACKGROUND_TASKS=1`](/docs/en/env-vars#variables) or running in [bare mode](/docs/en/headless#start-faster-with-bare-mode) disables auto-backgrounding along with the rest of the background task functionality, … |
|
v2.1.277backgrounding |
Documentation arrivedA small documentation edit on Tools reference touched a line naming backgrounding after this was published.
the line in the docsSetting [`CLAUDE_CODE_DISABLE_BACKGROUND_TASKS=1`](/docs/en/env-vars#variables) or running in [bare mode](/docs/en/headless#start-faster-with-bare-mode) disables auto-backgrounding along with the rest of the background task functionality, … |
|
v2.1.277backgrounding |
Documentation arrivedA small documentation edit on Tools reference touched a line naming backgrounding after this was published.
the line in the docsSetting [`CLAUDE_CODE_DISABLE_BACKGROUND_TASKS=1`](/docs/en/env-vars#variables) or running in [bare mode](/docs/en/headless#start-faster-with-bare-mode) disables auto-backgrounding along with the rest of the background task functionality, … |
|
v2.1.283claude --remote |
Documentation arrivedAnthropic's documentation has since written up claude --remote, on Continue local sessions from any device with Remote Control.
the line in the docs* **With `/remote-control`, `claude --remote-control`, or [auto-connect](#enable-remote-control-for-all-sessions)**: the session keeps running without Remote Control, and Claude Code archives it at claude.ai |
|
v2.1.285--remote |
Documentation arrivedAnthropic's documentation has since written up --remote, on Continue local sessions from any device with Remote Control.
the line in the docs* **With `/remote-control`, `claude --remote-control`, or [auto-connect](#enable-remote-control-for-all-sessions)**: the session keeps running without Remote Control, and Claude Code archives it at claude.ai |
|
v2.1.286--bare |
Documentation arrivedAnthropic's documentation has since written up --bare, on Run Claude Code programmatically.
the line in the docsBefore v2.1.286, these limits held only partly: an interactive `--bare` session connected the MCP servers that a normal session would, every `--bare` session sent system reminders, and background tasks stayed available. |
|
v2.1.286--mcp-config |
Documentation arrivedAnthropic's documentation has since written up --mcp-config, on Run Claude Code programmatically.
the line in the docs* **MCP servers**: only servers supplied on the command line connect, for example with `--mcp-config`. In an interactive session, Claude Code also skips the automatic IDE connection unless you pass `--ide`. |
|
v2.1.286/ultrareview |
Documentation arrivedA small documentation edit on Code Review touched a line naming /ultrareview after this was published.
the line in the docsTo run a cloud review from a script or CI job, use the [`claude ultrareview` subcommand](/docs/en/ultrareview#run-ultrareview-non-interactively), which waits for the findings and prints them to stdout. |
|
v2.1.286/ultrareview |
Documentation arrivedA small documentation edit on Code Review touched a line naming /ultrareview after this was published.
the line in the docsTo run a cloud review from a script or CI job, use the [`claude ultrareview` subcommand](/docs/en/ultrareview#run-ultrareview-non-interactively), which waits for the findings and prints them to stdout. |
|
v2.1.286/ultrareview |
Documentation arrivedA small documentation edit on Code Review touched a line naming /ultrareview after this was published.
the line in the docsTo run a cloud review from a script or CI job, use the [`claude ultrareview` subcommand](/docs/en/ultrareview#run-ultrareview-non-interactively), which waits for the findings and prints them to stdout. |
|
v2.1.286/ultrareview |
Documentation arrivedA small documentation edit on Code Review touched a line naming /ultrareview after this was published.
the line in the docsTo run a cloud review from a script or CI job, use the [`claude ultrareview` subcommand](/docs/en/ultrareview#run-ultrareview-non-interactively), which waits for the findings and prints them to stdout. |
|
v2.1.285/ultrareview |
Documentation arrivedA small documentation edit on Code Review touched a line naming /ultrareview after this was published.
the line in the docsTo run a cloud review from a script or CI job, use the [`claude ultrareview` subcommand](/docs/en/ultrareview#run-ultrareview-non-interactively), which waits for the findings and prints them to stdout. |
|
v2.1.277/ultrareview |
Documentation arrivedA small documentation edit on Code Review touched a line naming /ultrareview after this was published.
the line in the docsTo run a cloud review from a script or CI job, use the [`claude ultrareview` subcommand](/docs/en/ultrareview#run-ultrareview-non-interactively), which waits for the findings and prints them to stdout. |
|
v2.1.271/ultrareview |
Documentation arrivedA small documentation edit on Code Review touched a line naming /ultrareview after this was published.
the line in the docsTo run a cloud review from a script or CI job, use the [`claude ultrareview` subcommand](/docs/en/ultrareview#run-ultrareview-non-interactively), which waits for the findings and prints them to stdout. |
|
v2.1.261claude ultrareview |
Documentation arrivedA small documentation edit on Code Review touched a line naming claude ultrareview after this was published.
the line in the docsTo run a cloud review from a script or CI job, use the [`claude ultrareview` subcommand](/docs/en/ultrareview#run-ultrareview-non-interactively), which waits for the findings and prints them to stdout. |
|
v2.1.286/compact |
Documentation arrivedAnthropic's documentation has since written up /compact, on Orchestrate teams of Claude Code sessions.
the line in the docs* `/compact`, `/clear`, and `/rewind` act on the lead's conversation, so Claude Code asks you to confirm before running one of them from this view. |
|
v2.1.280SKILL.md |
Documentation arrivedA small documentation edit on Admin controls touched a line naming SKILL.md after this was published.
the line in the docsTo let members manage their own skills, host them in a GitHub repository. Put one `skills/<name>/SKILL.md` folder per skill in the repository and share the link. Members import them in the Claude Science app under **Settings** > **Skills**… |
|
v2.1.281TMPDIR |
Documentation arrivedA small documentation edit on Choose a sandbox environment touched a line naming TMPDIR after this was published.
the line in the docs* The directory where Claude Code writes runtime files. Unless you set [`CLAUDE_CODE_TMPDIR`](/docs/en/env-vars), that directory is: |
|
v2.1.281TMPDIR |
Documentation arrivedA small documentation edit on Choose a sandbox environment touched a line naming TMPDIR after this was published.
the line in the docs* The directory where Claude Code writes runtime files. Unless you set [`CLAUDE_CODE_TMPDIR`](/docs/en/env-vars), that directory is: |
|
v2.1.277TMPDIR |
Documentation arrivedA small documentation edit on Choose a sandbox environment touched a line naming TMPDIR after this was published.
the line in the docs* The directory where Claude Code writes runtime files. Unless you set [`CLAUDE_CODE_TMPDIR`](/docs/en/env-vars), that directory is: |
|
v2.1.277TMPDIR |
Documentation arrivedA small documentation edit on Choose a sandbox environment touched a line naming TMPDIR after this was published.
the line in the docs* The directory where Claude Code writes runtime files. Unless you set [`CLAUDE_CODE_TMPDIR`](/docs/en/env-vars), that directory is: |
|
v2.1.281ui.render |
Documentation arrivedA small documentation edit on Mods reference touched a line naming ui.render after this was published.
the line in the docsElements are the building blocks of a tree a `ui.render` hook returns, and you get them from `$.ui.resolve(e)`. [Build a tree from elements](/docs/en/plugins/mods/interface#build-a-tree-from-elements) shows the common ones with how the ter… |
|
v2.1.277ui.render |
Documentation arrivedA small documentation edit on Mods reference touched a line naming ui.render after this was published.
the line in the docsElements are the building blocks of a tree a `ui.render` hook returns, and you get them from `$.ui.resolve(e)`. [Build a tree from elements](/docs/en/plugins/mods/interface#build-a-tree-from-elements) shows the common ones with how the ter… |
|
v2.1.267ui.resolve |
Documentation arrivedA small documentation edit on Mods reference touched a line naming ui.resolve after this was published.
the line in the docsElements are the building blocks of a tree a `ui.render` hook returns, and you get them from `$.ui.resolve(e)`. [Build a tree from elements](/docs/en/plugins/mods/interface#build-a-tree-from-elements) shows the common ones with how the ter… |
|
v2.1.267ui.resolve |
Documentation arrivedA small documentation edit on Mods reference touched a line naming ui.resolve after this was published.
the line in the docsElements are the building blocks of a tree a `ui.render` hook returns, and you get them from `$.ui.resolve(e)`. [Build a tree from elements](/docs/en/plugins/mods/interface#build-a-tree-from-elements) shows the common ones with how the ter… |
|
v2.1.282/sandbox |
Documentation arrivedA small documentation edit on Mods overview touched a line naming /sandbox after this was published.
the line in the docsMods aren't sandboxed. If you turn on [sandboxing](/docs/en/sandboxing), the sandbox isolates the Bash commands Claude runs, and a process that a mod starts runs outside it. |
|
v2.1.282/sandbox |
Documentation arrivedA small documentation edit on Mods overview touched a line naming /sandbox after this was published.
the line in the docsMods aren't sandboxed. If you turn on [sandboxing](/docs/en/sandboxing), the sandbox isolates the Bash commands Claude runs, and a process that a mod starts runs outside it. |
|
v2.1.286cc-plugin-sec-default@builtin |
Documentation arrivedAnthropic's documentation has since written up cc-plugin-sec-default@builtin, on Manage mods for your organization.
the line in the docs"cc-plugin-sec-default@builtin": { |
|
v2.1.285cc-plugin-sec-default@builtin |
Documentation arrivedAnthropic's documentation has since written up cc-plugin-sec-default@builtin, on Manage mods for your organization.
the line in the docs"cc-plugin-sec-default@builtin": { |
|
v2.1.286bunfig.toml |
Documentation arrivedAnthropic's documentation has since written up bunfig.toml, on Plugin loading reference.
the line in the docs* **A separate install folder**: the package manager runs in a folder of its own that holds only a copy of the checked dependency list, so npm and Bun don't read the plugin's `.npmrc`, `.env`, or `bunfig.toml`. When the install succeeds, C… |
|
v2.1.286package-lock.json |
Documentation arrivedAnthropic's documentation has since written up package-lock.json, on Plugin loading reference.
the line in the docs| `npm-shrinkwrap.json` or `package-lock.json` | npm | |
|
v2.1.286bun.lockb |
Documentation arrivedAnthropic's documentation has since written up bun.lockb, on Plugin loading reference.
the line in the docs* **`bun.lockb`**: Bun's binary lockfile can't be checked. Ship a text `bun.lock` or an npm lockfile instead |
|
v2.1.286bun.lock |
Documentation arrivedAnthropic's documentation has since written up bun.lock, on Plugin loading reference.
the line in the docs| `bun.lock` | Bun | |
|
v2.1.281claude plugin test |
Documentation arrivedAnthropic's documentation has since written up claude plugin test, on Plugin commands reference.
the line in the docsclaude plugin test [directory] |
|
v2.1.280claude plugin test |
Documentation arrivedAnthropic's documentation has since written up claude plugin test, on Plugin commands reference.
the line in the docsclaude plugin test [directory] |
|
v2.1.271claude plugin test |
Documentation arrivedAnthropic's documentation has since written up claude plugin test, on Plugin commands reference.
the line in the docsclaude plugin test [directory] |
|
v2.1.284claude-sonnet-5-5 |
Documentation arrivedA small documentation edit on Agent SDK reference - Python touched a line naming claude-sonnet-5-5 after this was published.
the line in the docsOn the Claude API, the `context-1m-2025-08-07` beta is retired for Claude Sonnet 4.5 and Claude Sonnet 4. If you still pass it with either model, requests that exceed the standard 200K-token context window return an error, so remove it fro… |
|
v2.1.284claude-sonnet-5-5 |
Documentation arrivedA small documentation edit on Agent SDK reference - Python touched a line naming claude-sonnet-5-5 after this was published.
the line in the docsOn the Claude API, the `context-1m-2025-08-07` beta is retired for Claude Sonnet 4.5 and Claude Sonnet 4. If you still pass it with either model, requests that exceed the standard 200K-token context window return an error, so remove it fro… |
|
v2.1.284claude-sonnet-5-5 |
Documentation arrivedA small documentation edit on Agent SDK reference - Python touched a line naming claude-sonnet-5-5 after this was published.
the line in the docsOn the Claude API, the `context-1m-2025-08-07` beta is retired for Claude Sonnet 4.5 and Claude Sonnet 4. If you still pass it with either model, requests that exceed the standard 200K-token context window return an error, so remove it fro… |
|
v2.1.285claude-sonnet-5 |
Documentation arrivedA small documentation edit on Agent SDK reference - Python touched a line naming claude-sonnet-5 after this was published.
the line in the docsOn the Claude API, the `context-1m-2025-08-07` beta is retired for Claude Sonnet 4.5 and Claude Sonnet 4. If you still pass it with either model, requests that exceed the standard 200K-token context window return an error, so remove it fro… |
|
v2.1.283claude --remote |
Documentation arrivedA small documentation edit on Continue local sessions from any device with Remote Control touched a line naming claude --remote after this was published.
the line in the docsTo bring back a session you started with `claude --remote-control` or `/remote-control`, resume the conversation with `claude --continue` or `claude --resume`. For the permission mode that the resumed conversation starts in, see [permissio… |
|
v2.1.285--remote |
Documentation arrivedA small documentation edit on Continue local sessions from any device with Remote Control touched a line naming --remote after this was published.
the line in the docsTo bring back a session you started with `claude --remote-control` or `/remote-control`, resume the conversation with `claude --continue` or `claude --resume`. For the permission mode that the resumed conversation starts in, see [permissio… |
|
v2.1.283--remote |
Documentation arrivedA small documentation edit on Continue local sessions from any device with Remote Control touched a line naming --remote after this was published.
the line in the docsTo bring back a session you started with `claude --remote-control` or `/remote-control`, resume the conversation with `claude --continue` or `claude --resume`. For the permission mode that the resumed conversation starts in, see [permissio… |
|
v2.1.283--remote |
Documentation arrivedA small documentation edit on Continue local sessions from any device with Remote Control touched a line naming --remote after this was published.
the line in the docsTo bring back a session you started with `claude --remote-control` or `/remote-control`, resume the conversation with `claude --continue` or `claude --resume`. For the permission mode that the resumed conversation starts in, see [permissio… |
|
v2.1.282--remote |
Documentation arrivedA small documentation edit on Continue local sessions from any device with Remote Control touched a line naming --remote after this was published.
the line in the docsTo bring back a session you started with `claude --remote-control` or `/remote-control`, resume the conversation with `claude --continue` or `claude --resume`. For the permission mode that the resumed conversation starts in, see [permissio… |
|
v2.1.275--remote |
Documentation arrivedA small documentation edit on Continue local sessions from any device with Remote Control touched a line naming --remote after this was published.
the line in the docsTo bring back a session you started with `claude --remote-control` or `/remote-control`, resume the conversation with `claude --continue` or `claude --resume`. For the permission mode that the resumed conversation starts in, see [permissio… |
|
v2.1.286/clear |
Documentation arrivedAnthropic's documentation has since written up /clear, on Troubleshooting.
the line in the docsIf the error comes back after a `/clear`, run [`/context`](/docs/en/debug-your-config) and compare the `Messages` row with the rows above it: |
|
v2.1.275command.run |
Documentation arrivedAnthropic's documentation has since written up command.run, on Troubleshoot a mod.
the line in the docs### `no command.run hook answered it` |
|
v2.1.265command.run |
Documentation arrivedAnthropic's documentation has since written up command.run, on Troubleshoot a mod.
the line in the docs### `no command.run hook answered it` |
|
v2.1.265command.run |
Documentation arrivedAnthropic's documentation has since written up command.run, on Troubleshoot a mod.
the line in the docs### `no command.run hook answered it` |