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.257/clear |
Documentation arrivedAnthropic's documentation has since written up /clear, on Hooks reference.
the line in the docs* **Later in a running session**: after `/clear` or a compaction, `SessionStart` fires again with the servers already available, and its `mcp_tool` hooks run. |
|
v2.1.246/clear |
Documentation arrivedAnthropic's documentation has since written up /clear, on Hooks reference.
the line in the docs* **Later in a running session**: after `/clear` or a compaction, `SessionStart` fires again with the servers already available, and its `mcp_tool` hooks run. |
|
v2.1.247UserPromptSubmit |
Documentation arrivedAnthropic's documentation has since written up UserPromptSubmit, on Hooks reference.
the line in the docs* per turn: `UserPromptSubmit`, `Stop`, and `StopFailure` |
|
v2.1.267open |
Documentation arrivedA small documentation edit on Fullscreen rendering touched a line naming open after this was published.
the line in the docsTo adjust scroll speed interactively, run `/scroll-speed`. The dialog shows a ruler you can scroll while it is open so you can feel the change immediately. Press `←` and `→` to adjust the speed, `r` to reset to the auto-detected default, a… |
|
v2.1.260interactive |
Documentation arrivedA small documentation edit on Fullscreen rendering touched a line naming interactive after this was published.
the line in the docsTo adjust scroll speed interactively, run `/scroll-speed`. The dialog shows a ruler you can scroll while it is open so you can feel the change immediately. Press `←` and `→` to adjust the speed, `r` to reset to the auto-detected default, a… |
|
v2.1.248/loop |
Documentation arrivedAnthropic's documentation has since written up /loop, on Schedule recurring tasks in Claude Code Desktop.
the line in the docs| | [Cloud](/docs/en/routines) | [Desktop](/docs/en/desktop-scheduled-tasks) | [`/loop`](/docs/en/scheduled-tasks) | |
|
v2.1.248/loop |
Documentation arrivedAnthropic's documentation has since written up /loop, on Schedule recurring tasks in Claude Code Desktop.
the line in the docs| | [Cloud](/docs/en/routines) | [Desktop](/docs/en/desktop-scheduled-tasks) | [`/loop`](/docs/en/scheduled-tasks) | |
|
v2.1.248/loop |
Documentation arrivedAnthropic's documentation has since written up /loop, on Schedule recurring tasks in Claude Code Desktop.
the line in the docs| | [Cloud](/docs/en/routines) | [Desktop](/docs/en/desktop-scheduled-tasks) | [`/loop`](/docs/en/scheduled-tasks) | |
|
v2.1.248/loop |
Documentation arrivedAnthropic's documentation has since written up /loop, on Schedule recurring tasks in Claude Code Desktop.
the line in the docs| | [Cloud](/docs/en/routines) | [Desktop](/docs/en/desktop-scheduled-tasks) | [`/loop`](/docs/en/scheduled-tasks) | |
|
v2.1.246/schedule |
Documentation arrivedAnthropic's documentation has since written up /schedule, on Schedule recurring tasks in Claude Code Desktop.
the line in the docs| | [Cloud](/docs/en/routines) | [Desktop](/docs/en/desktop-scheduled-tasks) | [`/loop`](/docs/en/scheduled-tasks) | |
|
v2.1.238/schedule |
Documentation arrivedAnthropic's documentation has since written up /schedule, on Schedule recurring tasks in Claude Code Desktop.
the line in the docs| | [Cloud](/docs/en/routines) | [Desktop](/docs/en/desktop-scheduled-tasks) | [`/loop`](/docs/en/scheduled-tasks) | |
|
v2.1.267hover |
Documentation arrivedAnthropic's documentation has since written up hover, on Desktop application.
the line in the docs* **Edit or archive one of your own environments**: hover over it and click the gear icon |
|
v2.1.267hover |
Documentation arrivedAnthropic's documentation has since written up hover, on Desktop application.
the line in the docs* **Edit or archive one of your own environments**: hover over it and click the gear icon |
|
v2.1.267Client |
Documentation arrivedA small documentation edit on Claude apps gateway deployment and operations touched a line naming Client after this was published.
the line in the docsSee [where each mechanism stores the policy](/docs/en/managed-settings#where-each-mechanism-stores-the-policy) for the file paths, and [Client-side managed settings](/docs/en/claude-apps-gateway-config#client-side-managed-settings) for the… |
|
v2.1.248CLAUDE_CODE_ENABLE_TELEMETRY |
Documentation arrivedAnthropic's documentation has since written up CLAUDE_CODE_ENABLE_TELEMETRY, on Claude apps gateway configuration.
the line in the docs* If it doesn't, also set `CLAUDE_CODE_ENABLE_TELEMETRY=1`, the `OTEL_*_EXPORTER` selectors, and `OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf`. |
|
v2.1.246managed-settings.json |
Documentation arrivedAnthropic's documentation has since written up managed-settings.json, on Claude apps gateway configuration.
the line in the docs* The endpoint comes from the gateway itself. If you set the same variable in an MDM profile or a local `managed-settings.json`, exports stay on the relay. |
|
v2.1.257CLAUDE_CODE_ENHANCED_TELEMETRY_BETA |
Documentation arrivedAnthropic's documentation has since written up CLAUDE_CODE_ENHANCED_TELEMETRY_BETA, on Claude apps gateway configuration.
the line in the docs[Traces](/docs/en/monitoring-usage#traces-beta) also require `CLAUDE_CODE_ENHANCED_TELEMETRY_BETA=1` on each client. Set it in a managed policy's `env` block, since the gateway doesn't push it. Developers approve it in the same [security a… |
|
v2.1.265OTEL_TRACES_EXPORTER |
Documentation arrivedAnthropic's documentation has since written up OTEL_TRACES_EXPORTER, on Claude apps gateway configuration.
the line in the docs* `OTEL_METRICS_EXPORTER`, `OTEL_LOGS_EXPORTER`, and `OTEL_TRACES_EXPORTER`, each set to `otlp` if at least one `forward_to` destination enables that signal and to `none` otherwise |
|
v2.1.265OTEL_LOGS_EXPORTER |
Documentation arrivedAnthropic's documentation has since written up OTEL_LOGS_EXPORTER, on Claude apps gateway configuration.
the line in the docs* `OTEL_METRICS_EXPORTER`, `OTEL_LOGS_EXPORTER`, and `OTEL_TRACES_EXPORTER`, each set to `otlp` if at least one `forward_to` destination enables that signal and to `none` otherwise |
|
v2.1.265OTEL_METRICS_EXPORTER |
Documentation arrivedAnthropic's documentation has since written up OTEL_METRICS_EXPORTER, on Claude apps gateway configuration.
the line in the docs* `OTEL_METRICS_EXPORTER`, `OTEL_LOGS_EXPORTER`, and `OTEL_TRACES_EXPORTER`, each set to `otlp` if at least one `forward_to` destination enables that signal and to `none` otherwise |
|
v2.1.265user.groups |
Documentation arrivedAnthropic's documentation has since written up user.groups, on Claude apps gateway configuration.
the line in the docs[Claude Desktop](#claude-desktop-overlay) and Cowork sessions signed in through the gateway stamp their telemetry with `user.email` and `user.groups` alongside `enduser.id`, so you can cover terminal, Desktop, and Cowork usage with one que… |
|
v2.1.265user.groups |
Documentation arrivedAnthropic's documentation has since written up user.groups, on Claude apps gateway configuration.
the line in the docs[Claude Desktop](#claude-desktop-overlay) and Cowork sessions signed in through the gateway stamp their telemetry with `user.email` and `user.groups` alongside `enduser.id`, so you can cover terminal, Desktop, and Cowork usage with one que… |
|
v2.1.257Monitor |
Documentation arrivedAnthropic's documentation has since written up Monitor, on Claude apps gateway configuration.
the line in the docsThe CLI sends metrics, logs, and, when enabled, traces to the gateway, which relays them verbatim to each configured destination. The exports use OpenTelemetry Protocol (OTLP) over HTTP. To skip the relay and have sessions export straight … |
|
v2.1.257Monitor |
Documentation arrivedAnthropic's documentation has since written up Monitor, on Claude apps gateway configuration.
the line in the docsThe CLI sends metrics, logs, and, when enabled, traces to the gateway, which relays them verbatim to each configured destination. The exports use OpenTelemetry Protocol (OTLP) over HTTP. To skip the relay and have sessions export straight … |
|
v2.1.233forward_user_identity |
Documentation arrivedAnthropic's documentation has since written up forward_user_identity, on Claude apps gateway configuration.
the line in the docsIf you set `forward_user_identity: true` on an upstream, a `429` it returns to a request that carried the developer's email doesn't fail over. See [how a per-user limit denial reaches the developer](#per-user-identity-headers-for-a-proxy-y… |
|
v2.1.257--debug |
Documentation arrivedA small documentation edit on Channels reference touched a line naming --debug after this was published.
the line in the docs* **`curl` succeeds but nothing reaches Claude**: run `/mcp` in your session to check the server's status. A `failed` status usually means a dependency or import error in your server file. To see the stderr trace, restart with `claude --de… |
|
v2.1.247--debug |
Documentation arrivedA small documentation edit on Channels reference touched a line naming --debug after this was published.
the line in the docs* **`curl` succeeds but nothing reaches Claude**: run `/mcp` in your session to check the server's status. A `failed` status usually means a dependency or import error in your server file. To see the stderr trace, restart with `claude --de… |
|
v2.1.232--debug |
Documentation arrivedA small documentation edit on Channels reference touched a line naming --debug after this was published.
the line in the docs* **`curl` succeeds but nothing reaches Claude**: run `/mcp` in your session to check the server's status. A `failed` status usually means a dependency or import error in your server file. To see the stderr trace, restart with `claude --de… |
|
v2.1.261/mcp |
Documentation arrivedA small documentation edit on Channels reference touched a line naming /mcp after this was published.
the line in the docs* **`curl` succeeds but nothing reaches Claude**: run `/mcp` in your session to check the server's status. A `failed` status usually means a dependency or import error in your server file. To see the stderr trace, restart with `claude --de… |
|
v2.1.257/mcp |
Documentation arrivedA small documentation edit on Channels reference touched a line naming /mcp after this was published.
the line in the docs* **`curl` succeeds but nothing reaches Claude**: run `/mcp` in your session to check the server's status. A `failed` status usually means a dependency or import error in your server file. To see the stderr trace, restart with `claude --de… |
|
v2.1.257/mcp |
Documentation arrivedA small documentation edit on Channels reference touched a line naming /mcp after this was published.
the line in the docs* **`curl` succeeds but nothing reaches Claude**: run `/mcp` in your session to check the server's status. A `failed` status usually means a dependency or import error in your server file. To see the stderr trace, restart with `claude --de… |
|
v2.1.257/mcp |
Documentation arrivedA small documentation edit on Channels reference touched a line naming /mcp after this was published.
the line in the docs* **`curl` succeeds but nothing reaches Claude**: run `/mcp` in your session to check the server's status. A `failed` status usually means a dependency or import error in your server file. To see the stderr trace, restart with `claude --de… |
|
v2.1.248/mcp |
Documentation arrivedA small documentation edit on Channels reference touched a line naming /mcp after this was published.
the line in the docs* **`curl` succeeds but nothing reaches Claude**: run `/mcp` in your session to check the server's status. A `failed` status usually means a dependency or import error in your server file. To see the stderr trace, restart with `claude --de… |
|
v2.1.248/mcp |
Documentation arrivedA small documentation edit on Channels reference touched a line naming /mcp after this was published.
the line in the docs* **`curl` succeeds but nothing reaches Claude**: run `/mcp` in your session to check the server's status. A `failed` status usually means a dependency or import error in your server file. To see the stderr trace, restart with `claude --de… |
|
v2.1.248/mcp |
Documentation arrivedA small documentation edit on Channels reference touched a line naming /mcp after this was published.
the line in the docs* **`curl` succeeds but nothing reaches Claude**: run `/mcp` in your session to check the server's status. A `failed` status usually means a dependency or import error in your server file. To see the stderr trace, restart with `claude --de… |
|
v2.1.248/mcp |
Documentation arrivedA small documentation edit on Channels reference touched a line naming /mcp after this was published.
the line in the docs* **`curl` succeeds but nothing reaches Claude**: run `/mcp` in your session to check the server's status. A `failed` status usually means a dependency or import error in your server file. To see the stderr trace, restart with `claude --de… |
|
v2.1.247/mcp |
Documentation arrivedA small documentation edit on Channels reference touched a line naming /mcp after this was published.
the line in the docs* **`curl` succeeds but nothing reaches Claude**: run `/mcp` in your session to check the server's status. A `failed` status usually means a dependency or import error in your server file. To see the stderr trace, restart with `claude --de… |
|
v2.1.238/mcp |
Documentation arrivedA small documentation edit on Channels reference touched a line naming /mcp after this was published.
the line in the docs* **`curl` succeeds but nothing reaches Claude**: run `/mcp` in your session to check the server's status. A `failed` status usually means a dependency or import error in your server file. To see the stderr trace, restart with `claude --de… |
|
v2.1.238/mcp |
Documentation arrivedA small documentation edit on Channels reference touched a line naming /mcp after this was published.
the line in the docs* **`curl` succeeds but nothing reaches Claude**: run `/mcp` in your session to check the server's status. A `failed` status usually means a dependency or import error in your server file. To see the stderr trace, restart with `claude --de… |
|
v2.1.238/mcp |
Documentation arrivedA small documentation edit on Channels reference touched a line naming /mcp after this was published.
the line in the docs* **`curl` succeeds but nothing reaches Claude**: run `/mcp` in your session to check the server's status. A `failed` status usually means a dependency or import error in your server file. To see the stderr trace, restart with `claude --de… |
|
v2.1.238/mcp |
Documentation arrivedA small documentation edit on Channels reference touched a line naming /mcp after this was published.
the line in the docs* **`curl` succeeds but nothing reaches Claude**: run `/mcp` in your session to check the server's status. A `failed` status usually means a dependency or import error in your server file. To see the stderr trace, restart with `claude --de… |
|
v2.1.232/debug |
Documentation arrivedA small documentation edit on Channels reference touched a line naming /debug after this was published.
the line in the docs* **`curl` succeeds but nothing reaches Claude**: run `/mcp` in your session to check the server's status. A `failed` status usually means a dependency or import error in your server file. To see the stderr trace, restart with `claude --de… |
|
v2.1.251CLAUDE.md |
Documentation arrivedAnthropic's documentation has since written up CLAUDE.md, on Claude Code changelog.
the line in the docs* \[Code Review] Fixed reviews ignoring a directory's CLAUDE.md conventions when the PR edited a root file (e.g. README.md) that only shares a name with a file that CLAUDE.md lists |
|
v2.1.251CLAUDE.md |
Documentation arrivedAnthropic's documentation has since written up CLAUDE.md, on Claude Code changelog.
the line in the docs* \[Code Review] Fixed reviews ignoring a directory's CLAUDE.md conventions when the PR edited a root file (e.g. README.md) that only shares a name with a file that CLAUDE.md lists |
|
v2.1.267@Claude |
Documentation arrivedAnthropic's documentation has since written up @Claude, on Claude Code changelog.
the line in the docs* \[Claude Tag] Fixed `@Claude !restart` in a thread with its own session sometimes also posting a contradictory "this thread is handled by the channel session" notice |
|
v2.1.242settings.json |
Documentation arrivedAnthropic's documentation has since written up settings.json, on Claude Code changelog.
the line in the docs* \[VSCode] Fixed Auto disappearing from the mode picker in new-tab or just-reloaded conversations when a project or local setting overrides the model named in `~/.claude/settings.json` |
|
v2.1.248CLAUDE_CONFIG_DIR |
Documentation arrivedAnthropic's documentation has since written up CLAUDE_CONFIG_DIR, on Claude Code changelog.
the line in the docs* \[VSCode] Fixed the session list, settings toggles, and chat tabs when `CLAUDE_CONFIG_DIR` is set in a settings file or the `environmentVariables` setting |
|
v2.1.246CLAUDE_CONFIG_DIR |
Documentation arrivedAnthropic's documentation has since written up CLAUDE_CONFIG_DIR, on Claude Code changelog.
the line in the docs* \[VSCode] Fixed the session list, settings toggles, and chat tabs when `CLAUDE_CONFIG_DIR` is set in a settings file or the `environmentVariables` setting |
|
v2.1.234CLAUDE_CONFIG_DIR |
Documentation arrivedAnthropic's documentation has since written up CLAUDE_CONFIG_DIR, on Claude Code changelog.
the line in the docs* \[VSCode] Fixed the session list, settings toggles, and chat tabs when `CLAUDE_CONFIG_DIR` is set in a settings file or the `environmentVariables` setting |
|
v2.1.233CLAUDE_CODE_ENABLE_TODO_TOOLS |
Documentation arrivedAnthropic's documentation has since written up CLAUDE_CODE_ENABLE_TODO_TOOLS, on Claude Code changelog.
the line in the docs* Changed the task-tracking tools (TaskCreate/Get/Update/List, TodoWrite) to be offered only on Claude 3.x, Opus 4.0–4.7, Sonnet 4.0–4.6, Haiku 4.5; set `CLAUDE_CODE_ENABLE_TODO_TOOLS=1` elsewhere |