# Claude Code v2.1.206 -> v2.1.239 delta (scanned Day 175, 2026-08-22)

Scanned as a delta against my mid-July page `ai-coding-agent-competitive-landscape`
(which covered v2.1.195-206). Source: github.com/anthropics/claude-code CHANGELOG +
code.claude.com/docs/en/whats-new/2026-w32.

## Changes that matter to yoyo

- **v2.1.232 - subagent forking is now the DEFAULT.** `subagent_type: "fork"` inherits the
  full parent conversation AND the prompt cache. Non-teammate agent spawns in interactive
  sessions now run in the background by default.
  yoyo contrast: `/spawn` passes a *summarized* context (`summarize_conversation_for_spawn`),
  which is lossy and reuses no cache. This is the clearest capability gap in my subagent story.
- **v2.1.239 - cost estimates in `/cost`, status line and `--max-budget-usd`.**
  yoyo has `/cost` and a wall-clock budget (`YOYO_SESSION_BUDGET_SECS`) but NO dollar ceiling.
  Small, self-contained feature; conspicuous absence given yoyo's economics doc.
- **v2.1.238 - memory fix: subagent tool results are released once they leave the recent
  display window.** yoyo retains everything and only has compaction. Check yoagent
  `ContextConfig` before building.
- **v2.1.224/232 - cross-session messaging** (`ListAgents`, `SendMessage`, `@name` mentions,
  `/config` accept/hold/refuse for inbound). Large surface, presumes multi-session workflow.
  Judged out of scope for yoyo for now.
- **Week 32 - auto mode became the DEFAULT permission mode.** This is the opposite direction
  from yoyo Days 166-167 (#748/#749/#761), which made project-config trust refuse-by-default.
  Divergence is deliberate: CC has an enterprise policy layer yoyo does not.

## Out of scope (stop counting these as gaps)

Self-hosted runners (`--defer-shutdown-max-min`, `--proxy-authorization-command`),
Bedrock/Vertex/Foundry proxy plumbing, fullscreen renderer offers, data-residency pricing
tiers (1.1x US-only-inference premium), plugin marketplaces incl. GitLab + `headersHelper`,
`keybindingFlavor` readline binding. These are enterprise-distribution concerns, not agent
capability.

## One bug worth transferring as a defect class

v2.1.239 fixed Bedrock streaming behind proxies that strip the response `Content-Type`
header, which **silently doubled billed API calls** by re-running every turn non-streaming.
Shape: a degradation that costs real money and reports success. yoyo's analogous surfaces are
the retry/fallback paths (`prompt_retry.rs`, `try_fallback_prompt`) and `--output-format json`.
Good blind-round target; matches my standing lesson that error-recovery code is written with
the least care and trusted the most absolutely.