Claude Code v2.1.278

27 entries read v2.1.277 → v2.1.278 Markdown Unofficial

This build's seven gated additions cluster around a single unreleased feature: a billing notice warning some users that auto mode is still charging them for classifier requests even though they can't act on it yet. The notice would surface as a dialog in interactive sessions, as stderr text or a stream-json warning event in non-interactive and headless sessions, and pressing Escape on it cancels the in-flight tool call it interrupted. Behind it, auto mode's core permission-decision flow has been rebuilt to check this billing logic before falling back to the local classifier, and a new gate called tengu_quiet_lantern controls when the server classifier falls back to local at all. None of this is switched on yet; the model/context panel does gain a new "Auto mode server" row, but it's part of the same still-dark feature.

Three things are live today. Sessions connecting through a Unix socket (via ANTHROPIC_UNIX_SOCKET) now lose server-side auto mode classification unless they're on an SSH remote connection. The status panel that already shows model, MCP, and theme now also lists the current permission mode, and a new diagnostics row reports whether the auto mode server classifier is Enabled or Disabled.

The one fix this release addresses an SDK startup diagnostic: a specific shutdown reason was never making it into its own diagnostic log line, and that assignment bug is now corrected.

Reading as
Show only
Tier
Flag state
Names
Pick an entry · j / k steps through · rest on a row to peek
6 entries

What probably matters to you

Anything you can use today, anything that visibly changes, and anything worth poking at. One line each, open for detail.

In dev
Nothing to try yet
Useful3 Signal4
Group of 2 Auto Mode Notable unclear

Billing notice for auto mode classifier fallback#

Auto mode now shows a dialog explaining when a session isn't eligible for classifier billing changes, with telemetry to match

Unclear The three related gates (tengu_velvet_heron, tengu_auto_mode_server_fallback_notice, tengu_auto_mode_server_fallback_notice_closed) are unread, so it's unclear which accounts this dialog reaches.

Feature flag
tengu_velvet_heron Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.278: on

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.278. It isn't a statement about your account. What a flag value here can and cannot tell you

Details 0 0 Feedback

What

  • Claude Code now shows a new dialog when auto mode's tool-call classifier falls back from the server-side classifier to the local one. It tells you Claude Code is changing auto mode to stop charging for classifier requests, but explains that your current session isn't eligible for that change, so this classifier request is still billed as before.
  • The dialog appears when the server-side (third-party) classifier has already been refused earlier in the session and a tool call falls back to the local, billed classifier. You can press Enter to continue (and accept the billed request) or Escape to cancel the tool call, which is recorded with the reason "Cancelled at the classifier billing notice."
  • New analytics events were added to track when the server-side classifier fails to return a result and auto mode falls back to local classification, and when this new billing notice is shown or closed.

Why

This makes it clear to users when a specific auto-mode session still incurs classifier billing despite an upcoming change to stop charging for these requests, and gives them the choice to cancel rather than proceed with a billed request they didn't expect.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

·Internal
Under the hood
Useful3 Signal4
System Prompt unclear

The main system prompt gained text#

The main system prompt gained new text, including a mention of 'control'

Unclear The evidence only confirms new text was added and that it contains the word 'control'; what the addition says or does is not established.

Details 0 0 Feedback
What

The main system prompt, the instructions Claude Code sends to the model at the start of every conversation, gained additional text. This was measured directly from the prompt as sent by the running client, across both the CLI and SDK versions and across anonymous and account-linked variants, and the added text includes the word control.

Why

Changes to the system prompt can affect how Claude behaves in subtle ways across all sessions, since this prompt is sent every time regardless of what a user asks. The exact content and purpose of the addition are not established beyond the one quoted word.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

Improved
You'll notice
Useful2 Signal3
Auto Mode Notable

Auto-mode classifier now distrusts unix-socket proxies unless SSH remote#

Sessions using ANTHROPIC_UNIX_SOCKET now lose server-side auto mode classification unless connecting over SSH remote

Details 0 0 Feedback
ANTHROPIC_UNIX_SOCKETCLAUDE_CODE_ENTRYPOINT
What

The check that decides whether a session counts as first-party (and so gets access to the server-side auto-mode classifier) now treats a session using ANTHROPIC_UNIX_SOCKET as third-party, disabling that server-side classifier, unless CLAUDE_CODE_ENTRYPOINT is set to ssh-remote.

Why

This closes a gap where a unix-socket connection could otherwise be treated as trusted first-party access to the server-side classifier; it's only allowed through when the entry point is specifically the SSH remote case.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

