Skip to content

About

An open kit for groups whose AI agents work toward one goal together, with every decision signed by a person.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

1 star

Watchers

0 watching

Forks

CoalitionKit

An open kit for groups whose AI agents work toward one goal together, with every decision signed by a person.

CI License: Apache 2.0 Python 3.12 or newer Status: pre-release

CoalitionKit in one view: rooms on a map, a room composed from one sentence, joining with a QR code, agents working together, plans to choose from, and results that show their sources

You say what needs doing in one sentence. Everyone joins with their own agent, from any vendor. The agents ask their people a few private questions, make offers and compare free times without showing them. The room lays out plans, and nothing binds anyone until that person signs it with a press and hold.

These are real screens from real rooms on real models. The rooms on the map are samples, and are marked as samples. The catalog pages use example data.

Generative UI, from a closed catalog

Models compose the screen, and code decides what is allowed

The screens in a room are not templates. A model composes them as you go, as A2UI trees streamed over AG-UI:

  • From one sentence, it chooses the components for your room: a map, seats, a calendar, costs, a route.
  • When an agent asks its person something, it picks the input that fits: time slots for dates, a slider for money.
  • When work is done, it lays out the result as a card that names the signed events it came from.

A generated screen is also a place where a tricked model could show something false, so the model only chooses. It picks from 201 components in 11 families, and the host checks every tree before it reaches a browser. There is no HTML and no script. Every number points at a real event. And a tree can never answer a consent, so a screen can never sign for you.

Try it

You need uv and Node 22 for the web room. To compare free times privately, also install libsodium (apt install libsodium23 on Debian or Ubuntu, brew install libsodium on macOS).

git clone https://github.com/HeshamFS/coalitionkit
cd coalitionkit
uv run coalitionkit up

The first run builds the web room, which takes a minute or two. Then open the address it prints, and say what needs doing in one sentence.

No model key is needed: without one, the room runs on fixed rules and says so. Set COALITIONKIT_META_API_KEY for real models. In our test runs, a room of two or three people cost about $0.10 to $0.25 in model calls. See Your first room.

What is in it

Any agent can join Over MCP from a tool you already use, or over A2A with its own signed card. There are example members on Google ADK and LangGraph
People decide An agent can never commit you. Consent is signed with your own key, on a screen no model can draw
Private by design Your vault answers narrow questions only, and free times are compared with private set intersection
An independent checker The Steward runs fixed policies, then a model audit on a different model, before a message reaches anyone
A record you can check One signed, hash-linked log per room, with receipts, which your own browser can verify
Screens from a closed catalog Models compose from 201 checked components, never HTML, and every number points at a real event
Fair plans from fixed rules Plans come from code. The model only explains them
Plans can change Say what happened, and a ripple reopens only the tasks it touches
More than a browser People can also take part over WhatsApp or a glasses view
Teach it your field A Discipline Pack is a folder of data: words, roles, schemas, policies and tests. It cannot run code in the host

How it fits together

flowchart LR
    P1[Person and<br/>hosted agent] -- browser --> H
    P2[Person and<br/>their own MCP agent] -- MCP --> H
    B[Outside agent<br/>with a signed card] -- A2A --> H
    H[Host<br/>signed log, scopes, consent]
    H <--> G[Gardener<br/>plans by fixed rules]
    H <--> S[Steward<br/>policies, then a model audit]
    P1 -. private set intersection .- B
    H -- a live view per viewer --> V[The Table]
Loading

The host orders one log per room and gives each viewer only what their scope allows. The protocol is an extension of A2A 1.0.

Docs

The docs are online at coalitionkit.dev.

Version 0.1 is a pre-release. The protocol is a draft and will change, and the kit has had no outside security audit.

Packages

Package What it does
contracts Envelope, receipt and consent types, schema validation, signing, scope resolution
runtime CoalitionHost: the signed log, lifecycle rules, a view per viewer, SQLite or PostgreSQL
edges A2A transport: agent cards, the member client, the extension on the wire
vault Each member's private data, answered only by typed queries and private set intersection
steward The independent checker
gardener Deterministic planning from needs and offers
server The reference host: the room engine, A2A, MCP, the live feed, admin routes, WhatsApp
mcp_server The MCP tools and the MCP App view
surfaces The live feed, the agent stream and validated A2UI screens
channels Message channels, starting with WhatsApp
mint Turns a short video and a voice note into a policy-checked MCP server for a shared resource or device
models The model gateway, media client, price table and cost meter
packs Discipline Packs: loaded, validated and signed as data
conformance The black-box conformance runner
acceptance Whole-journey acceptance tests
cli The coalitionkit command
langchain A room's actions as LangChain tools
langgraph A graph as a seat, with an interrupt where a person must consent
apps/web The web room and the glasses view

Develop

uv sync
uv run python tools/check.py          # lint, types, import boundaries, tests, the core rule
npm --prefix apps/web ci && npm --prefix apps/web test

Live tests run only with COALITIONKIT_LIVE=1 and a key, and are reported as not run otherwise. See CONTRIBUTING.md.

Built during the Meta Global AI Developer Hackathon

All of this repository was built during the event's building period, October 27 to November 4, 2026. Its first commit is dated October 28, and the history shows the rest.

It runs on Meta's models: Muse Spark for the agents, Muse Spark Open on Baseten for the Steward's audit.

License

Apache 2.0. See LICENSE and NOTICE.

About

An open kit for groups whose AI agents work toward one goal together, with every decision signed by a person.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages