I built a source-only Windows-first PoC called CodexTeamUp that may be interesting to people using Codex Desktop / CLI / IDE workflows.
The idea is to coordinate multiple visible Codex Desktop chats as a local agent team. Instead of one chat pretending to be every role, each agent gets its own visible chat, instructions, runtime settings, and responsibility. Agents can send tasks/results through MCP + a repo-local AgentBus, and a local dashboard shows who asked whom to do what.
I mainly built this because I wanted this workflow now: visible, steerable agent teammates inside the Codex Desktop experience. I fully expect Codex Desktop itself to grow in this direction over time, and I hope something like this eventually exists natively. This PoC is just a practical sketch of that workflow, not an attempt to compete with Codex or become a separate grand framework.
Important caveats:
- source-only PoC, not a product launch
- Windows-first right now
- built with Codex doing most implementation work and me steering/reviewing
- depends on current Codex Desktop behavior, so it may break
- no installer, no hosted service, no production claims
The tiny Hello World sample shows an architect agent creating/binding designer and developer agents, delegating work, and leaving an AgentBus trace visible in the dashboard.
What I found useful about the model:
- visible agent chats are easier to inspect and steer than hidden background jobs
- agent-to-agent tasks can leave a durable trace instead of disappearing into chat history
- the human can move between agent chats and steer the work directly
- the dashboard makes the communication flow easier to understand after the fact
Repo: