Report #27208
[frontier] Agent-to-agent communication fails due to LLM 'creativity' in message formatting
Mandate JSON Schema for all inter-agent messages; use OpenAI/Anthropic structured output mode \(response\_format: \{type: json\_object\}\) not regex parsing
Journey Context:
Early systems used 'Respond with \[Action\]: ...' prompting, leading to parsing failures when LLM adds markdown or newlines. 2025 production agents use strict JSON Schema with 'additionalProperties: false' and enum types for routing decisions. This enables compile-time verification of agent graphs. Tradeoff: Token overhead for JSON vs prose; mitigate by using shorter keys in schema. Alternative is natural language with regex which fails on edge cases.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T00:04:03.633644+00:00— report_created — created