◉CLAUDE LABJP
●CC 2.1.325 — No new release over the weekend; 2.1.325 (11/13) is still the latest●BILLING — 2.1.325 fixes background sessions on a claude.ai login being billed to an API key from the shell●SONNET 4.5 — Retires on the Claude API on 11/30, 14 days left. Check saved model settings too●403 — Users report a Cloudflare 403 page mid-session that still burns tokens●MANAGED — Since 11/12 you can request self-hosted Claude Managed Agents that run entirely on your own infrastructure●NEW — When Browser Extension Is Not Connected Won't Go Away●CC 2.1.325 — No new release over the weekend; 2.1.325 (11/13) is still the latest●BILLING — 2.1.325 fixes background sessions on a claude.ai login being billed to an API key from the shell●SONNET 4.5 — Retires on the Claude API on 11/30, 14 days left. Check saved model settings too●403 — Users report a Cloudflare 403 page mid-session that still burns tokens●MANAGED — Since 11/12 you can request self-hosted Claude Managed Agents that run entirely on your own infrastructure●NEW — When Browser Extension Is Not Connected Won't Go Away
Articles/Claude Code
⟐ Claude Code/2026-09-29Beginner

Two Default-Model Changes Haven't Reached Claude Code's Stable Channel Yet

This morning, Claude Code's stable channel sat 6 releases and 10 days behind latest. A small standard-library Python script that counts the gap in real, published releases instead of version arithmetic, and lists what hasn't arrived yet with a headline for each.

Claude Code285autoUpdatesChannelrelease channelupdatesPython32

✦ Premium Article

Tuesday mornings start with a small chore on the machines I keep running: I write down the Claude Code version, one line per day, so I can later trace what arrived when. This morning the line for latest read 2.1.284. Then I checked stable the same way, and the answer was 2.1.277 — unchanged since September 18.

In those ten days the default Opus moved to 5.5, and yesterday's release moved the default Sonnet to 5.5 as well. A machine on the stable channel has received neither. That was the moment I realized I had been trusting the phrase "stable is about a week behind" without ever counting it.

The counting tool came to about 80 lines of standard-library Python. What follows is how I built it, together with the numbers it produced today. If you can run python3 in a terminal, you can follow along even if you don't write code often.

The numbers first

The first thing I'd like to say plainly: the stable channel's lag should be measured in real, published releases, not described as "about a week." Here is what I measured this morning.

ChannelPoints toPublished (UTC)
stable2.1.2772026-09-18
latest2.1.2842026-09-28
Gap6 releases10 days

The 6 deserves a footnote. Subtract 277 from 284 and you get 7, but there is no 2.1.279 in the npm registry. Arithmetic says 7; counting the versions that exist says 6. That mismatch ended up shaping the script's design.

Taking only the first bullet of each release note, these are the changes a stable-channel machine does not yet have:

VersionPublishedFirst listed change
2.1.278Sep 19Auto mode's classifier defaults to the server side for API and Enterprise users and on Bedrock / Vertex / Foundry / gateways (no classifier overhead billed)
2.1.280Sep 22Claude Opus 5.5 (claude-opus-5-5) becomes the default Opus model: 1M context, $4/$20 per Mtok, $0.20 cache reads
2.1.281Sep 23Claude apps gateway support for newer Claude Desktop policy keys
2.1.282Sep 24New maxProseWidth setting
2.1.283Sep 25x-claude-code-prompt-id added to the gateway hint headers
2.1.284Sep 28Claude Sonnet 5.5 (claude-sonnet-5-5) becomes the default Sonnet model: 1M context, $2/$10 per Mtok, $0.20 cache reads

Two default-model changes and one billing-relevant default change. I still think choosing the stable channel is a sound decision. But if you know, in one line each morning, what that choice is holding back, you get to decide for yourself whether to wait or to move.

Step 1: Find out which channel your machine follows

Before building anything, confirm where your own installation stands. There are three places to look.

# the version that is running
claude --version
 
# the channel you follow (defaults to latest if the key is absent)
grep -H autoUpdatesChannel ~/.claude/settings.json 2>/dev/null || echo "autoUpdatesChannel not set (latest)"
 
# native installs keep their binaries here
ls ~/.local/share/claude/versions/ 2>/dev/null

Inside a session, opening /config and reading the Auto-update channel row is enough. The documentation describes latest, the default, as receiving new features as soon as they ship, and stable as a version that is typically about one week old, skipping releases with major regressions.

One caveat. Homebrew users pick a channel by cask name rather than by this setting: claude-code tracks stable and claude-code@latest tracks latest. For npm installs, the docs note that npm update -g may not move you to the newest release, so npm install -g @anthropic-ai/claude-code@latest is the safer way to upgrade.

✦

Thank you for reading this far.

Continue Reading

What follows includes implementation code, benchmarks, and practical content we hope you'll find useful. This site runs without ads — server and development costs are supported entirely by members like you. If it's been helpful, we'd be truly grateful for your support.

WHAT YOU'LL LEARN
✦You will be able to check, every morning with one script, whether your Claude Code follows the stable or latest channel and how many releases behind it currently sits
✦You will be able to count only the releases that actually exist, instead of subtracting version numbers, and turn the result into a headline list of changes that haven't reached you
✦You will be able to avoid spending weeks unaware that a default-model change or an auto-mode default change never arrived in your environment
Secure payment via Stripe · Cancel anytime
✦

Unlock This Article

Get full access to the rest of this article. Buy once, read anytime. This site is ad-free — your support goes directly toward keeping it running.

or
Unlock all articles with Membership →
Share

Thank You for Reading

Claude Lab is ad-free, supported entirely by members like you. We publish practical guides daily with implementation code, benchmarks, and production-ready patterns. If you've found it useful, we'd love to have you on board.

  • ✦Copy-paste ready implementation code
  • ✦New advanced guides published daily
  • ✦$5/mo or $10 for lifetime access
View Membership →

Related Articles

⟐ Claude Code2026-11-06
Claude Code Shipped 21 Releases in Four Weeks. I Counted Before Deciding How Often to Update
Should you check Claude Code updates every day or once a week? I counted npm's publish history with a standard-library Python script and used the last 28 days of counts and gaps to set a rhythm.
⟐ Claude Code2026-10-27
Counting How Often Claude Code Ships, Straight from npm's Publish History
How many Claude Code versions ship per week, and how many hours apart? A 37-line Python script reads npm's publish history to count weekly releases and the median gap, including the empty-week trap and why a Tuesday run makes this week look quiet.
⟐ Claude Code2026-10-15
The Hook That Was Meant to Guard My Japanese Folder Never Blocked Anything — Python Was Reading stdin as cp932
A PreToolUse hook guarding folders like 経理 or 議事録 silently lets edits through when Python's stdin defaults to cp932. How I reproduced it, the three-line fix, and one command to check your own hooks.