{"version":"2.1.222","anchor":"agent-to-agent-messaging-gets-a-classifier-review-path","canonical_anchor":"agent-to-agent-messaging-gets-a-classifier-review-path","heading":"Agent-to-agent messaging gets a classifier review path","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222\/e\/agent-to-agent-messaging-gets-a-classifier-review-path","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222","markdown":"### Agent-to-agent messaging gets a classifier review path\n\nMessaging another agent may now require classifier review instead of being automatically allowed.\n\n**What**\n\nThe tool for messaging another agent no longer auto-allows in every permission mode; in some modes it defers to classifier review.\n\n**Details**\n\n- The permission check can now return a passthrough behavior with a message stating that classifier review is required.\n- Recipient names must match a single-line pattern.\n- Over-long summaries are truncated rather than rejected outright.\n- The classifier input string now carries the summary, shutdown reason, request id and plan feedback.\n\n**Evidence**\n\n`Message to another agent requires classifier review.`\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}