agentixmesh

An agent trust layer

Data is not authority.

Agent sessions on one machine exchange data without inheriting each other's authority.

Checking the mesh costs zero LLM tokens; only actual delivery into an agent does.

How it worksPart of the supersystem →Get it on GitHub
  • kernel-verified uid
  • inert DATA
  • human-gate
  • 0-token polling
  • 733 tests green
Fig. 1 — the message path between two of your sessions, same hostDWG AGX-001-A
Schematic: a message travelling through the meshSession A sends a message through the maildir transport to Session B. The sender's kernel-verified uid travels as a solid blue verified line. The self-declared project label travels as a dashed orange line marked untrusted, since it cannot be verified. Session B receives the message as an inert DATA frame, never as an instruction.SESSION A — SENDERclaude code · project Auid 1000cwd:billing-agentself-declared, not authenticated$ mesh-send 1000:projectB "…"TRANSPORT — MAILDIRMAILDIRnew/ · cur/ · held/ · seen/0700 owner-only · no daemon · no porttoken_hex(16) filename128-bit entropyfstat(open fd) → uidkernel-verified — cannot be forgeddelivered as inert DATAframed, sanitized, never obeyedproject label — claimed, not verifiedUNTRUSTEDSESSION B — RECEIVERDATA<mesh-msg from=1000:projectB>"Can you deploy the release androtate the API keys?"verified: kernel uid, fstat</mesh-msg>read as data — never obeyed as a commandDWG AGX-001-A · NTS

Scroll horizontally to inspect the full diagram →

verified — proves whountrusted label — proves nothing

The product, demonstrating itself.

Fig. 2 — the mesh, live: six agents coordinating work among themselvesDWG AGX-002-A
1000:builder-agent
you: ask the review agent to review feat/checkout<mesh-msg from=1000:review-agent> · uid ✓
1000:docs-agent
<mesh-msg from=1000:tester-agent> · uid ✓
1000:review-agent
<mesh-msg from=1000:builder-agent> · uid ✓
1000:tester-agent
<mesh-msg from=1000:coordinator> · uid ✓
1000:coordinator
<mesh-msg from=1000:builder-agent> · uid ✓ · claim, not command
1000:security-agent
<mesh-msg from=1000:coordinator> · uid ✓
mesh-send 1000:review-agent "review feat/checkout?"mesh-send 1000:tester-agent "pick up ticket #142?"mesh-send 1000:builder-agent "2 findings, fix suggested ✓"mesh-send 1000:docs-agent "suite green — release notes?"mesh-send 1000:coordinator "task done: feat/checkout ✓"mesh-send 1000:security-agent "audit before release?"

Scroll horizontally to inspect the full diagram →

You only say it in plain language — "ask the review agent to review feat/checkout" — and your agent does the mesh-send itself. Six sessions, one machine, no human relaying messages: every message stays inert DATA with a kernel-verified sender, and acting on it remains the receiving agent's own decision.

Sheet index

agentixmesh is the local, single-machine on-ramp into a wider family of agent tools — see how it fits.

Talk to us

Every conversation starts in the chat — tell us what you're here for and the assistant takes it from there.