Skip to content

research(orchestration): Codex-style structured inter-agent messaging with path-based addressing #3072

@bug-ops

Description

@bug-ops

Description

Codex CLI v0.118+ introduced multi-agent v2 workflows where sub-agents use readable path-based addresses like `/root/agent_a` with structured inter-agent messaging and agent listing. This enables deterministic routing between agents in a hierarchy, beyond simple parallel task dispatch.

Zeph has orchestration (#2789 tracks parallel read-only subagents) and a DAG planner, but lacks:

  • Named agent addresses in a namespace hierarchy
  • Structured inter-agent message protocol (typed payloads, sender/receiver fields)
  • `/agents` list command to inspect active sub-agent topology at runtime

Reproduction Steps

N/A — this is a research/parity issue.

Expected Behavior

Sub-agents spawned by the orchestrator have stable, human-readable addresses. Messages between agents carry source/destination metadata, making trace logs interpretable. Callers can inspect the active agent graph at runtime.

Actual Behavior

Orchestrator dispatches sub-agents by index/type. No addressable namespace. No structured inter-agent message envelopes. No runtime agent topology inspection.

Environment

Logs / Evidence

From Codex changelog: "Sub-agents now use readable path-based addresses like /root/agent_a, with structured inter-agent messaging and agent listing for multi-agent v2 workflows."

Also relevant: #2789 (parallel read-only subagents), #2434 (AdaptOrch DAG topology).

Metadata

Metadata

Assignees

No one assigned

    Labels

    P4Long-term / exploratoryresearchResearch-driven improvement

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions