CLAUDE CODE 2.1.86–2.1.87 SHIPS A SESSION HEADER FOR PROXIES AND KEY STABILITY FIXES; COMMUNITY SKILLS ADD SAAS MULTI‑TENANCY
Claude Code added a session-aware HTTP header and fixed several reliability issues that affected long sessions, tools, and cowork dispatch. The latest releases...
Claude Code added a session-aware HTTP header and fixed several reliability issues that affected long sessions, tools, and cowork dispatch.
The latest releases add an X-Claude-Code-Session-Id header so proxies can group and meter traffic per session, plus a stack of fixes for long transcripts, resume failures, MCP tools in bare mode, and VCS directory exclusions releases. A follow-up patch fixes cowork dispatch messages not being delivered in some cases.
A popular community skills pack introduced a multi-tenant SaaS architecture guide and a phase‑gated debugging workflow, alongside quality-of-life updates for discovery and 3D stacks v9.1.0 skills release. If you need a lightweight way to track Claude Code deltas, there’s also a community changelog repo you can watch changelog.
Session-level header makes observability, throttling, and attribution easier without parsing bodies in gateways or proxies.
Stability and memory fixes reduce failures in real-world, long-running coding sessions and unblock MCP tool usage in bare mode.
-
terminal
Update your proxy/gateway to log and bucket by X-Claude-Code-Session-Id; verify rate limits, quotas, and dashboards aggregate correctly by session.
-
terminal
Stress a long session with large transcripts and /feedback to confirm OOM and resume issues are gone, and validate MCP tools appear in --bare interactive sessions.
Legacy codebase integration strategies...
- 01.
Teach existing API gateways and SIEMs to trust, log, and alert on X-Claude-Code-Session-Id; backfill dashboards to pivot by session.
- 02.
Re-test legacy sessions created pre-2.1.85 for --resume behavior and confirm Grep/file autocomplete ignore .jj and .sl directories.
Fresh architecture paradigms...
- 01.
Design session-scoped quotas, cost accounting, and SLOs from day one using the new header.
- 02.
Use the community saas-multi-tenant skill as a starting blueprint for tenant isolation and admin pathways.