What's new in Claude Code — weekly dev digest

1 card

1. 01

   Once you are effective with one session, the next step is to multiply: worktrees for isolation, cross-session messages for coordination, headless runs for fan-out — and the summer of 2026 moved exactly these pieces from experiment to default.

   What's new in Claude Code — weekly dev digest · 2026

   Worktrees for isolation, cross-session messages for coordination, headless runs for fan-out.

   The guide puts scaling after verification, not before it. The tools: git worktrees (isolated checkouts, edits don't collide, EnterWorktree starts one from inside a session), claude -p for scripts and CI (with JSON output and an allowed-tools list for unattended runs), /batch, which splits a large change across 5–30 sub-agents each with its own worktree and pull request, and the Writer / Reviewer pattern in two sessions: a fresh context is not biased toward the code it just wrote. What changed between June and August 2026, per the weekly digest: Sonnet 5 (native one-million-token window, adaptive thinking) and Opus 5 (the same million, plus fast mode) became the default models; sub-agents run in the background by default, and since August fork mode is on — a sub-agent can inherit the whole conversation instead of starting empty; sessions message each other and can be @-mentioned by name; auto mode became the default permission mode on paid plans, with a classifier that blocks only what looks risky; /code-review runs as a background sub-agent; /design (preview) draws editable artboards; dynamic workflows orchestrate dozens of agents from one script. The cost of each step is that it moves coordination from you to tools; what does not move is verification. Parallelism multiplies throughput, not quality.

   “Cross-session messaging: on macOS and Linux, your Claude Code sessions can now message each other, so Claude passes a finding or a decision from one session to another instead of you re-explaining it.”

   Open the card →