Follow Discord
Sweep 03 Oct 2026 · 20:28Z Build v2.1.289 510 read Stable v2.1.285 Latest v2.1.289 Next v2.1.289 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.289 ·

Teammates now keep their spawn details and ignore background and cwd overrides

Spawned teammates record how they were started, carry a teammateId, and keep their original background and cwd even when a tool call asks otherwise

Group of 3 You'll notice Improvements
JSON All of v2.1.289
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
TeammatesArea: what it touches
ImprovementsKind: in v2.1.289,
ImprovementsSection of the release

What

A teammate is a helper agent that Claude Code starts to work alongside the main session. Teammates now remember how they were started and hold on to those settings.

  • Spawn record: teammates now store a spawnedWith object holding the description, agentType and parentAgentId they were started with.
  • Spawn results: agent.spawn results now include a teammateId.
  • Listing: in-process teammates are listed with their agent type, description and parent instead of a generic "teammate".
  • Fixed settings: a teammate's background and cwd (its working folder) are forced back to the values it was spawned with. Claude Code says the override "does not apply to a teammate", or "do not apply to a teammate" when both are overridden.
  • Addressing: a message to an @-address that matches no teammate now gets "no live teammate of this session has the address".
  • isTeammate is added to the list of fields recorded with parentAgentId and provider.

Why

A teammate can no longer be moved out of its working folder or its foreground or background mode through tool arguments. Its records now say how it was started, which makes it easier to find and message the right teammate.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear which tools' inputs these resets apply to.

See this entry in the whole of v2.1.289 →

Feedback