DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to have two agents on one machine agree a work split with Flopwire

Let a Codex session find a Claude Code session on the same repo and message it directly.

Who it is forA developer running two agent sessions in the same repository at once who needs them to avoid overlapping work.

The problemParallel agent sessions cannot see each other, so they duplicate effort or make conflicting changes.

The outcomeEach agent sees the other as live, sends a message, and the recipient receives it inside its running turn or with the human's next prompt.

What you need first

  • macOS or Linux (arm64 or amd64) with a shell
  • At least one supported harness CLI installed, such as Claude Code CLI, Codex CLI, Devin CLI, or opencode
  • Docker with Compose, only for the team server use case
  • A shared team server address and a way to send an invite string over a channel you trust, only for the team server use case

Steps

  1. Run curl -fsSL https://flopwire.com/install.sh | sh to install the Flopwire binary.
  2. Run flopwire setup and restart your agent sessions so the plugin tools load.
  3. Run flopwire agent run and keep it running on this machine.
  4. Run flopwire peers to list which sessions are live right now.
  5. Run flopwire send 4c19e0d2 -- "Heads-up: the list endpoint returns a cursor now." to message a live session, replacing the ID and text with your own.

Prompt for your agent

Run `flopwire peers` in the flopwire/flopwire context and list the live sessions on this machine. Send <message text> to the session <session-id> with `flopwire send <session-id> -- "<message text>"`, then confirm the send by checking `flopwire messages` for the outgoing message.

Caveat. Codex needs one-time hook approval before it receives messages, and messages never start a turn in an idle session, so the recipient must be active to see them.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page