Durable, addressable messaging between agents: git inbox or atproto permissioned space, one delivery contract
README.md

agent-messenger #

Durable, addressable messaging between agents, across hosts and backends. Two transports behind one delivery contract; a project picks one:

  • git inbox — one file per message on an inbox branch of a repository; a push to a Tangled knot emits sh.tangled.git.refUpdate on the knot's event stream, so the listener reacts in about a second without polling (polling is the fallback for forges without such a stream).
  • atproto permissioned space — a page.lichen.agent.message record (CAS-shaped) written into the project's space by the sender's DID; Habitat's SAP syncs the space and the listener reads its /channel outbox websocket.

agent-messenger is a Go binary, independent of agent-orchestrator; the orchestrator will run it (listen, send, mark-delivered) as its transport once this works on its own. Start with PLAN.md, then docs/DELIVERY-CONTRACT.md. The full discussion, the alternatives considered and every measured fact are in docs/DESIGN-NOTES.md; naming in docs/NAMING.md.