My regular workflow is to run code agents in Tmux panes and often I have Claude Code consult/collaborate with Codex, using my tmux-cli [1] tool, which is a wrapper around Tmux that provides good defaults (delay etc) for robust sending of messages, and waiting for completion etc.

[1] https://pchalasani.github.io/claude-code-tools/tools/tmux-cl...

Claude Code (subscription) has Agent Teams built in. Teams of Agents communicate with local files that they use as inboxes and task list. Has tmux and iTerm 2 integration. https://code.claude.com/docs/en/agent-teams

They can rack up some extra tokens if you leave agents going idle. Because they loop, checking for new messages for them.

This fellow reverse-engineered exactly how it works and then abstracted the pattern into an MCP server that any Harness/agent can use. https://github.com/cs50victor/claude-code-teams-mcp

Have you seen https://www.roborev.io/ from Wes McKinney?

> use the subscription plans you already have, avoid paying for API usage, and keep the setup simple enough that you can try it in a few minutes.

That interested me, but the article does not explain how to do this at all. I was hoping it would tell how use my work's ChatGPT Pro subscription via the CLI without having to pay per token over their API.

I put together a skill to do this with OpenCode and the GitHub Copilot provider. Works pretty well.

I’ve been keeping them open in tmux and using either send_keys or paste buffer for communication. Using print mode and always resume last means you can’t have parallel systems going.

In Cursor or OpenCode is very easy, just change the LLM in the same conversation.

[dead]

[dead]

[dead]

[dead]