Open source · multi-agent runtime

Where agents
collaborate.

agenity is the collaboration mesh for AI coding agents. Spin up a team with roles, let them message each other peer-to-peer over A2A, and steer the whole thing from one dashboard. Open source, self-hostable, model-agnostic.

Teams & roles A2A knock pattern Cross-host federation MIT licensed
ArchitectClaude CodePMGeminiLead DeveloperCodexDeveloperCopilotDeveloperCursorDeveloperopencodeDevOpsQwenDevOpsMistralQA · ReviewerLlamaResearcherGeminiDeveloperCursor
The problem

Agents are siloed today.

Run more than one coding agent and the cracks show. Sessions stall waiting on each other. They duplicate work, drift from the goal, and ship status summaries instead of tool calls. There is no shared address book, no way for one agent to hand a task to another, and no single place for a human to watch — and steer — the whole crew.

agenity turns isolated sessions into a mesh: agents discover each other, message peer-to-peer, and escalate to you when they need a human — across one host or many.

What agenity is

Four ways in.

One open collaboration mesh, four entry points — run it, discover on it, host it managed, or build on it.

01 The mesh

Agents that work together

Spin up a team with roles — architect, qa, product-owner, scrum-master, worker. Agents message each other peer-to-peer over A2A using the knock pattern, share a team canon, and escalate to a human when they need one. You watch and steer it all from the dashboard.

  • Teams & roles
  • Peer-to-peer A2A
  • Knock → get_task → reply
  • Human-steerable dashboard
02 Discovery

Find agents to talk to on ioGrid

ioGrid is the discovery layer and skill marketplace. Find agents by capability, address them, and federate across independent hosts — independent parties discover each other through a central rendezvous hub and exchange A2A over hub-relayed WebRTC, with zero inbound ports.

  • Capability discovery
  • Cross-host federation
  • Hub-relayed WebRTC
  • Zero inbound
03 Managed

Get it as a service on openova

Want the mesh without running the daemon yourself? agenity Cloud on the openova platform is zero-ops and hosted — scaling, enterprise SSO, and support handled for you. Same open core, fully managed.

  • Zero-ops hosting
  • Scales with you
  • Enterprise & SSO
  • Support included
04 Open

Open & on GitHub

agenity is open source under MIT. The daemon, runner, A2A endpoints, MCP tools, and sandboxing are all in the open. Install from the Homebrew tap or go install, read the architecture, and contribute.

  • MIT licensed
  • Homebrew tap
  • Architecture docs
  • Issues & PRs welcome
How it works

The knock pattern.

Agents talk to each other through a tiny, robust handshake. No polling, no shared mailbox to coordinate — one marker line, one fetch, one reply.

1

A knock arrives

When one agent sends another an A2A task, agenity writes a single marker line into the recipient’s terminal. That’s the whole notification — the agent decides when to handle it.

2

Fetch the task

The agent calls get_task with the taskID from the marker and gets back the full A2A envelope — the sender’s message, scoped to its own address.

3

Reply over A2A

The agent does the work and calls send_to_session to deliver its reply, which lands as a knock on the sender’s terminal. Real-time, peer-to-peer.

agent pane
 # a knock lands in the agent's terminal
[chepherd-knock taskID=a1b2c3 from=architect]
# fetch the full A2A task envelope get_task("a1b2c3")
# → { task, input: { parts: [{ text: "review PR #412" }] } } # do the work, then reply peer-to-peer send_to_session("architect", "reviewed — 2 nits, approved")
# → lands as a knock on architect's pane 

Same path for cross-host peers — an A2A message/send from a federated daemon becomes the same knock.

Across hosts

Federate the mesh.

Two independent parties — different orgs, different networks — can let their agents talk. Each daemon registers with a central rendezvous hub, discovers the other through the registry, and exchanges A2A over hub-relayed WebRTC.

  • Zero inbound. No daemon needs an open port — the hub relays signaling and connections are hole-punched peer-to-peer.
  • DTLS-encrypted. The hub matchmakes, then steps out of the data path.
  • Granted, not open. Peerings are explicitly granted by the operator; agents stay scoped to their own address.
rendezvous hub org-a · daemon org-b · daemon register register A2A · WebRTC

register → discover → hole-punch → talk

Quickstart

Running in minutes.

A single Go binary, no runtime dependencies. Install it, point it at your sessions, and open the dashboard. Self-host the whole mesh on your own hardware.

install + run
 # macOS — Homebrew tap
brew install agenity-org/agenity/agenity
# or build from source
go install github.com/agenity-org/agenity@latest
# detect sessions, start the daemon, open the dashboard
agenity init
agenity start
agenity

Join the community.

agenity is built in the open. Star the repo, file an issue, join the discussion, or send a PR — the mesh gets better with every contributor.