Regression: encrypted MultiAgentV2 messages remove readable task audit trail
### What version of Codex CLI is running? Upstream `main` after #26210 (`Encrypt multi-agent v2 message payloads`, merged 2026-06-05). This appears to affect versions that include that change and enable MultiAgentV2 (post-0.137.0). ### What subscription do you have? Not subscription-specific. ### Which model were you using? Not model-specific. This concerns MultiAgentV2 `spawn_agent`, `send_message`, and `followup_task` message handling. ### What platform is your computer? Not platform-specific. ### What terminal emulator and version are you using (if applicable)? Not terminal-specific. ### Codex doctor report Not applicable. The regression is visible from the merged code behavior in #26210 rather than from local environment state. ### What issue are you seeing? #26210 makes MultiAgentV2 agent task/message payloads opaque to Codex by marking the model-facing `message` parameter as encrypted, storing only `InterAgentCommunication.encrypted_content`, and leaving `InterAgentCommunication.content` empty. The encrypted delivery path is understandable as privacy hardening, but it also removes the human-readable task/message text from local rollout history, trace reduction, and parent-side audit/debug surfaces. That makes it difficult to answer basic questions such as: - What task did this `spawn_agent` call give the child agent? - What message was sent to a subagent? - Why did a child thread exist when reviewing a rollout after the fact? This is different from #2675
Posted by ignatremizov on Jun 13, 2026, 8:06 AM
Tags
Related issues
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
ux (Healthcare)
I've dabbled in both Garage and RustFS.
Regression: encrypted MultiAgentV2 messages remove readable task audit trail
Prevalence of the disease - if it only impacts 1/100 million, going to be hard to ever find sufficient patient population to test an...
Regression: encrypted MultiAgentV2 messages remove readable task audit trail
### What version of Codex CLI is running? Upstream `main` after #26210 (`Encrypt multi-agent v2 message payloads`, merged 2026-06-05). This appears to affect versions that include that change and enable MultiAgentV2 (post-0.137.0). ### What subscription do you have? Not subscription-specific. ### Which model were you using? Not model-specific. This concerns MultiAgentV2 `spawn_agent`, `send_message`, and `followup_task` message handling. ### What platform is your computer? Not platform-specific. ### What terminal emulator and version are you using (if applicable)? Not terminal-specific. ### Codex doctor report Not applicable. The regression is visible from the merged code behavior in #26210 rather than from local environment state. ### What issue are you seeing? #26210 makes MultiAgentV2 agent task/message payloads opaque to Codex by marking the model-facing `message` parameter as encrypted, storing only `InterAgentCommunication.encrypted_content`, and leaving `InterAgentCommunication.content` empty. The encrypted delivery path is understandable as privacy hardening, but it also removes the human-readable task/message text from local rollout history, trace reduction, and parent-side audit/debug surfaces. That makes it difficult to answer basic questions such as: - What task did this `spawn_agent` call give the child agent? - What message was sent to a subagent? - Why did a child thread exist when reviewing a rollout after the fact? This is different from #2675
Comments (0)
No comments yet. Start the discussion.