Tags
"An expandable usage limits section" is part of a new Claude Code layout for Claude Desktop, according to TestingCatalog, along with an updated model selector. Anthropic's official redesign announcement doesn't mention either one.
An admin pins Claude Code to the one model version the team vetted. In 2.1.283, setting the model match to "exact" keeps every newer release blocked until that admin adds it to the allowed list.
"Instead of cutting off mid-edit": Claude Code will try to wrap up when you hit the 5-hour limit mid-task, using a small allowance taken from your weekly limit. On Pro plans, that works once a week.
It's New Year's Eve, Opus is throwing 500 errors, and an Anthropic on-call engineer hands the hunt to Claude Code. It found the bug, then kept going and flagged 200 accounts from a batch of 4,000 for the safeguards team.
Claude Code 2.1.282 won't let a cloned repo's settings switch on telemetry. It ignores OpenTelemetry variables that turn on export or capture content, and names each skipped one at startup.
4% of Claude Code sessions ran up 65% of a ten-person team's spend over 30 days. Two of them, kept open and resumed daily for over a week, took 32% of the bill on their own.
Threads in Claude Code Projects were built as cloud sessions that keep working after you close your device, but Anthropic says they can now run on your own machine as well.
A one-time $250 credit on Max and $100 on Pro sits outside your usage limits, so when you hit a cap locally, Claude Code keeps going in cloud sessions until the credit runs out. You have to claim it by Oct 7.
A platform team sending Claude Code traffic through its own gateway into Bedrock can apply one Amazon Bedrock guardrail to every request in version 2.1.281, though it has to go on all Bedrock upstreams or none.
A canary test revealed that Claude Code skips AGENTS.md whenever telemetry is off, because loading it waits on a remote flag. Nothing warns you, and per the linked GitHub issue, Bedrock and Vertex users hit the same wall.
"Certain actions always happen," the Claude Code hooks guide promises, but only if your script exits 2. Exit 1, the usual Unix failure code, blocks nothing, and the agent carries on.
You're deep in a Claude Code session on Pro, Max or Team when the cap hits, and a banked reset now waits in Settings → Usage, good any time until Oct 22. It stacks on 5-hour limits that went up 20% today.
You're mid-migration, Claude Code has been running for hours, and it stops to ask "Want me to continue?" Anthropic's Opus 5.5 guide says one short CLAUDE.md rule about when to keep going cuts down those stops.
Pro and Team Standard plans in Claude Code switched their default from Sonnet to Opus, and that Opus is the new Opus 5.5, with 1M context at $4/$20 per Mtok.
A team pools its Claude Code subscriptions and routes GitHub reviews to whichever account still has capacity. By their own normalized tally, the Max 20x edge over Max 5x has shrunk from about 2.5x to about 1.5x.
Of the 33 tools AgentsMesh generates for, 17 read a root AGENTS.md and Claude Code makes 18. Though only when no CLAUDE.md sits in your working directory or above it: keep both files and the AGENTS.md is ignored entirely.
Anthropic deleted its own post after criticism that it framed a cut as an increase: Claude Code weekly limits go up 25% on September 14, but that sits 17% below the temporary 50% boost expiring September 13.
Run Claude Code in auto mode on the API, Bedrock or Vertex and a classifier rides along. From 2.1.278 it defaults to the server side, which doesn't charge for classifier overhead, and /status shows which path you got.
You clone a repo with an AGENTS.md in it and no CLAUDE.md, and Claude Code 2.1.277 reads it as the project instructions. Bedrock, Vertex and Foundry don't get that fallback yet.
Nearly two thousand original TypeScript files came with Claude Code on npm, tucked inside the source maps, and the teardown built on them says forked sub-agents share prompt prefixes to cut input tokens by around 95%.