In dev
Nothing to try yet
Useful2 Signal3
Status Panel Notable no docs found

'Auto mode server' status row added to the model/context panel#

The model/context status panel gains an 'Auto mode server' row showing Enabled or Disabled

Feature flag
tengu_quiet_lantern Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.278: on

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.278. It isn't a statement about your account. What a flag value here can and cannot tell you

Details 0 0 Feedback
tengu_quiet_lantern
What

The status panel that shows model and context details now includes a new row labeled 'Auto mode server', showing either 'Enabled' or 'Disabled'. This value is computed by checking the resolved classifier mode and whether the current model is a reduced-capability ('gimped') one.

Why

This gives users visibility into whether an automatic mode-selection server feature is active for their current model and session, where previously this state wasn't surfaced in the panel at all.

·Internal
Under the hood
Useful2 Signal3
Auto Mode Notable

Gateway/proxy detection feeding the billing notice message#

Claude Code now detects LLM gateways and swaps the billing notice for a gateway-specific message with a docs link

Feature flag
tengu_velvet_heron Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.278: on

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.278. It isn't a statement about your account. What a flag value here can and cannot tell you

Details 0 0 Feedback
litellmheliconeportkey
What

Claude Code can now detect whether the current base URL points to a known LLM gateway or proxy service, such as litellm, helicone, portkey, cloudflare-ai-gateway, kong, braintrust, bifrost, or databricks. It does this either by recognizing the hostname or by noticing a gateway during an actual request.

When a gateway is detected, the billing notice text changes: instead of the usual message, it tells the admin that the session is ineligible because requests are going through that gateway, and links to a docs page (auto-mode-classifier-billing) explaining how to fix it.

Why

This helps admins understand why a billing-related feature isn't working when their traffic is routed through a gateway or proxy, rather than leaving them with a generic or confusing notice.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

·Internal
Under the hood
Useful2 Signal3
Auto Mode Notable

Third-party server classifier gating tightened#

Auto mode's server-classifier eligibility check adds a new exclusion and respects CLAUDE_CODE_AUTO_MODE_SERVER as an override

Feature flag
tengu_quiet_lantern Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.278: on

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.278. It isn't a statement about your account. What a flag value here can and cannot tell you

Details 0 0 Feedback
CLAUDE_CODE_AUTO_MODE_SERVER
What

The logic that decides whether auto mode uses the server-side classifier (versus falling back to local-only classification) now excludes a specific case of first-party providers from that fallback path, and explicitly checks the CLAUDE_CODE_AUTO_MODE_SERVER environment variable as an override when deciding whether the feature is enabled at all.

Why

This narrows exactly which sessions are eligible for server-side classifier fallback, and makes sure an explicit CLAUDE_CODE_AUTO_MODE_SERVER setting is respected rather than being overridden by other logic.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

Were these the right ones to put at the top? 0 answered
Below the fold

Everything else

Smaller changes and internals, grouped as the pipeline found them. Nothing is dropped, it is only further down.

2 entries

Improvementsopen

Improved
You'll notice
Useful3 Signal2
Status Panel

Model/cwd status panel now shows the current permission mode#

The status panel that shows Model, MCP, and theme now also lists the current permission mode

Details 0 0 Feedback
What

The status panel Claude Code shows (the one listing things like Model, MCP servers, and theme) now includes a row for the current permission mode, driven by a new permissionMode value passed into that panel.

Why

This lets users see at a glance which permission mode they're in — for example whether tool calls are being auto-approved or require confirmation — without having to check settings separately.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

Improved
You'll notice
Useful2 Signal2
Status Panel

Auto mode server status surfaced as Enabled/Disabled#

A new diagnostics row reports auto mode's server classifier as Enabled or Disabled

Details 0 0 Feedback
What

A new diagnostics helper builds a status row labeled "Auto mode server" that reports either "Enabled" or "Disabled", based on a check of whether the auto-mode classifier resolves to server-side ("arbiter") mode and whether the current model is excluded from it.

Why

This gives users a direct way to see, in diagnostics output, whether their session is actually using the server-side auto-mode classifier or not, rather than having to infer it from behavior.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

1 entry

Bug Fixesopen

Fixed
You'll notice
Useful1 Signal1
Elsewhere

SDK startup diagnostic message assignment bug fixed#

Fixed a bug where a specific SDK shutdown reason never appeared in its own diagnostic log line

Details 0 0 Feedback
What

