CLAUDE CODE V2.1.80 SHIPS BIG-REPO PERF GAINS, PROXY STREAMING FIXES, AND NEW MCP PUSH CHANNELS
Anthropic released Claude Code v2.1.80 with large-repo performance improvements, safer proxy streaming, new agent hooks, and visible rate-limit status. The [v2...
Anthropic released Claude Code v2.1.80 with large-repo performance improvements, safer proxy streaming, new agent hooks, and visible rate-limit status.
The v2.1.80 release trims about 80 MB at startup on 250k-file repos, speeds up @ file autocomplete, and properly restores parallel tool results when resuming sessions. It also fixes 400s seen with fine-grained tool streaming through API proxies, AWS Bedrock, and Vertex, and hardens voice mode WebSockets.
Agent-facing updates include a rate_limits field for statusline scripts, inline plugin declarations via source: 'settings', an effort override for skills and slash commands, and a research-preview --channels flag so MCP servers can push messages into a session notes. The ecosystem is moving too: the installable skills library got a reliability and onboarding pass in antigravity-awesome-skills v8.3.0, and there’s an open-source testing stack tailored to coding agents in Agentic QE Fleet.
Fewer flaky failures and lower memory use make agents viable on very large monorepos and behind enterprise API gateways.
New MCP push channels and inline plugin provisioning reduce glue code for event-driven workflows and environment setup.
-
terminal
Point Claude Code at a 200k+ file repo and compare startup memory and @ autocomplete latency before vs. v2.1.80.
-
terminal
Run a tool-streaming workflow through Bedrock or Vertex and confirm 400s are gone; validate --resume restores all parallel tool results.
Legacy codebase integration strategies...
- 01.
If you proxy through Bedrock/Vertex, upgrade to cut 400s and add rate-limit surfacing in your statusline to avoid job thrashing.
- 02.
Use source: 'settings' to declare required plugins in versioned settings.json for deterministic environments across devs and CI.
Fresh architecture paradigms...
- 01.
Prototype event-driven agents with --channels and an MCP server pushing repo or pipeline events into Claude Code sessions.
- 02.
Adopt a curated skills bundle (e.g., antigravity-awesome-skills) to standardize prompts and workflows from day one.