| name | polis-protocol |
| description | Coordinate multi-vendor AI agents as a self-improving team — a learning router assigns work by track record and citizens can amend the protocol's own rules. |
| category | orchestration |
| risk | critical |
| source | community |
| source_repo | yehudalevy-collab/polis-protocol |
| source_type | community |
| date_added | 2026-06-02 |
| author | yehudalevy-collab |
| tags | ["multi-agent","coordination","routing","orchestration","governance","vendor-agnostic"] |
| tools | ["claude","cursor","gemini","codex","antigravity"] |
| license | MIT |
| license_source | https://github.com/yehudalevy-collab/polis-protocol/blob/main/LICENSE |
| plugin | {"targets":{"codex":"blocked","claude":"blocked"}} |
Polis Protocol — a team of agents that develops
Overview
Most agent coordination is a passive board: claim a task, do it, mark it done. It records, but it never gets smarter, and its rules are frozen. Polis Protocol is the active alternative — a folder of markdown where each agent is a "citizen" with a capability card, work is routed by a learning bandit to whoever has the best track record on the task's tags, settled work files lessons that update the routing, and citizens can propose and vote on amendments to the protocol itself. It is vendor-agnostic: Antigravity, Claude, Codex, and Gemini agents can all share one _polis/.
In Antigravity specifically, this turns Manager View's fixed pipeline into a team that learns who is actually best at each kind of work, instead of running the same roles in the same order every time.
When to Use This Skill
- Use when 2+ agents (especially across vendors) work on one project and "who should do this" is a real question.
- Use when you want the team to measurably improve over time — routing that adapts from outcomes, not static role labels.
- Use when you need a durable, git-auditable record of who did what, what was learned, and which rules changed.
- Use when Antigravity's default orchestration is too rigid and you want routing + governance on top of it.
How It Works
Step 1: Found a polis
Use a reviewed checkout by default so the scaffolder code is pinned before it writes into the project:
git clone https://github.com/yehudalevy-collab/polis-protocol.git
cd polis-protocol
git checkout <reviewed-commit-sha>
python3 scripts/init_polis.py \
--project-root . \
--agent-id gemini-antigravity-yourproject \
--vendor google --model gemini-3 --tool antigravity
If you prefer the published PyPI package, install an exact version after reviewing that release, for example pipx install polis-protocol==<reviewed-version>. Do not invoke the package through an unpinned uvx or "latest" workflow for automated setup.
This writes _polis/ plus the skill into .agents/skills/ (the path Antigravity reads), and bridge pointers (GEMINI.md, AGENTS.md) that point every tool at _polis/CONSTITUTION.md. Tip: add --dry-run to preview every file before anything is written; init never overwrites existing files, and polis init --repair restores missing ones.
Step 2: Register citizens and open contracts
Each agent publishes a capability card under . Work is opened as a contract with , not assigned to a fixed role.
