Five hours passed between these two releases. 2.1.275 landed at 20:20 UTC last night, 2.1.276 at 01:39 UTC this morning — and the second one exists only because the first shipped a regression.
It hit anyone pointing ANTHROPIC_BASE_URL at a proxy or gateway. Every request failed with 400 … Input tag 'advisor_20260301'. Not some requests. All of them. If you updated last night and work behind a corporate gateway, you had a dead tool for a few hours.
Your account brings its skills along
The most interesting addition in 2.1.275 is easy to skim past: skills and plugins enabled on your claude.ai account now sync into terminal sessions signed in with that account. Set up what Claude should be able to do once, in the app, and find it again in the terminal.
If you’d rather not, set syncClaudeAiSkills: false and syncClaudeAiPlugins: false. Two separate switches, and you have to know about both.
In the same vein: /plugin install <plugin> --marketplace <source> now offers to add the marketplace for you instead of sending you off to run a second command first. And when you sign in through a Claude apps gateway, Claude Code shows the account the gateway names and asks you to confirm it before saving the credential. /status displays it afterwards.
Ctrl+Enter sends everything at once
There’s now a key that interrupts the current turn and fires off every message you’ve queued: ctrl+enter, or ctrl+x ctrl+s. Sent and queued messages sit there in gray until the model receives them. Sounds minor. It changes how you feed things in during a long answer.
One fix goes past convenience. Plugin messages, logs and the output of claude plugin marketplace list could print a password or token stored inside a git, ssh or marketplace URL. That’s fixed now. If you’ve shared logs like that anywhere, it’s worth a look.
The crash list is long
The rest of 2.1.275 is roughly thirty repairs, and a striking number involve corrupted session data. Sessions refused to resume when the saved transcript held a malformed entry — in task reminders, in @-file attachments, in individual message content blocks. All three are caught now.
Also: /rewind in forked and background sessions sometimes restored a zero-filled or truncated file. Sandboxed Bash on Linux reported exit code 0 for failed commands when the shell was zsh. And SubagentStop hooks with a specific matcher fired for every stopping subagent whose type was empty.
Somebody pays for daily releases
With 2.1.274 two days ago, the pace of releases was already hard to miss. Today you can see the bill: a release in the evening, an emergency release overnight, and in between a tool that wouldn’t start for an entire group of users.
Worth noting: the npm stable channel still sits at 2.1.267 while latest and next are on 2.1.276. If you don’t want to be the test subject every evening, that’s where the difference lives.
Sources: