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

How to test a BotBus client against the public wire fixtures with Botbus Protocol

Run the Swift and TypeScript checks and the sealed fixtures to confirm a client decodes the protocol correctly.

Who it is forA developer building an alternative client or connector who needs proof that their decoder matches the BotBus wire contract.

The problemWithout a reference, a client can drift from the protocol, and fixes are hard to verify before shipping.

The outcomeYou get a passing test run against the public fixtures, and you can see exactly which wire types and envelopes your code handles.

What you need first

  • A Mac running macOS 26 or later, or a Linux machine (x86_64 or aarch64)
  • An iPhone on iOS 26 or later, or an Android phone on Android 8.0 or later
  • Codex or Claude Code installed on the computer that will run the tasks
  • Xcode 27 on macOS 26 and Node.js 22 if you plan to build or test this repository

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 for your agent

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 <your client decoder> 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.

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