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

How to run the provider-free coordination demo with Peerbridge MCP

Run the synthetic demo and check the receipt for writer lease, quorum, and audit results.

Who it is forA maintainer or evaluator who wants proof that the coordination core blocks overlapping writers before trusting it with real agents.

The problemClaims about write leases, peer review quorum, and audit chains are hard to judge from a README alone.

The outcomeA public receipt showing an overlapping second writer was rejected, two reviewers met quorum, completion rehashed the artifact, and the audit chain verified.

What you need first

  • Python installed for the source demo and source installation
  • A local Git repository for worktree-based work
  • Windows x64 for the portable Alpha 6 ZIP build
  • Agent clients or provider accounts you already use, such as Codex or Claude Code, for live runs

Steps

  1. git clone https://github.com/Hoylon/peerbridge-mcp (inferred, check the README)
  2. cd peerbridge-mcp (inferred, check the README)
  3. python examples\demo_workflow.py --workspace demo-workspace --scope demo
  4. Read the printed receipt and confirm the overlapping writer was rejected and the audit chain verified with zero writes.

Prompt for your agent

Clone the Hoylon/peerbridge-mcp repo and run examples\demo_workflow.py with --workspace demo-workspace and --scope demo. Report the receipt, and verify that it shows the overlapping second writer rejected and the audit chain verified.

Caveat. The project is alpha and the public API and database schema may change before 1.0, so treat the demo as evaluation, not a production guarantee.

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