{"version":"2.1.296","anchor":"policy-getters-for-agent-messaging-and-foreground-to-backgro","canonical_anchor":"policy-getters-for-agent-messaging-and-foreground-to-backgro","heading":"New controls over moving agents to the background and over agent messaging","tier":"internal","area":"Agent Messaging","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/policy-getters-for-agent-messaging-and-foreground-to-backgro","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### New controls over moving agents to the background and over agent messaging\n\nA `backgroundLaunchRule` can now veto moving a foreground agent to the background, and new policy getters cover agent moves and cross-agent messaging\n\n**Unclear.** How these two values are set, and whether a user or administrator can set them, is not stated.\n\n**What**\n\nAn 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:\n\n- `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\".\n\n- `foregroundAgentMovesAdmitted`: a new policy getter about moving agents from the foreground to the background.\n\n- `messagingBeyondOwnAgentsDisabled`: a new policy getter about agents messaging other agents beyond their own.\n\nThe existing `backgroundLaunchRule` and `backgroundCompletionNoticeDisabled` getters are kept.\n\n**Why**\n\nSoftware 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.\n\n- Area: Agent Messaging\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 4\/5\n- Scope: both\n- Heads-up: no"}