# AI use cases for Botbus Protocol (botbus-io/botbus-protocol) Repo: [botbus-io/botbus-protocol](https://github.com/botbus-io/botbus-protocol) | Use cases: 4 | Page: https://dedupedai.com/use-cases/botbus-io-botbus-protocol/ BotBus Protocol is the public wire contract, Swift connector code and test fixtures behind the BotBus apps, which let you follow and approve Codex and Claude Code tasks from your phone and watch. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Approve Codex and Claude Code requests from your phone: https://dedupedai.com/use-cases/botbus-io-botbus-protocol/approve-coding-agent-requests-from-phone/ - Review agent screenshots, previews and changes on your phone: https://dedupedai.com/use-cases/botbus-io-botbus-protocol/review-agent-output-on-phone/ - Pair a Linux machine running agents with your phone: https://dedupedai.com/use-cases/botbus-io-botbus-protocol/run-agent-host-on-linux-and-pair/ - Test a BotBus client against the public wire fixtures: https://dedupedai.com/use-cases/botbus-io-botbus-protocol/check-client-against-public-fixtures/ ## How to approve Codex and Claude Code requests from your phone with Botbus Protocol Repo: [botbus-io/botbus-protocol](https://github.com/botbus-io/botbus-protocol) | Difficulty: Beginner | Time: 30 minutes | Basis: From the README Pair your computer with your phone so you can approve commands and answer agent questions away from your desk. **Who it is for:** A developer who starts a long Codex or Claude Code task on their Mac and leaves the room while it keeps running. **The problem:** The agent stops and waits for approval on a command or a question, and nothing moves until you return to the computer. **The outcome:** You see the pending request on your phone or Apple Watch, approve, deny or reply, and the agent continues on your computer. ### Steps 1. Download the BotBus app for macOS from the DMG link on botbus.io and install it on your Mac. 2. Install the BotBus app on your iPhone from the App Store page linked in the README. 3. Open pairing from the Mac menu bar and scan the QR code with your phone. 4. Start a Codex or Claude Code task on your computer, either from BotBus or from your own terminal or IDE. 5. Open the task on your phone and approve, deny or answer the pending request. ### Prompt to paste into your agent ```text Using the BotBus setup described in botbus-io/botbus-protocol, confirm that the Mac app is paired with . Report whether a Codex or Claude Code task on is waiting for a request, and list the request kind and task ID without approving anything. ``` ### Caveat The phone pairing and relay are closed source and not in this repository, so this repo only documents the wire contract the apps use. 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/botbus-io-botbus-protocol/approve-coding-agent-requests-from-phone/ ## How to review agent screenshots, previews and changes on your phone with Botbus Protocol Repo: [botbus-io/botbus-protocol](https://github.com/botbus-io/botbus-protocol) | Difficulty: Beginner | Time: 30 minutes | Basis: From the README Open what an agent built, including dev-server pages and working changes, without going back to your desk. **Who it is for:** A developer or reviewer who wants to check a web app or document an agent produced while away from the computer. **The problem:** Agent output lives on the computer, so checking a page or a set of changes means walking back to it. **The outcome:** You receive screenshots, videos, documents and links on your phone, open dev-server previews, and review the working changes. ### Steps 1. Pair your phone with the Mac app as described in the README. 2. Ask the agent to run its work on a dev server or to produce screenshots or documents. 3. Open the task on your phone and check the artifacts that arrived. 4. Open the dev-server preview from the phone to see the page as it runs. 5. Review the working changes on the phone and send a follow-up if something needs fixing. ### Prompt to paste into your agent ```text Using the BotBus app paired to , list the artifacts and dev-server previews attached to task . Confirm that each item opens on the phone and report anything that does not load. ``` ### Caveat Developer web previews go through a separate proxy and are not end-to-end encrypted, unlike conversations and commands. 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/botbus-io-botbus-protocol/review-agent-output-on-phone/ ## How to pair a Linux machine running agents with your phone with Botbus Protocol Repo: [botbus-io/botbus-protocol](https://github.com/botbus-io/botbus-protocol) | Difficulty: Intermediate | Time: 45 minutes | Basis: From the README Install BotBus on a Linux computer and pair it so agents on that box can be followed from your phone. **Who it is for:** A developer who runs coding agents on a Linux workstation or server and wants the same phone control as a Mac user. **The problem:** The Mac menu bar pairing flow does not apply to a Linux machine, so the agents there are out of reach from a phone. **The outcome:** Your Linux computer is paired, and its agent tasks appear on the phone grouped by computer and project. ### Steps 1. Open the Linux install guide at https://botbus.io/en/docs/install-linux and install BotBus for your architecture, x86_64 or aarch64. 2. Run `botbus pair` on the Linux machine. 3. Scan the QR code shown on the Linux machine with your phone. 4. Start or open a Codex or Claude Code task on the Linux machine. 5. Check that the task is listed on the phone under the Linux computer and its project. ### Prompt to paste into your agent ```text On the Linux host, run `botbus pair` and report the pairing status. Then list the tasks BotBus sees on that host, grouped by project, and note any host that is offline. ``` ### Caveat Actions depend on connector support, task state and whether the computer is online, so an offline Linux host will not show live control. 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/botbus-io-botbus-protocol/run-agent-host-on-linux-and-pair/ ## How to test a BotBus client against the public wire fixtures with Botbus Protocol Repo: [botbus-io/botbus-protocol](https://github.com/botbus-io/botbus-protocol) | Difficulty: Advanced | Time: 1 hour | Basis: From the README Run the Swift and TypeScript checks and the sealed fixtures to confirm a client decodes the protocol correctly. **Who it is for:** A developer building an alternative client or connector who needs proof that their decoder matches the BotBus wire contract. **The problem:** Without a reference, a client can drift from the protocol, and fixes are hard to verify before shipping. **The outcome:** You get a passing test run against the public fixtures, and you can see exactly which wire types and envelopes your code handles. ### Steps 1. Clone botbus-io/botbus-protocol and read PROTOCOL.md for the wire contract. 2. Run `swift build` and then `swift test` on macOS 26 with Xcode 27. 3. Run `npm ci && npm run typecheck && npm test` for the TypeScript side. 4. Point your own decoder at the files in protocol-fixtures/ and compare the results with the expected values. 5. Regenerate sealed vectors only if you change files in plain/, using `npm run seal-fixtures`. ### Prompt to paste into your agent ```text Clone botbus-io/botbus-protocol, run `swift test` and `npm test`, and report the pass or fail count for each. Then decode every file in protocol-fixtures/ with and list any fixture it fails to parse. ``` ### Caveat The fixtures are synthetic samples, and the Relay client and pairing keys are not in this repository, so passing these tests does not prove end-to-end pairing works. 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/botbus-io-botbus-protocol/check-client-against-public-fixtures/