Follow Discord
Sweep 09 Oct 2026 · 17:27Z Build v2.1.296 517 read Stable v2.1.287 Latest v2.1.296 Next v2.1.296 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.296 ·

New controls over moving agents to the background and over agent messaging

A backgroundLaunchRule can now veto moving a foreground agent to the background, and new policy getters cover agent moves and cross-agent messaging

Group of 2 Under the hood Internal Changes
JSON All of v2.1.296
Under the hoodTier: how much it should matter to you
3Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
Agent MessagingArea: what it touches
Internal ChangesKind: in v2.1.296,
What probably matters to youSection of the release

Unclear How these two values are set, and whether a user or administrator can set them, is not stated.

What

An agent is a helper Claude Code runs on a task. It can run in the foreground, where you watch it, or in the background. This release adds controls over that:

  • admitMove: a new check that lets a backgroundLaunchRule refuse to move a foreground agent to the background. If the rule throws an error or returns something other than true or false, the agent stays in the foreground and Claude Code logs "A foreground agent was not moved to the background".
  • foregroundAgentMovesAdmitted: a new policy getter about moving agents from the foreground to the background.
  • messagingBeyondOwnAgentsDisabled: a new policy getter about agents messaging other agents beyond their own.

The existing backgroundLaunchRule and backgroundCompletionNoticeDisabled getters are kept.

Why

Software that embeds Claude Code, or an organization's policy, can now restrict when agents move to the background and possibly which agents they can message. If an agent refuses to move to the background, a rule like this may be the cause.

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 doubtHow these two values are set, and whether a user or administrator can set them, is not stated.

See this entry in the whole of v2.1.296 →

Feedback