Claude Code 2.1.240 and 2.1.241: two releases, no release notes

2.1.240 shipped on August 22, 2.1.241 on August 23. Each carries exactly one entry in the official changelog: "Bug fixes and reliability improvements". Not a single line more, on either one.

Let's be upfront: there is no digest to write about the contents of these two releases, because no contents were published. What deserves three minutes is what you do when this happens.

What "bug fixes" does not tell you

The contrast is brutal. 2.1.239, two days ago, listed 61 entries, including a Bedrock bug that was silently doubling your billed API calls. That was verifiable, judgeable, actionable: you could read the list and decide whether it applied to you.

Here, you can decide nothing. A one-line entry lets you know neither whether a security fix is in there nor whether a regression is waiting for you. It does not prove the releases are empty either: the changelog page itself points to the CHANGELOG.md on GitHub for the full version, and the summary published in the docs is a selection, not an exhaustive list.

The natural instinct, digging around to reconstruct what moved, is a waste of time at a rate of one release per day. The right instinct is to fix the problem once, upstream.

The setting that answers this: autoUpdatesChannel

This is the parameter most people have never opened, and it is exactly the one that handles the "I have no idea what is in this" case. The setup docs describe two channels:

• "latest", the default: you get every release the moment it ships.
• "stable": you run a version that is typically about a week old, and that channel skips releases with major regressions.

The second half is what matters, not the first. The stable channel is not merely lag, it is a filter: problem releases never reach you at all. At a pace of two undocumented releases in two days, letting someone else spend a week discovering the regressions is a reasonable trade.

Set it through /config then Auto-update channel, or in your settings.json:

{
  "autoUpdatesChannel": "stable"
}

One useful detail if you switch: moving from latest to stable offers you either to stay on your current version or to accept the downgrade. Choosing to stay sets a minimumVersion at that version, which acts as a floor: neither the background update nor claude update will install anything below it. Switching back to latest clears it.

If you installed through Homebrew, the channel is not picked in your settings but by cask name: claude-code follows stable, claude-code@latest follows latest.

Knowing what you are actually running

Native installations update themselves in the background, on startup and periodically, and the change takes effect the next time you launch. Which means you have most likely already moved to 2.1.241 without asking for it.

Two commands are enough to check:

claude --version   # the version you are running
claude doctor      # including the result of the most recent update attempt

claude doctor is the lesser known of the two and the more useful one here: it prints read-only diagnostics without starting a session, including validation errors in your settings files.

And if you are on Homebrew, WinGet, apt, dnf or apk, nothing updates on its own by default: you may be several versions behind without knowing it.

What to take away

Do not try to reconstruct what 2.1.240 and 2.1.241 contain. The information is not published in any usable form, and the cost of digging outweighs the payoff.

The real question these two days raise sits elsewhere. If you use Claude Code for serious work and you have stayed on the default latest channel without ever thinking about it, you are accepting every undocumented release on the day it ships, including the ones the stable channel would have filtered out. That is a defensible choice if you want new features immediately. It is a much weaker one if you did not know you were making it.