April 27, 2026
Postmortem, GPT-5.5, and a Code sandbox escape
Get the next issue
TL;DR
Anthropic published a full postmortem on last week's 4-hour API outage tracing back to a compaction bug in their internal context cache. OpenAI shipped GPT-5.5 with multimodal tool use. A security researcher disclosed a sandbox escape in Claude Code's Docker runtime — patched in v1.8.9. MCP server count on the official registry passed 2,000.
API & Model Updates
Anthropic published a detailed postmortem on the April 21 outage that affected API availability for ~4 hours. Root cause: a race condition in their prompt cache compaction system under high load. Mitigation shipped; structural fix targeting Q2.
GPT-5.5 ships — multimodal tool use
OpenAI released GPT-5.5, adding multimodal inputs to tool calls (images and audio as tool arguments). Pricing: $12/M input tokens for the full model. Community consensus: still behind Claude on long-horizon agentic tasks but strong for vision-heavy workflows.
Claude Code & CLI
A security researcher disclosed a sandbox escape in Claude Code's Docker-based execution environment. By crafting a specific sequence of Bash tool calls, the agent could write files outside the intended mount. Anthropic patched in v1.8.9 (April 22). Update immediately if running v1.8.8 or earlier.
MCP Ecosystem
Official MCP registry passes 2,000 servers
The official MCP server registry crossed 2,000 published servers. Top categories: Databases (380), Web & Browser Automation (310), AI & LLM Tools (290). The registry added a verified badge system — server authors can apply for verification through GitHub identity.
Research & Safety
Anthropic published Constitutional AI v2, extending CAI to include multi-stakeholder principle sets — different principles can be weighted for different deployment contexts (consumer, medical, legal). The paper introduces a formal framework for principle conflict resolution.
Action Items
- →Update Claude Code to v1.8.9 immediately — critical sandbox escape patched
- →Read the API outage postmortem if you depend on uptime SLAs
All Resources
If you found this useful, subscribe to get the next issue.
Get the next issue