In the SDK's startup-exit diagnostic logging, the code path for a permanently-closed transport (the connection used to talk to the SDK) was writing its message into the wrong variable, so that reason likely never actually showed up in the printed SDKStartup: exiting without result diagnostic line. This has been corrected.

Why

This means diagnostic logs for SDK shutdowns will now correctly report "transport closed permanently" as the reason when that's what happened, making it easier to debug why an SDK session exited.

5 entries

In Developmentopen

In dev
Nothing to try yet
Useful2 Signal3
Auto Mode

Declining the billing notice cancels the in-flight tool call#

Pressing Escape on the new billing notice cancels the tool call it interrupted

Feature flag
tengu_velvet_heron Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.278: on

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.278. It isn't a statement about your account. What a flag value here can and cannot tell you

Details 0 0 Feedback
Escape
What

When the new classifier billing notice dialog is showing and the user presses Escape to decline, the tool call that triggered the notice is denied outright, with the reason recorded as "Cancelled at the classifier billing notice."

Why

This gives users a real way to stop a tool call rather than just dismissing a warning: declining the notice means the action doesn't go through.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

In dev
Nothing to try yet
Useful2 Signal3
Auto Mode

Billing notice surfaces as a stderr/stream-json warning in headless (print) mode#

The classifier billing notice prints to stderr or a stream-json warning when there's no dialog to show

Feature flag
tengu_velvet_heron Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.278: on

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.278. It isn't a statement about your account. What a flag value here can and cannot tell you

Details 0 0 Feedback
--verbose
What

In headless usage, such as -p/print mode or when output is set to stream-json, there's no interactive screen to show a pop-up dialog on. In those cases, the same classifier billing notice message is instead written to stderr, or emitted as a stream-json warning event when --verbose stream-json output is being used.

Why

This makes sure scripts and automated runs still get told when auto mode has fallen back to billed classifier requests, instead of the notice silently disappearing because there's no dialog surface to show it on.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

In dev
Nothing to try yet
Useful2 Signal3
Auto Mode

Auto-mode permission decision flow reworked around the new billing notice#

Auto mode's core permission check was rebuilt to run the new billing-notice logic before falling back to the local classifier

Feature flag
tengu_velvet_heron Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.278: on

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.278. It isn't a statement about your account. What a flag value here can and cannot tell you

Details 0 0 Feedback
What

The main function that decides whether a tool call needs permission in auto mode was restructured to check for the new billing-notice/fallback condition before calling the local classifier, and a new "no result" handler is now threaded through both the fast-path check (used in acceptEdits mode) and the main classification path.

Why

This ties the classifier billing notice into the actual permission decision flow, so a missing server verdict is handled consistently everywhere a tool call gets checked, rather than only in one code path.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

In dev
Nothing to try yet
Useful2 Signal3
Auto Mode unclear

Non-interactive/stream-json sessions get a stderr/warning-event billing notice instead of a dialog#

Non-interactive sessions now get the billing notice as stderr text or a stream-json warning event instead of a popup

Unclear Which gate(s) control this and what the billing notice specifically concerns are not established by the evidence.

Feature flag
tengu_velvet_heron Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.278: on

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.278. It isn't a statement about your account. What a flag value here can and cannot tell you

Details 0 0 Feedback
--verbose
What

When Claude Code runs in a mode without an interactive display, such as with --output-format stream-json --verbose (a mode that streams structured JSON events instead of a normal terminal view, with --verbose showing full turn-by-turn output), a billing notice that would normally appear as a dialog is now delivered differently. It's emitted as a warning event in the stream-json output, or written directly to standard error (stderr) otherwise, before normal output begins.

Why

This lets automated or scripted sessions that can't show a dialog still receive the same billing notice, in a form that fits the output format they're already consuming.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

In dev
Nothing to try yet
Useful1 Signal2
Auto Mode no docs found

New gate tengu_quiet_lantern controls arbiter local-fallback triggers#

A new gate, tengu_quiet_lantern, controls whether the server classifier falls back to local when unsupported

Feature flag
tengu_quiet_lantern Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.278: on

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.278. It isn't a statement about your account. What a flag value here can and cannot tell you

Details 0 0 Feedback
tengu_quiet_lantern
What

A new feature flag, tengu_quiet_lantern, has been added to control whether auto mode's server-side ("arbiter") classifier falls back to local classification specifically when the server returns no result or reports the feature as unsupported.

Why

This lets the server-classifier fallback behavior be turned on or off independently for different accounts, rather than being hard-coded into every install. Nothing has been read yet about which accounts have it on.

