kxm is by kontextmind — not by us.
We indexed this project so people can find it. We are not selling it, we host no copy of the code, and we are not affiliated with or endorsed by its authors — get it from them.
Indexed Oct 5, 2026 · 2 stars at index time. Maintainers: claiming verifies your identity and unlocks a higher assurance tier. Removal requests are honored.
AI agent · for humans & their agents
kxm
unclaimed listingactively maintainedFreeMIT
Pi extensions for multi-agent communication and orchestration
by Open Source Community · New publisher
Pi extensions for multi-agent communication and orchestration
kontextmind/kxm is an open-source project by kontextmind: Pi extensions for multi-agent communication and orchestration. Indexed here so it can be found — not resold.
It is free. Get it from the upstream repository: https://github.com/kontextmind/kxm
From the project's own README (excerpt, reproduced for discovery under its MIT license):
KXM
KXM gives coding agents (Claude Code, Pi and other harnesses) a durable, authenticated message and workflow plane, so they can delegate bounded work to each other and prove who answered, without sharing one giant context.
KXM runs on your machine: one kxm CLI, a local hub for messages and webhook workflows, and a local Runtime for workflow runs. Your project is reviewable YAML in Git, every agent keeps its own context and its own safety controls, and the docs say plainly what KXM does not guarantee (Status and limits).
What makes KXM different • Durable messages, not chat. Every request is a SQLite record that moves from queued to delivered to replied, survives hub and agent restarts, and deduplicates retries by idempotency key. Agents authenticate with a project token and see only their own project's peers. Message peer agents • Provenance you can check. A quorum gate counts only replies the hub itself routed, from distinct eligible peers, for the exact run, stage and attempt. Text a coordinator writes never counts. It proves who answered, not that the answer is right. Peer provenance and quorum gates • Workflows that release the turn. Signed Jira, GitHub or generic webhooks start durable runs. A coordinator can park a stage, give up its turn, and resume only when a signed CI, review or merge callback arrives. Run webhook workflows • Local-first and reviewable. The project lives in .kxm/.yaml. kxm trust diff lists every permission expansion, and kxm trust check fails on any expansion beyond the base revision. kxm run executes workflows in an event-sourced Runtime that works with the hub down and ends each drive with a receipt it verifies. Architecture • Native harnesses, fail-closed auth, honest cost. Before a live run dispatches, KXM checks that the…
01Capabilities
Does
- No capabilities recorded
Doesn’t
- No exclusions declared
02Requirements & stack
Depends on
No declared dependencies
Credentials needed
None declared
Stack
03Community
No endorsements yetNo verified confirmations yet — be the first.
Confirmations come from verified purchasers, installers, vetted reviewers, or an installation outcome your org reported through the agent tools. They grade quality — security is verified separately, and community votes can never override the security gate.
Sign in to confirm — weight comes from verified usage, not vote count.
Issues 0
Open an issueNobody has reported anything yet — a success counts as a report too.
04Trust Passport
Full passport →0/0 automated components pass. An automated score is never a security guarantee.
This listing is unclaimed, so publisher identity cannot be verified and it stays below the “verified” tier by design — that is a statement about the listing, not about the project’s quality. Our automated scans still ran; a maintainer who claims it unlocks identity verification.
05Versions
Full history →| Version | Channel | Released | Notes |
|---|---|---|---|
| 0.0.0 | stable | Oct 5, 2026 | Indexed listing — see the upstream repository for real release history. |