◉CLAUDE LABJP
●FORK — Claude Code 2.1.212 changes what /fork does: it copies your conversation into a new background session with its own row in claude agents, so you can keep working. The old in-session subagent is now /subtask●LIMITS — WebSearch calls are now capped at 200 per session by default, and subagent spawns get the same 200 ceiling, so a runaway search or delegation loop stops on its own●MCPBG — MCP tool calls running past two minutes now move to the background automatically, keeping the session usable. Tune the threshold with CLAUDE_CODE_MCP_AUTO_BACKGROUND_MS●PLANFIX — Fixed plan mode auto-running file-modifying Bash commands such as touch and rm without a permission prompt or an SDK canUseTool callback●SONNET5 — Claude Sonnet 5 is running on introductory pricing of $2 per million input tokens and $10 per million output. After August 31 it moves to $3 and $15●IPO — Bankers are reportedly lining up investor meetings for Anthropic ahead of a possible public listing as soon as October●FORK — Claude Code 2.1.212 changes what /fork does: it copies your conversation into a new background session with its own row in claude agents, so you can keep working. The old in-session subagent is now /subtask●LIMITS — WebSearch calls are now capped at 200 per session by default, and subagent spawns get the same 200 ceiling, so a runaway search or delegation loop stops on its own●MCPBG — MCP tool calls running past two minutes now move to the background automatically, keeping the session usable. Tune the threshold with CLAUDE_CODE_MCP_AUTO_BACKGROUND_MS●PLANFIX — Fixed plan mode auto-running file-modifying Bash commands such as touch and rm without a permission prompt or an SDK canUseTool callback●SONNET5 — Claude Sonnet 5 is running on introductory pricing of $2 per million input tokens and $10 per million output. After August 31 it moves to $3 and $15●IPO — Bankers are reportedly lining up investor meetings for Anthropic ahead of a possible public listing as soon as October
TAG

deployment

4 articles
← Back to all tags
Related:
claude-api3infrastructure3production2capacity-planning1streaming1claude-code1ci-cd1release1code-review1sizing1sla1observability1
⬡ API & SDK/2026-07-03Advanced

How Many Concurrent Claude API Requests Can You Actually Hold? Sizing Production Infrastructure with Little's Law and Measured Memory

Concurrency, queue depth, and memory are numbers you can derive, not guess. A working method for sizing Claude API production deployments with Little's Law, a memory probe, and a 30-minute load check — learned the hard way from an OOM crash.

⟐ Claude Code/2026-05-01Advanced

Designing a Release Gate Claude Code Can Run — Pre-Deploy Verification You Can Actually Read

A green CI does not mean a safe release. Walk through a seven-checkpoint release gate that asks Claude Code to write a readable, narrative report — with concrete scripts and the operational lessons behind them.

⬡ API & SDK/2026-04-29Intermediate

Infrastructure Requirements for Claude API Deployment: Sizing, SLA, and Compliance Decisions Before Production

Your prototype works. But what does 'production-ready' actually mean? This guide walks through how to derive infrastructure requirements from traffic, SLA, and data-residency decisions — with concrete numbers and a sizing formula.

⬡ API & SDK/2026-04-27Intermediate

Production Infrastructure for Claude API — 8 Things You Need Between 'It Works' and 'It Holds Up'

There is a much bigger gap than you'd think between a working Claude API call on your laptop and a service that survives real users. Here are the eight pieces of infrastructure I now consider non-negotiable, learned the hard way.