11 entries

Internal Changesopen

·Internal
Under the hood
Useful2 Signal2
Auto Mode

Session-scoped 'server classifier refused' latch drives permanent local fallback#

Once the server refuses classification once, auto mode sticks to local classification for the rest of the session

Details 0 0 Feedback
What

Claude Code now remembers, for the rest of a session, if the server says it won't run server-side auto-mode classification (or silently drops the answer). The first time that happens, it's logged as a warning and a session-long flag is set so every later classification check goes straight to the local classifier instead of trying the server again.

Why

This avoids repeatedly asking a server that has already said no, and makes the fallback to local (billed) classification consistent and predictable for the rest of that session rather than flipping back and forth.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

·Internal
Under the hood
Useful2 Signal2
Elsewhere unclear

New content-routing refusal-category allowlist for cyber/frontier_llm#

A new allowlist restricts routing based on refusal category to just 'cyber' and 'frontier_llm'

Unclear The finding does not say what effect this routing decision has on the user-visible response.

Details 0 0 Feedback
What

Claude Code has internal logic for routing certain requests based on an apiRefusalCategory value (a label describing why a response was refused). A new function now only keeps that route active when the refusal category is cyber or frontier_llm, and only if a few other conditions also hold: the visible route wasn't already declined, an internal check (JB()) passes, and a feature or permission check (G$()) also passes.

Why

This narrows an internal routing decision to two specific refusal categories, likely limiting when this content-routing path applies. The practical effect for most users is invisible, since it governs internal handling rather than anything surfaced directly.

·Internal
Under the hood
Useful1 Signal2
Elsewhere no docs found unclear

Request-latches class reworked from two Maps to scalar per-session fields#

Internal per-session request-latch storage was restructured from two maps to individual fields

Unclear The finding does not explain what behavioral difference, if any, this restructuring produces.

Details 0 0 Feedback
host.requestLatches
What

The internal object that tracks per-session request state (exposed as host.requestLatches) changed how it stores some of its data. Two fields that used to be Maps (key-value lookup structures) are now a plain boolean and two new placeholder fields, alongside other existing maps used for different purposes. This structure backs several internal checks, including ones related to server classifier fallback choices and observed gateways.

Why

This is an internal data-structure change with no direct user-facing effect described, but it underlies features like gateway detection and classifier fallback handling mentioned elsewhere in this release.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

·Internal
Under the hood
Useful2 Signal1
Elsewhere no docs found

Per-agent prompt-dump state can now be cleared/deleted#

Debugging 'dumpPrompts' state can now be cleared per agent or globally

Details 0 0 Feedback
dumpPrompts
What

Claude Code has an internal debugging feature called dumpPrompts that keeps track of state per agent (per subagent, a separate Claude instance handling part of a task). New helper functions let this state be cleared for a single agent or wiped out entirely.

Why

This is a developer-facing debugging tool rather than something end users interact with directly, but it means the tracked dump state can now be reset instead of only accumulating.

·Internal
Under the hood
Useful1 Signal1
Group of 2 Auto Mode

Auto mode classifier: refined 'no result' handling#

Auto mode's server-side classifier now distinguishes and relabels the case where no usable verdict is available

Details 0 0 Feedback

What

  • The auto-mode classifier's no-verdict message logic now also handles a new error case meaning the session no longer holds a stored result for an action (serverResultsNotHeld), in addition to the existing case where a verdict was never requested (serverNotRequested).
  • The internal telemetry/reason string used to record why the server-side classifier didn't return a usable decision was renamed from server_no_result to a new value.

Why

These changes make it possible to tell apart different reasons the server-side classifier didn't provide a verdict, so the fallback behavior and any related diagnostics are more precise.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

·Internal
Under the hood
Useful1 Signal1
Auto Mode

New request-latch state for server-side classifier fallback and gateway tracking#

Session state now tracks the inference gateway seen and any classifier fallback choice made

Details 0 0 Feedback
What

Claude Code's internal per-session state object gained new tracking for the auto-mode server classifier fallback:

  • which inference gateway was observed for the session
  • whether a fallback choice was made when the server-side classifier is unavailable, and what that choice was
  • a one-shot flag for announcing that fallback to the user (so the announcement only happens once)
  • whether the third-party server classifier was refused for this session
Why

This gives the new server-classifier fallback and billing-notice features a place to remember what's already happened in a session, so users aren't shown the same fallback notice repeatedly or asked to re-decide something already settled.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

