# AI use cases for Flopwire (flopwire/flopwire) Repo: [flopwire/flopwire](https://github.com/flopwire/flopwire) | Use cases: 4 | Page: https://dedupedai.com/use-cases/flopwire-flopwire/ Flopwire is an open source, self-hostable tool that lets AI agents message each other and search shared history of their past and live sessions across harnesses, machines, and teammates. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Trace a commit back to the agent session that wrote it: https://dedupedai.com/use-cases/flopwire-flopwire/trace-commit-to-agent-session/ - Search every past agent session for an earlier decision: https://dedupedai.com/use-cases/flopwire-flopwire/search-past-agent-sessions-for-decisions/ - Have two agents on one machine agree a work split: https://dedupedai.com/use-cases/flopwire-flopwire/coordinate-two-agents-on-one-repo/ - Set up a self-hosted team server for shared agent history: https://dedupedai.com/use-cases/flopwire-flopwire/run-a-team-archive-for-shared-agent-history/ ## How to trace a commit back to the agent session that wrote it with Flopwire Repo: [flopwire/flopwire](https://github.com/flopwire/flopwire) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README Find the session behind a commit and read the command and result evidence it produced. **Who it is for:** A developer reviewing an unfamiliar commit made with an AI agent who needs to know why the change was made. **The problem:** The commit message says what changed but not the reasoning, and the original agent session is hard to find among many past chats. **The outcome:** The reviewer gets the session that produced the commit, with its command and result evidence, and can read the conversation behind the change. ### Steps 1. Run `curl -fsSL https://flopwire.com/install.sh | sh` to install the Flopwire binary. 2. Run `flopwire setup` to configure supported harnesses detected on PATH. 3. Run `flopwire agent run` and keep it running so this machine's transcripts get indexed. 4. Run `flopwire trace ` with the full commit ID to get the session that produced the commit. (inferred, check the README) 5. Open the returned session with `flopwire read` or the `flopwire_read` tool to read the conversation behind the change. (inferred, check the README) ### Prompt to paste into your agent ```text In the flopwire/flopwire repo context, run the trace command for the full commit ID and report the session ID and the command and result evidence it returns. Verify that the session ID appears in `flopwire sessions --repo . --since 30d`. ``` ### Caveat Trace only works on transcripts the device agent has indexed, so it needs the agent running and path rules that allow the repository. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/flopwire-flopwire/trace-commit-to-agent-session/ ## How to search every past agent session for an earlier decision with Flopwire Repo: [flopwire/flopwire](https://github.com/flopwire/flopwire) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README Use regex and ranked search to recover how a problem was solved in a previous session. **Who it is for:** A developer or agent starting a task that may have been tackled in an earlier session, such as an error pattern or a design choice. **The problem:** Earlier attempts and decisions are scattered across many single-session chat histories that the harness does not search together. **The outcome:** The user or agent finds the matching sessions, with the user, device, harness, and session named for each hit, and reads the relevant passage. ### Steps 1. Run `curl -fsSL https://flopwire.com/install.sh | sh` to install the Flopwire binary. 2. Run `flopwire setup` to configure supported harnesses detected on PATH. 3. Run `flopwire agent run` and keep it running to index this machine's transcripts. 4. Run `flopwire grep 'exit (code|status) [1-9]' --since 24h` to find matching lines across every session, or replace the pattern with your own. 5. Run `flopwire search 'how did we handle rate limits?'` for ranked keyword results, then `flopwire read` on a hit to see the passage. (inferred, check the README) ### Prompt to paste into your agent ```text Use the flopwire/flopwire CLI to search all indexed sessions for with `flopwire search ''`. Report the top three hits with user, device, harness, and session for each, and confirm each hit by reading its passage with `flopwire read`. ``` ### Caveat Search covers only transcripts from supported harnesses that the device agent indexes under your path rules, so sessions in excluded paths will not appear. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/flopwire-flopwire/search-past-agent-sessions-for-decisions/ ## How to have two agents on one machine agree a work split with Flopwire Repo: [flopwire/flopwire](https://github.com/flopwire/flopwire) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README Let a Codex session find a Claude Code session on the same repo and message it directly. **Who it is for:** A developer running two agent sessions in the same repository at once who needs them to avoid overlapping work. **The problem:** Parallel agent sessions cannot see each other, so they duplicate effort or make conflicting changes. **The outcome:** Each 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. ### 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 to paste into your agent ```text Run `flopwire peers` in the flopwire/flopwire context and list the live sessions on this machine. Send to the session with `flopwire send -- ""`, 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. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/flopwire-flopwire/coordinate-two-agents-on-one-repo/ ## How to set up a self-hosted team server for shared agent history with Flopwire Repo: [flopwire/flopwire](https://github.com/flopwire/flopwire) | Difficulty: Advanced | Time: 90 minutes | Basis: From the README Join every teammate's devices into one searchable archive on a server you run. **Who it is for:** A team lead or platform engineer who wants all members' agent sessions searchable together on infrastructure they control. **The problem:** Each developer's agent history stays on their own machine, so the team cannot search or reuse what others learned. **The outcome:** The team has one server, teammates enroll their devices, and searches span connected machines and team members. ### Steps 1. Run `git clone https://github.com/flopwire/flopwire && cd flopwire` and then `cp .env.example .env`, replacing every example secret. 2. Run `docker compose up -d --wait` to start Postgres, object storage, and the server. 3. Run `docker compose exec -T flopwire flopwire fingerprint` to print the server fingerprint, then run `docker compose exec -it flopwire flopwire bootstrap --server https://flopwire.example.internal:8080 --fingerprint --name 'Ada Admin' --email ada@example.com` to create the first administrator. (inferred, check the README) 4. Run `flopwire invite --email teammate@example.com` and send the printed invite string over a channel you trust. 5. Have the teammate run `flopwire claim --invite '' --name 'Teammate'` and then `flopwire enroll --name laptop`. (inferred, check the README) ### Prompt to paste into your agent ```text In the flopwire/flopwire repo, follow docs/two-laptop.md to start the team server and verify with `docker compose exec -T flopwire flopwire fingerprint` that it prints a sha256 fingerprint. Report the server address and the fingerprint, and confirm that `flopwire login` works for . ``` ### Caveat The server always serves TLS, and the README says to read SECURITY.md before deploying a team server, since every member can search the whole organization's archive. Risk, credentials: Secrets are redacted only by pattern, so any secret the patterns miss is stored as written and visible to every team member in the archive. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/flopwire-flopwire/run-a-team-archive-for-shared-agent-history/