{"version":"2.1.323","anchor":"plan-approval-mismatch-feedback-reworded-and-now-names-the-e","canonical_anchor":"plan-approval-mismatch-feedback-reworded-and-now-names-the-e","heading":"Reworded message when a team lead's reply does not match a plan","tier":"notice","area":"Agent Teams","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/plan-approval-mismatch-feedback-reworded-and-now-names-the-e","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Reworded message when a team lead's reply does not match a plan\n\nWhen a team lead's answer does not match a plan request, the agent now hears it was not used and is told to resubmit the plan\n\n**What**\n\nIn agent teams, several Claude agents work together, and a team lead can approve or reject a member's plan. When the lead's reply is for a different request, the member is now told: \"The team lead's answer did not match this plan request, so it was not used.\" It is then told to call the plan tool again to resubmit. That tool, `ExitPlanMode`, is now named by its current name rather than written into the text.\n\nThe old message said the lead's verdict was for a different request and told the agent to call ExitPlanMode again.\n\n**Why**\n\nA team member gets a clearer account of why its plan was not approved and what to do next.\n\n- Area: Agent Teams\n- Names: `ExitPlanMode`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}