Claude Code Daily Briefing - 2026-10-04

Release Summary

VersionDateKey Changes
v2.1.28910/3Added agent.spawn API for teammates, fixed ~20 Claude Mods stability bugs, ~30 changes total
v2.1.28810/2Added /code-review --max-findings, MCP OAuth re-auth prompt, ~95 changes total (covered in the 10/3 briefing)
v2.1.28710/1Added Claude Mods and the “You should know” side agent, ~110 changes total (covered in the 10/2 briefing)

A day after v2.1.288 landed on 10/2, v2.1.289 shipped on 10/3. The only new feature is the agent.spawn API for plugin teammates; nearly everything else is a bug fix shoring up the stability of Claude Mods’ UI rendering, plugin hot-reload, and sandbox permission checks — all of which had launched just two days earlier, on 10/1.

Full release notes


New Features & Practical Usage

Claude Mods teammate API agent.spawn lands — along with a big batch of stability fixes just two days after launch (v2.1.289)

Plugins can now spawn teammate agents directly with the new agent.spawn API, paired with agent IDs that stay consistent across plugin hook events and idle/waiting state lookups via $.agent.list(). Since Claude Mods — which shipped on 10/1 — is an extension point that reaches deep into Claude Code’s internals, this same release also bundles roughly 20 stability fixes: mod-drawn UI freezing or crashing the whole session, plugin hot-reload failures, and commands hiding behind environment-variable prefixes that slipped past permission-deny rules.

# Spawn a teammate agent from mod/plugin code
$.agent.spawn(...)

If you’re building a mod that leans on side agents or teammates, it’s worth trying patterns that coordinate multiple agents through agent.spawn, and if you’re already running Mods, this update should make a noticeable dent in flakiness. Full release notes


Developer Workflow Tips

How to get the most out of Opus 5.5 in Claude and Claude Code (10/4)

Opus 5.5 responds better when you hand it the whole task up front — the goal, completion criteria, and the conditions under which it should pause and ask — rather than walking it through instructions step by step. It holds onto long, multi-stage work without losing the thread better than previous Opus versions did, letting early testers hand off hours-long coding tasks with minimal supervision. It also runs through its own reasoning before every response by default, so adding instructions like “think carefully” doesn’t noticeably change how deeply it reasons.

If you’re running Opus 5.5 on long autonomous tasks, it’s worth dropping the habit of micromanaging each step and instead front-loading the goal, completion criteria, and escalation conditions in one go — that’s where the model plays to its strengths. GeekNews


Security & Limitations

Claude service status — all operational as of 10/4, three days stable since the 10/1 credit-delay incident (10/4)

Checking status.claude.com directly: as of 10/4, claude.ai, Claude Console, Claude API, Claude Code, Claude Cowork, and Claude for Government are all Operational, with no active incidents. The most recent incident — a 10/1 delay in platform credits posting — was resolved the same day at 18:23 UTC, and it’s been three incident-free days since.

With all three incidents from the past 90 days (the 9/22 multi-model errors, the 9/29 error spike, and the 10/1 credit delay) resolved within the same day they occurred, there’s no need for any special action right now — business as usual. Claude Status

D.C. Circuit Court of Appeals upholds the Pentagon’s exclusion of Anthropic’s Claude (9/25)

The U.S. Court of Appeals for the D.C. Circuit ruled 2-1 to uphold the Department of Defense’s decision last March to exclude Anthropic’s Claude models from its defense supply chain. The court found that Anthropic’s built-in training restrictions — refusing to support tasks like mass domestic surveillance or fully autonomous weapons — amounted to the kind of interference with model design and operation the relevant statute addresses, and that the DoD had reasonable grounds to treat this as a national security risk. Anthropic had sued after refusing the DoD’s demand to lift these restrictions, but the court didn’t side with them.

If you’re selling Claude to government or defense-adjacent organizations, or courting customers in that space, this appellate ruling reconfirms that keeping the safety restrictions in place means U.S. defense supply-chain access stays off the table for now. The Hill


Community News


Minor Changes

All of the following are from v2.1.289 (10/3).



Interesting Projects & Tools