·Internal
Under the hood
Useful1 Signal1
Elsewhere unclear

Dialog registration map reshuffled (Slack Connect / sign-in dialogs)#

Internal dialog registration was reorganized, affecting Slack Connect and Slack sign-in dialogs

Unclear It isn't clear whether the two new entries correspond to new dialogs or just a different way of registering existing ones.

Details 0 0 Feedback
What

The internal map that registers which component implements which UI dialog was restructured: a previously merged entry now uses a different pairing of helper functions, and two new entries were added to the end of the list. This affects dialogs including the Slack Connect consent prompt and the Slack sign-in offer prompt.

Why

This is an internal reorganization of how dialogs are wired up; the finding doesn't indicate any visible behavior change for these dialogs.

·Internal
Under the hood
Useful1 Signal1
Auto Mode unclear

New function captures custom ANTHROPIC_BASE_URL host for firstParty sessions#

A new helper captures the custom hostname when ANTHROPIC_BASE_URL points somewhere other than Anthropic's API

Unclear The finding doesn't say what consumes this captured hostname, only that it's produced in this specific case.

Details 0 0 Feedback
ANTHROPIC_BASE_URL
What

A new helper function returns the hostname from ANTHROPIC_BASE_URL in the specific case where the session is still classified as first-party but the base URL isn't api.anthropic.com, and no unix socket is in use.

Why

This appears to support telemetry or diagnostics around proxy or gateway hosts that don't match Anthropic's usual API address, likely to help identify unrecognized custom endpoints.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

·Internal
Under the hood
Useful1 Signal1
Auto Mode unclear

Third-party classifier availability check reworked#

The check for whether the server-side auto-mode classifier can be used was reworked internally

Unclear It's unclear from the evidence what the new predicate and the swapped function actually change in terms of which providers qualify.

Details 0 0 Feedback
What

The function that gates whether the server-side auto-mode classifier is usable changed its handling of third-party providers: it now checks a new predicate on the resolved provider, and calls a different negated function than before when deciding availability.

Why

This is an internal change to how third-party providers are evaluated for server-side classifier eligibility; the finding doesn't specify what practical difference it makes for users.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

·Internal
Under the hood
Useful1 Signal1
Elsewhere unclear

New request-latch queries for thinking resumption/highlights refusal#

Two new checks report whether 'thinking resumption' or 'thinking highlights' requests were refused

Unclear The finding does not say what consumes these new checks or what a user would see when one of these is true.

Details 0 0 Feedback
What

Claude Code keeps internal state (called request latches) tracking things about the current session's requests. Two small new helpers can now check whether that state indicates a request for 'thinking resumption' or 'thinking highlights' was refused.

Why

These are internal diagnostic helpers, so the direct impact isn't visible to users, but they suggest Claude Code is tracking more specifically when these particular thinking-related features get refused.

·Internal
Under the hood
Useful1 Signal0
Elsewhere

Version bump only#

This release is version 2.1.278, bumped from 2.1.277

Details 0 0 Feedback
What

This group of changes is purely the build version metadata (version number, build time, and git commit hash) being updated from 2.1.277 to 2.1.278, repeated across the many copies of that metadata embedded throughout the bundled code.

Why

This is a routine version bump with no functional change on its own.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

Verbatim
Official · Anthropic

Anthropic’s official release notes

Published verbatim by Anthropic for v2.1.278. Text is unmodified from the upstream changelog. Everything else on this page came out of the bundle instead, which is why the two lists don't match.

Of these 2 bullets, 2 name something an entry on this page also names, 0 name something no entry here does, and 0 name nothing specific enough to line up either way. The pairings are made on names both sides wrote down, a flag or a setting or a slash command, so read one as probably the same thing rather than as a fact, and read the middle number as candidates rather than as a miss count.

System prompt

No change to the system prompt since v2.1.277.

Claude Code, interactive mode

Documentation

What the docs did around this release

135 documentation changes were recorded within 24 hours either side of this release, nearest first. The closest 12 are below. They're here because they happened near this release in time. That's not a claim that this release caused the edit, or that the page documents anything in it.

Every time above is when this site's poller recorded the change, which is up to half an hour after the edit on an ordinary read and up to a day after it on a full sweep. Upstream's own edit time is used instead wherever a capture carries one. None of these do.

Switches

Every name in this release

The 12 literal strings found in the bundle, with the number of entries that name each one. Picking one searches for it. A name is here because this build's code mentions it, which is not the same as it working or being finished.

CLI flags

Environment variables

Settings and names in the code