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.261/login |
Documentation arrivedAnthropic's documentation has since written up /login, on Claude Code changelog.
the line in the docs* Added the `gatewayInternalNetworks` managed setting, letting administrators allow `/login` to a Claude apps gateway on their organization's own public IPv4 block |
|
v2.1.261/login |
Documentation arrivedAnthropic's documentation has since written up /login, on Claude Code changelog.
the line in the docs* Added the `gatewayInternalNetworks` managed setting, letting administrators allow `/login` to a Claude apps gateway on their organization's own public IPv4 block |
|
v2.1.257/login |
Documentation arrivedAnthropic's documentation has since written up /login, on Claude Code changelog.
the line in the docs* Added the `gatewayInternalNetworks` managed setting, letting administrators allow `/login` to a Claude apps gateway on their organization's own public IPv4 block |
|
v2.1.251/login |
Documentation arrivedAnthropic's documentation has since written up /login, on Claude Code changelog.
the line in the docs* Added the `gatewayInternalNetworks` managed setting, letting administrators allow `/login` to a Claude apps gateway on their organization's own public IPv4 block |
|
v2.1.248/login |
Documentation arrivedAnthropic's documentation has since written up /login, on Claude Code changelog.
the line in the docs* Added the `gatewayInternalNetworks` managed setting, letting administrators allow `/login` to a Claude apps gateway on their organization's own public IPv4 block |
|
v2.1.248/login |
Documentation arrivedAnthropic's documentation has since written up /login, on Claude Code changelog.
the line in the docs* Added the `gatewayInternalNetworks` managed setting, letting administrators allow `/login` to a Claude apps gateway on their organization's own public IPv4 block |
|
v2.1.242/login |
Documentation arrivedAnthropic's documentation has since written up /login, on Claude Code changelog.
the line in the docs* Added the `gatewayInternalNetworks` managed setting, letting administrators allow `/login` to a Claude apps gateway on their organization's own public IPv4 block |
|
v2.1.242/login |
Documentation arrivedAnthropic's documentation has since written up /login, on Claude Code changelog.
the line in the docs* Added the `gatewayInternalNetworks` managed setting, letting administrators allow `/login` to a Claude apps gateway on their organization's own public IPv4 block |
|
v2.1.234/login |
Documentation arrivedAnthropic's documentation has since written up /login, on Claude Code changelog.
the line in the docs* Added the `gatewayInternalNetworks` managed setting, letting administrators allow `/login` to a Claude apps gateway on their organization's own public IPv4 block |
|
v2.1.232/login |
Documentation arrivedAnthropic's documentation has since written up /login, on Claude Code changelog.
the line in the docs* Added the `gatewayInternalNetworks` managed setting, letting administrators allow `/login` to a Claude apps gateway on their organization's own public IPv4 block |
|
v2.1.232/login |
Documentation arrivedAnthropic's documentation has since written up /login, on Claude Code changelog.
the line in the docs* Added the `gatewayInternalNetworks` managed setting, letting administrators allow `/login` to a Claude apps gateway on their organization's own public IPv4 block |
|
v2.1.232/login |
Documentation arrivedAnthropic's documentation has since written up /login, on Claude Code changelog.
the line in the docs* Added the `gatewayInternalNetworks` managed setting, letting administrators allow `/login` to a Claude apps gateway on their organization's own public IPv4 block |
|
v2.1.232/login |
Documentation arrivedAnthropic's documentation has since written up /login, on Claude Code changelog.
the line in the docs* Added the `gatewayInternalNetworks` managed setting, letting administrators allow `/login` to a Claude apps gateway on their organization's own public IPv4 block |
|
v2.1.232/login |
Documentation arrivedAnthropic's documentation has since written up /login, on Claude Code changelog.
the line in the docs* Added the `gatewayInternalNetworks` managed setting, letting administrators allow `/login` to a Claude apps gateway on their organization's own public IPv4 block |
|
v2.1.229/login |
Documentation arrivedAnthropic's documentation has since written up /login, on Claude Code changelog.
the line in the docs* Added the `gatewayInternalNetworks` managed setting, letting administrators allow `/login` to a Claude apps gateway on their organization's own public IPv4 block |
|
v2.1.239/cost |
Documentation arrivedAnthropic's documentation has since written up /cost, on Claude Code changelog.
the line in the docs* Added to the Claude apps gateway: with `pricing:` set in `gateway.yaml`, signed-in Claude Code clients receive the same rates through managed settings, so `/cost` and telemetry match the spend meter |
|
v2.1.234/cost |
Documentation arrivedAnthropic's documentation has since written up /cost, on Claude Code changelog.
the line in the docs* Added to the Claude apps gateway: with `pricing:` set in `gateway.yaml`, signed-in Claude Code clients receive the same rates through managed settings, so `/cost` and telemetry match the spend meter |
|
v2.1.232artifact |
Documentation arrivedA small documentation edit on Share session output as artifacts touched a line naming artifact after this was published.
the line in the docsAn artifact is a capture of work: one self-contained page with no backend, so it can't serve multiple routes. For a hosted internal tool with a backend, deploy it on your own infrastructure instead. See [Page constraints](#page-constraints… |
|
v2.1.237ANTHROPIC_BEDROCK_MANTLE_BASE_URL |
Documentation arrivedAnthropic's documentation has since written up ANTHROPIC_BEDROCK_MANTLE_BASE_URL, on Claude Code on Amazon Bedrock.
the line in the docsClaude Code constructs the endpoint URL from the AWS region, resolved with the same precedence as [Amazon Bedrock above](#3-configure-claude-code). To override the URL for a custom endpoint or gateway, set `ANTHROPIC_BEDROCK_MANTLE_BASE_UR… |
|
v2.1.251note |
Documentation arrivedAnthropic's documentation has since written up note, on Claude Code on Amazon Bedrock.
the line in the docsRun `/status` to see the resolved region. When the region came from your AWS config files or the default fallback, Claude Code also notes the source in the `/status` output. |
|
v2.1.261/status |
Documentation arrivedAnthropic's documentation has since written up /status, on Claude Code on Amazon Bedrock.
the line in the docsRun `/status` to see the resolved region. When the region came from your AWS config files or the default fallback, Claude Code also notes the source in the `/status` output. |
|
v2.1.260/status |
Documentation arrivedAnthropic's documentation has since written up /status, on Claude Code on Amazon Bedrock.
the line in the docsRun `/status` to see the resolved region. When the region came from your AWS config files or the default fallback, Claude Code also notes the source in the `/status` output. |
|
v2.1.259/status |
Documentation arrivedAnthropic's documentation has since written up /status, on Claude Code on Amazon Bedrock.
the line in the docsRun `/status` to see the resolved region. When the region came from your AWS config files or the default fallback, Claude Code also notes the source in the `/status` output. |
|
v2.1.257/status |
Documentation arrivedAnthropic's documentation has since written up /status, on Claude Code on Amazon Bedrock.
the line in the docsRun `/status` to see the resolved region. When the region came from your AWS config files or the default fallback, Claude Code also notes the source in the `/status` output. |
|
v2.1.248/status |
Documentation arrivedAnthropic's documentation has since written up /status, on Claude Code on Amazon Bedrock.
the line in the docsRun `/status` to see the resolved region. When the region came from your AWS config files or the default fallback, Claude Code also notes the source in the `/status` output. |
|
v2.1.248/status |
Documentation arrivedAnthropic's documentation has since written up /status, on Claude Code on Amazon Bedrock.
the line in the docsRun `/status` to see the resolved region. When the region came from your AWS config files or the default fallback, Claude Code also notes the source in the `/status` output. |
|
v2.1.246/status |
Documentation arrivedAnthropic's documentation has since written up /status, on Claude Code on Amazon Bedrock.
the line in the docsRun `/status` to see the resolved region. When the region came from your AWS config files or the default fallback, Claude Code also notes the source in the `/status` output. |
|
v2.1.243/status |
Documentation arrivedAnthropic's documentation has since written up /status, on Claude Code on Amazon Bedrock.
the line in the docsRun `/status` to see the resolved region. When the region came from your AWS config files or the default fallback, Claude Code also notes the source in the `/status` output. |
|
v2.1.232/status |
Documentation arrivedAnthropic's documentation has since written up /status, on Claude Code on Amazon Bedrock.
the line in the docsRun `/status` to see the resolved region. When the region came from your AWS config files or the default fallback, Claude Code also notes the source in the `/status` output. |
|
v2.1.231/status |
Documentation arrivedAnthropic's documentation has since written up /status, on Claude Code on Amazon Bedrock.
the line in the docsRun `/status` to see the resolved region. When the region came from your AWS config files or the default fallback, Claude Code also notes the source in the `/status` output. |
|
v2.1.229/status |
Documentation arrivedAnthropic's documentation has since written up /status, on Claude Code on Amazon Bedrock.
the line in the docsRun `/status` to see the resolved region. When the region came from your AWS config files or the default fallback, Claude Code also notes the source in the `/status` output. |
|
v2.1.232AWS_REGION |
Documentation arrivedAnthropic's documentation has since written up AWS_REGION, on Claude Code on Amazon Bedrock.
the line in the docs* You only need to set `AWS_REGION` to override your AWS profile's region or when your profile has no region. Claude Code resolves the region in this order: |
|
v2.1.232AWS_REGION |
Documentation arrivedAnthropic's documentation has since written up AWS_REGION, on Claude Code on Amazon Bedrock.
the line in the docs* You only need to set `AWS_REGION` to override your AWS profile's region or when your profile has no region. Claude Code resolves the region in this order: |
|
v2.1.232AWS_REGION |
Documentation arrivedAnthropic's documentation has since written up AWS_REGION, on Claude Code on Amazon Bedrock.
the line in the docs* You only need to set `AWS_REGION` to override your AWS profile's region or when your profile has no region. Claude Code resolves the region in this order: |
|
v2.1.251inherit |
Documentation arrivedAnthropic's documentation has since written up inherit, on Orchestrate teams of Claude Code sessions.
the line in the docsTeammates start with the lead's permission mode, except [`dontAsk` mode](/docs/en/permission-modes#allow-only-pre-approved-tools-with-dontask-mode), which they don't inherit. If the lead runs with `--dangerously-skip-permissions`, all team… |
|
v2.1.251inherit |
Documentation arrivedAnthropic's documentation has since written up inherit, on Orchestrate teams of Claude Code sessions.
the line in the docsTeammates start with the lead's permission mode, except [`dontAsk` mode](/docs/en/permission-modes#allow-only-pre-approved-tools-with-dontask-mode), which they don't inherit. If the lead runs with `--dangerously-skip-permissions`, all team… |
|
v2.1.251inherit |
Documentation arrivedAnthropic's documentation has since written up inherit, on Orchestrate teams of Claude Code sessions.
the line in the docsTeammates start with the lead's permission mode, except [`dontAsk` mode](/docs/en/permission-modes#allow-only-pre-approved-tools-with-dontask-mode), which they don't inherit. If the lead runs with `--dangerously-skip-permissions`, all team… |
|
v2.1.248dontAsk |
Documentation arrivedAnthropic's documentation has since written up dontAsk, on Orchestrate teams of Claude Code sessions.
the line in the docsTeammates start with the lead's permission mode, except [`dontAsk` mode](/docs/en/permission-modes#allow-only-pre-approved-tools-with-dontask-mode), which they don't inherit. If the lead runs with `--dangerously-skip-permissions`, all team… |
|
v2.1.257fable |
Documentation arrivedA small documentation edit on Escalate hard decisions with the advisor tool touched a line naming fable after this was published.
the line in the docsFable 5.1 requires Claude Code v2.1.257 or later. Both Fable models require [Fable access](/docs/en/model-config#work-with-fable). |
|
v2.1.236configs |
Documentation arrivedA small documentation edit on tools touched a line naming configs after this was published.
the line in the docsEnable the full toolset with `agent_toolset_20260401` when creating an agent. Use the `configs` array to disable specific tools or override their settings. Each config entry can also set a `permission_policy` that controls whether the tool… |
|
v2.1.260interactive |
Documentation arrivedAnthropic's documentation has since written up interactive, on permission-policies.
the line in the docsTo answer interactively instead, use `ant beta:sessions connect`, which shows the waiting call and sends this event when you allow or deny it. See [Connect to a Managed Agents session from your terminal](https://platform.claude.com/docs/en… |
|
v2.1.259addMcpServer |
Documentation arrivedAnthropic's documentation has since written up addMcpServer, on permission-policies.
the line in the docs.addMcpServer( |
|
v2.1.235language |
Documentation arrivedAnthropic's documentation has since written up language, on permission-policies.
the line in the docs<MultiFileExample language="cli" label="CLI"> |
|
v2.1.234ANTHROPIC_API_KEY |
Documentation arrivedAnthropic's documentation has since written up ANTHROPIC_API_KEY, on permission-policies.
the line in the docs-H "x-api-key: $ANTHROPIC_API_KEY" \ |
|
v2.1.233ANTHROPIC_API_KEY |
Documentation arrivedAnthropic's documentation has since written up ANTHROPIC_API_KEY, on permission-policies.
the line in the docs-H "x-api-key: $ANTHROPIC_API_KEY" \ |
|
v2.1.239/agents |
Documentation arrivedAnthropic's documentation has since written up /agents, on permission-policies.
the line in the docsagent=$(curl -fsSL https://api.anthropic.com/v1/agents \ |
|
v2.1.248deny |
Documentation arrivedA small documentation edit on multiagent-orchestration touched a line naming deny after this was published.
the line in the docsUnder `auto`, your `user.message` events can lead the server to allow a call it would otherwise deny. Nothing in a subagent's thread counts as your intent: your client posts no messages there, and the coordinator's messages to the subagent… |
|
v2.1.247origin |
Documentation arrivedA small documentation edit on multiagent-orchestration touched a line naming origin after this was published.
the line in the docsIf a subagent needs something from your client, such as [permission](https://platform.claude.com/docs/en/managed-agents/events-and-streaming#tool-confirmation) to run a tool call or the [result of a custom tool](https://platform.claude.com… |
|
v2.1.234max_turns |
Documentation arrivedAnthropic's documentation has since written up max_turns, on migration.
the line in the docs| `max_turns` | Count turns client-side. | |
|
v2.1.257PreToolUse |
Documentation arrivedAnthropic's documentation has since written up PreToolUse, on migration.
the line in the docs| `PreToolUse` / `PostToolUse` hooks | Your client already sees every `agent.custom_tool_use` event before responding; put the logic there. For built-in tools, use `permission_policy: always_ask` to review every call. [`auto`](https://plat… |