$ the-wire · showcase
Sonnet 5.5 becomes the default, Opus 5.5 takes over the skills docs
By RepoJournal · Filed · About Anthropic · Composed from the cited sources · methodology
Claude Code v2.1.284 ships Sonnet 5.5 as the API default, the skills guide rewrites its model defaults to Opus 5.5, and the sandbox runtime tightens write-limit and exit-status behavior.
v2.1.284 anthropics/claude-code
Claude Code v2.1.284 adds Claude Sonnet 5.5 (claude-sonnet-5-5) as the default Sonnet model on the Anthropic API, with 1M context and $2/$10 per Mtok including $0.20/Mtok cache reads. Auto mode also gains a "Yes, but ask again next time" answer for reads outside the working directories, and /usage now shows gateway spend limits in dollars.
Update claude-api skill: Claude Opus 5.5 default, Claude Sonnet 5.5, build-eval and hillclimb guides anthropics/skills
The claude-api skill makes claude-opus-5-5 the default model across SKILL.md, models.md, and every language example, demoting Claude Opus 5 to the previous Opus and adding a "Migrating to Claude Opus 5.5" guide to shared/model-migration.md. Claude Sonnet 5.5 becomes the current Sonnet. If you follow the skill's examples in generated code, the model IDs they emit are changing.
linux: exit status under zsh, and import zod/v3 anthropics/sandbox-runtime
A Linux network-restricting wrap now reports the command's own exit status under zsh; the cleanup trap previously ended in a bare exit, which zsh reads as the status of the trap's last command, so a failing command could report 0. The config schemas also import zod/v3 so they keep the v3 API where a consumer's dependency tree resolves zod to version 4.
mods: revert two changes (agents-md truncated reads, diff forced colors) anthropics/claude-code
Two mods return to their earlier behavior: the agents-md truncated-read fix and the diff forced-colors fix are both reverted. Teams relying on instructions being retained after truncated reads, or on hunks surviving Git's forced colored output, get the old behavior back.
linux: bind a deny path that another sandbox makes while the wrap is looking anthropics/sandbox-runtime
On Linux, two processes wrapping the same project could race when one created the empty mount-point file that blocks an absent denyWrite path while the other was still checking whether the path existed; the existence question now excludes the path itself. A separate README change documents that write limits are judged by where a write lands after every symlink is followed, tested on Linux and m...
