Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All releases Home ←olderv2.1.243 v2.1.246newer→

Claude Code v2.1.245

3 entries read diff v2.1.243 → v2.1.245 Markdown
How it breaks down
Not switched on2Under the hood1

Both of this release's visible changes sit around /autofix-pr, the command that watches your current pull request and fixes problems it finds, and neither is switched on. The command gains a second internal code path that returns a plain text result instead of drawing an interactive UI, but nothing in the build calls it, so /autofix-pr still behaves exactly as before: interactive only, and only when remote sessions are enabled for your account. Alongside it, the settings registry lists a key named autofixPrMode that is never defined or read, so setting it is not possible and would change nothing if it were. Taken together they look like the seams of a future switch for choosing how the command runs, headless or interactive.

Find
Pick an entry · j / k steps through
2 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.

Not switched on
Useful2 Signal4
Slash Commands

Groundwork for running /autofix-pr without the interactive UI#

A non-interactive version of /autofix-pr exists in the build but nothing calls it yet.

A text-only result path for /autofix-pr is fully written but unreachable; the command stays interactive-only.

/autofix-pr
What

/autofix-pr, which watches your current pull request and fixes problems it finds, gains a second code path that returns a plain text result instead of drawing a UI. Nothing in this build calls it, so the command still behaves exactly as before: interactive only, and only when remote sessions are enabled for your account.

Details
  • The new path trims the arguments you pass, runs the same autofix work, and returns text for success and failure, or the fixed string Autofix PR cancelled when the run is stopped.
  • That text-result shape is what commands usable from print mode return elsewhere in the bundle, which is what suggests a future non-interactive /autofix-pr.
  • The command's own description is unchanged and it is still declared as a UI command, without the flag that around 30 other commands set to mark themselves usable outside the interactive session.
  • The interactive flow is untouched, including its Spawning cloud autofix session… and Turning on autofix… steps.
  • Availability of /autofix-pr itself is unchanged: it needs the remote-sessions capability on your account plus an enterprise or API-key condition.
Evidence

return { type: "text", value: "Autofix PR cancelled" };

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

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

Not switched on
Useful1 Signal4
Slash Commands Notable not in their notes

An unused internal setting slot named autofixPrMode#

A settings key named autofixPrMode is listed but undefined, so setting it does nothing.

The key autofixPrMode appears in the settings registry with no definition and no reader.

autofixPrMode
What

The settings registry lists an internal key autofixPrMode but never defines or reads it, so it cannot be set to anything and changes nothing. It is the likely future switch for choosing how /autofix-pr runs.

Details
  • The name appears exactly once, at the end of the display order for the Internal settings group, alongside snipEnabled, doneMeansMerged and autoUploadSessions.
  • No setting definition backs it, nothing writes it, and no code consults it when picking the autofix path.
  • It was already present in 2.1.243 in the same inert state.
Evidence

"autofixPrMode"

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

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.

1 entry

Internal Changesopen

Under the hood
Useful2 Signal1
Elsewhere

Version bumped to 2.1.245#

The version number moves to 2.1.245; nothing else about this area changed.

What

The build stamp moves from 2.1.243 to 2.1.245. Nothing else in this area changed.

Details
  • Build time is now 2026-08-25T04:00:18Z, up from 2026-08-24T21:05:22Z.
  • The version string is copied into every place that reports it: the CLI version output, the claude-code/ and claude-cli/ user-agent strings, update and downgrade messages, daemon start logs, and the SDK binary-version response.
  • Around 110 of the 118 changes in this group are the same constant repeated across bundled modules, so this release carries almost no other code change here.
Evidence

GIT_SHA: "28b7e8c41235a9e2fcb24248e60c4cc2d29c853a", BUILD_TIME: "2026-08-25T04:00:18Z"

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

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.245. 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.

  • Fixed a crash on startup on Linux distributions that ship glibc 2.44 (for example Arch Linux, CachyOS and Fedora Rawhide)
Read it on GitHub →
System prompt

No change to the system prompt since v2.1.243.

Claude Code, interactive mode

Read the prompts for this release →
Documentation

What the docs did around this release

890 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.

office-agents/outlook Changed +7 -2 recorded here claude-docs office-agents/opentelemetry New page +304 -0 recorded here claude-docs claude-tag/users/proactivity Changed +1 -1 recorded here claude-docs claude-tag/users/memory Changed +4 -2 recorded here claude-docs claude-tag/users/getting-started Changed +9 -9 recorded here claude-docs claude-tag/concepts/security-and-data Changed +1 -0 recorded here claude-docs claude-tag/concepts/how-it-works Changed +5 -5 recorded here claude-docs claude-tag/concepts/data-lifecycle New page +104 -0 recorded here claude-docs claude-tag/admins/workspaces Changed +12 -3 recorded here claude-docs claude-tag/admins/restrict-access Changed +1 -0 recorded here claude-docs claude-tag/admins/for-slack-admins Changed +6 -0 recorded here claude-docs managed-agents/environments Changed +2 -2 recorded here api

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.

The documentation ledger →
Switches

Every name in this release

The 2 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.

Slash commands

Settings and names in the code