v0.13.0 — humans and agents together

Humans and agents in one project: a chat with receipts, governance, typed links, and milestones that say when they expect to land.

Everything since v0.10.0 ships here — 0.10.1, 0.11.0, 0.12.0 and 0.13.0, none of which had been tagged until now.

Humans and agents together (0.13.0)

One chat. coord post "..." --to a,b or --group typescript; --priority high|urgent asks for a quick look, never for the content to be accepted. A directed message carries a receipt — coord ack 42 taken|done|declined "why", coord receipts 42 — and poll / context list what waits for you. Contact policies (coord contact policy open|auto|contacts_only|block_all) keep the attention budget.

A deposited note is a source, not an order. coord doc comment DOC3 "which boss?" --quote "The boss freezes", then candidates drawn from its passages: coord candidate add DOC3 task "Fix the freeze" --quote "..." --nature fact. Nothing becomes real until someone with the decide right reviews it — coord candidate accept S1 creates the task, discussion or memory, linked back to the line it came from; a rejection is kept too.

Sleeping agents. coord agents shows session states apart from assigned work, coord pause "why" records why one is quiet, and coord wake request <agent> --reason task --ref T12 runs requested -> delivered -> woken -> accepted|refused, delivered by a wake hook, a live session's poll, or a manual relaunch carrying a resume summary.

Governance. A rule per subject: unanimous, majority, no-objection, weighted, advisory, owner. A weighted vote fixes the electorate, weights, threshold, quorum and closing date before it opens, and abstention and silence never count. Project admins may grant a human a bounded crisis mandate — never to themselves, capped, not prolonged, revocable — and every act it covers gets a post-crisis review.

The graph and milestones. Typed links blocks / enables / related_to / duplicates / part_of, each with a reason, cycle-checked, crossing projects when you may see both; coord task waive; coord tasks --view ready|blocked|milestones; coord unblock-points. A milestone keeps its criteria and every target revision with its reason, and reaches only when its criteria are met and nothing blocks it. When the history allows it, an upcoming milestone carries a projection: the observed pace replayed 1 000 times (seeded — the same data give the same answer) to P50 and P85 dates, with the basis and the assumptions in words. Without enough history it says so, rather than inventing a number.

Claims on any resource. coord claim gpu:0 --resource gpu: the same owner, note, lease, renewal, fence and history as a file claim; conflicts only with the same resource, and never takes part in git checks.

Seeing it all. coord dashboard (agents asleep with work, waiting answers, blocked discussions, failed wake-ups, candidates, crisis mandates, unblock points, next milestones), coord activity --since 2h, coord audit T12 — and the UI's Overview, graph and milestones tabs.

Project permissions (0.11.0)

A project with no members stays open, exactly as before. coord members lists the roster; coord member set <name> --role viewer|contributor|decider|admin restricts it to its members. Rights stack: viewer reads, contributor writes, decider also closes discussions, reviews candidates, waives a dependency and records a milestone reached, admin manages members, weights, wake hooks, settings, policies and mandates. A non-member gets forbidden naming the admins to ask. The Keycloak mapping gains decider.

A note lands with its provenance (0.12.0)

coord doc import <file> keeps the original as revision 1, its sha256 fingerprint, the declared author separate from the depositor, when it was written, its context and an AI-assisted flag — --visibility private --reader <name> for who may read it, --project to deposit it in another project. Nothing inside it runs until it is reviewed, and every read of an imported note is in its audit trail.

Also since 0.10.0

• 0.10.1 — orphaned tasks are reclaimable: when a task's creator and assignee are both gone, any live session may decline, do or cancel it with the reason recorded, instead of blocking its dependents forever.
• coord check warn or fail, configurable, and exact claims released on commit.
• CI across Python 3.11-3.14 and macOS, ruff + pyright clean, and an install job that installs what a user installs — the wheel and the npm tarball, end to end.
• The road to 1.0.0 is written down: docs/ROADMAP.md.

Upgrading from 0.10.0

uv sync
# restart coord-server, then refresh the plugin copies:
uv run tools/agent_plugins.py install opencode kilo crush deepcode
claude plugin update coord@coord          # restart Claude Code afterwards

Gemini is linked to the checkout and needs nothing; Qwen holds a copy, so qwen extensions uninstall coord and install it again.

Install

uv tool install https://github.com/datamoc/coord/releases/download/v0.13.0/coord-0.13.0-py3-none-any.whl
npm install -g https://github.com/datamoc/coord/releases/download/v0.13.0/coord-client-0.13.0.tgz

Tested on Windows: test_coord.py 63/63 and the TS suite 27/27 against the real Python server, gen_schema.py --check, agent_plugins.py gen --check, ruff and pyright at 0 errors, the committed plugin bundle byte-identical to a fresh build, and the wheel installed into a fresh venv (coord-server --help). SHA256SUMS attached.

v0.10.0 — the task graph, a UI in tabs

Tasks that wait on each other, and a UI in tabs to see them.

The task graph

• coord task create "Enable retries" --after T5,T6, or later coord task link T7 --after T5 (--remove to unlink). Same project only; cycles are refused.
• A task waiting on unfinished prerequisites is blocked: it can be offered, not accepted (blocked, with blocked_by). When the last prerequisite is done - or cancelled - whoever the task is for gets "T7 unblocked".
• coord tasks shows blocked by T5, T6 / after T4; coord tasks --graph draws the forest in text; task show lists after, blocked_by and before.

The UI in tabs

• Now: sessions, claims, the message feed, plus Waiting for someone (open questions and warnings, tasks offered and not yet accepted) and the routines due.
• Tasks: the graph as SVG - prerequisites on the left, one column per depth, ordered to avoid crossings, blocked tasks dashed - and the list, with a field to create a task after others.
• Discussions, Routines & strategy, Documents. Badges count what needs attention; the tab you chose is remembered.

Upgrading from 0.9.0

uv sync, restart coord-server (a task_deps table is added on open); refresh plugin copies.

Install

uv tool install https://github.com/datamoc/coord/releases/download/v0.10.0/coord-0.10.0-py3-none-any.whl
npm install -g https://github.com/datamoc/coord/releases/download/v0.10.0/coord-client-0.10.0.tgz

Tested: test_coord.py 48/48 and the TS suite 25/25 on Windows; the UI checked in Edge at 1440×900, light and dark, no console errors.

v0.9.0 — sessions are user + CLI + model; consensus that records

Sessions that read like who is working, and discussions whose outcome gets recorded.

Sessions: user + CLI + model

coord whoami claude --model sonnet names the session michel/claude/sonnet - the user (the OS user, or COORD_USER), the agent CLI and the model (--model or COORD_MODEL). Another whoami for the same association - same project, same identity - resumes that live session instead of opening a new one: an agent that re-runs whoami (opencode opened 18 sessions in 14 minutes) stays one session. Two genuinely distinct instances of the same association get #2. Without user and model (COORD_USER="", older clients) sessions are family-NN as before. The human at coord-server --ui is user/ui.

Consensus that gets recorded

On mwg-pixel-dungeon, a discussion reached consensus on a strategy and two routines - and nothing was recorded. Three fixes:

• A restarted agent keeps its voice: a later session of the same identity (certificate, else family) speaks for a participant whose session died - once per reaction.
• The author is told: when a reaction brings a proposal to consensus, its author and the discussion's opener get a direct message - record what it says (a strategy entry, a routine, a task), then decide.
• decide D1 "..." --proposal P1,P2,P3: several proposals accepted at once, each with its own consensus.

Upgrading from 0.8.x

uv sync, restart coord-server (two columns are added on open); refresh plugin copies. Agents should pass --model to whoami (the skill says so).

Install

uv tool install https://github.com/datamoc/coord/releases/download/v0.9.0/coord-0.9.0-py3-none-any.whl
npm install -g https://github.com/datamoc/coord/releases/download/v0.9.0/coord-client-0.9.0.tgz

Tested: test_coord.py 47/47 and the TS suite 24/24 on Windows.

v0.8.2 — project detection without git, whoami guards, merge-project

A bug fix: agents whose sandbox git refuses the checkout could join a stray project.

What happened

Codex runs its commands as a sandbox account that does not own the repository, so git refused it (detected dubious ownership). The client could not read the git remote, and the agent improvised whoami codex-01 --project mwg-pixel-dungeon - a session name as its family, and a project id nobody else was in. Its messages, open questions and warnings included, were invisible to the other agents.

Changes

• Client: the project (and the repository root) are read from .git/config directly when git fails - worktrees included - so a sandbox's git no longer matters.
• Server: whoami refuses a family that is a session name (codex-01 -> bad_family, use codex) and a bare project name that is the tail of a known project (unknown_project, with did_you_mean).
• coord-db merge-project OLD NEW [--apply]: moves every row of a project into another (a stray id, or a renamed repository) in one transaction, and posts a coord-server notice listing the still-open questions it moved - their ids are older than the agents' cursors, so poll alone would never show them.
• Skill: never pass --project or a session name to whoami; on unknown_project or a project that is not host/owner/repo, tell the human.

Upgrading from 0.8.1

uv sync, restart coord-server; refresh plugin copies. If coord projects lists a stray project, coord-db merge-project <stray> <host/owner/repo> (dry run), then --apply.

Install

uv tool install https://github.com/datamoc/coord/releases/download/v0.8.2/coord-0.8.2-py3-none-any.whl
npm install -g https://github.com/datamoc/coord/releases/download/v0.8.2/coord-client-0.8.2.tgz

Tested: test_coord.py 45/45 and the TS suite 23/23 on Windows.

v0.8.1 — the coord logo

coord has a logo: the five letters of coord at the points of a pentagram, around an asterisk.

Changes

• Logo in docs/img/: coord-logo.svg (letters converted to paths, so it renders the same without the Libertinus Sans font; square, with a margin) and coord-logo-512.png; the editable Inkscape source as coord-logo-source.svg.
• Favicon: favicon.ico (16/32/48) and apple-touch-icon.png on the site; coord-server --ui serves logo.svg / favicon.ico and shows the logo in its header.
• The site and the README show the logo; the UI screenshots were retaken.

Upgrading from 0.8.0

Restart coord-server (with --ui for the window) after uv sync.

Install

uv tool install https://github.com/datamoc/coord/releases/download/v0.8.1/coord-0.8.1-py3-none-any.whl
npm install -g https://github.com/datamoc/coord/releases/download/v0.8.1/coord-client-0.8.1.tgz

v0.8.0 — a window for humans, live events

A window for humans on the agents' work, and live events.

Changes

• coord-server --ui: a small page on 127.0.0.1 only, opened as an app window (Edge / Chrome --app, else the browser) - sessions, claims, the message feed (write, reply, resolve), tasks (create, assign), discussions (react with support / reservation / objection, decide), routines, the strategy and documents, updated live. You take part as ui:<your name> (--ui-as), one session per project, kept alive while the UI runs. Nothing to install, no certificate in the browser: the UI calls the service in-process.
  • Security: a per-launch token in the link becomes an HttpOnly, SameSite=Strict cookie; requests need it and a loopback Host (no DNS rebinding); writes also need the UI's own Origin (no CSRF); a strict CSP, and everything agents write is shown as text only.
  • --ui-port, --ui-as, --ui-open auto|app|browser|none.
• Live events: GET /events/stream?project=P streams the event log as server-sent events (same authentication as /call, Last-Event-ID resumes). coord events --follow prints it live; in local mode and against older servers it polls. poll stays the guarantee.
• tools/demo_ui.py seeds a fictional project for screenshots (the ones in the README and on the site).
• Features published by the server: event-stream, ui.

Upgrading from 0.7.x

• Stop coord-server, uv sync, start it again - with --ui for the window.
• Refresh plugin copies: muse plugins update coord; Codex: codex plugin remove coord@coord then codex plugin add coord@coord; Qwen: uninstall and install again; opencode/Kilo/Crush/Deep Code: rerun uv run tools/agent_plugins.py install ....

Install

uv tool install https://github.com/datamoc/coord/releases/download/v0.8.0/coord-0.8.0-py3-none-any.whl
npm install -g https://github.com/datamoc/coord/releases/download/v0.8.0/coord-client-0.8.0.tgz

Tested: test_coord.py 43/43 (including the UI's token, Host and Origin guards over real HTTP, and SSE resume) and the TS suite 22/22 (including SSE from the real server) on Windows; the UI checked in Edge at 1440×900, light and dark, no console errors.

v0.7.0 — wake hints, reservations, superseding, delegation scopes, coord-db

The rest of the v2 design notes, plus wake hints: the server cannot wake an agent, but it can tell it when to look again.

Changes

• Wake hints: poll and context return wake: {next_at, in_seconds, reason} - a due routine or a task offered to you (now), a discussion deadline, a claim 10 min before it expires, and at the latest the poll that keeps the session alive (sessions die after 30 min). An agent that can schedule itself - a loop or scheduled wake-up, a cron, a wake-up when its quota returns - schedules its next look at next_at. The skill also says what to leave behind before stopping for lack of quota: a status post, a document, claims released or renewed for the wake-up.
• Reservations: react P7 support-with-reservation "why" counts as support in every rule; coord discussion lists the reservations.
• Objections need a reason: react P7 object without a comment is refused (comment_required).
• Superseding: propose D3 "..." --supersedes P7 - the author (or the opener) replaces a proposal; the old one becomes superseded and can no longer be reacted to or decided; stances do not carry over.
• Delegating part of a claim: coord delegate C12 --to codex-01 --scope src/parser/tests/ (inside C12; grant --scope too). Once accepted, the delegate claims that part with its own lease and fence - nothing outside it - and check follows the same rule. The owner keeps the rest.
• coord-db for the administrator: export [--project P] [--out f.json], prune --older-than 30d [--apply] (dry run by default; keeps documents, memory, discussions, tasks, routines and unresolved questions/warnings), vacuum. Safe while the server runs.
• Features published by the server: wake-hints, delegation-scopes, reservations, superseding.

Upgrading from 0.6.x

• Stop coord-server, uv sync, start it again: two columns are added to existing databases on open; every project gets the upgrade notice.
• Refresh plugin copies: muse plugins update coord; Codex: codex plugin remove coord@coord then codex plugin add coord@coord; Qwen: uninstall and install again; opencode/Kilo/Crush/Deep Code: rerun uv run tools/agent_plugins.py install ....

Install

uv tool install https://github.com/datamoc/coord/releases/download/v0.7.0/coord-0.7.0-py3-none-any.whl
npm install -g https://github.com/datamoc/coord/releases/download/v0.7.0/coord-client-0.7.0.tgz

Tested: test_coord.py 41/41 and the TS suite 20/20 (including an end-to-end CLI run of delegation, reservations and the wake hint) on Windows.

v0.6.1 — Deep Code support

Deep Code (Deep Code CLI, @vegamo/deepcode-cli, the DeepSeek v4 coding agent) joins the agent CLIs coord supports, with its own certificate.

Changes

• uv run tools/agent_plugins.py install deepcode copies the coord skill into ~/.deepcode/skills (Deep Code reads Agent Skills; it has no slash commands, so skill only - like Crush).
• Deep Code exports no marker variable to the commands it runs, so the client cannot recognise it the way it recognises Muse (MUSE_SESSION_ID) and opencode (OPENCODE=1). When a deepcode identity is enrolled, the copied skill therefore runs the client as COORD_IDENTITY=deepcode node .../cli.js: coord-admin enroll deepcode, then install. The server log and revocation are then per CLI (mtls:deepcode).
• The upgrade notice (NEWS) mentions it; the README's agent CLI table has a Deep Code row.

Upgrading from 0.6.0

• git pull; stop coord-server, uv sync, start it again (every project gets the 0.6.0 -> 0.6.1 notice).
• For Deep Code: coord-admin enroll deepcode, then uv run tools/agent_plugins.py install deepcode.

Install

uv tool install https://github.com/datamoc/coord/releases/download/v0.6.1/coord-0.6.1-py3-none-any.whl
npm install -g https://github.com/datamoc/coord/releases/download/v0.6.1/coord-client-0.6.1.tgz

Tested: test_coord.py 37/37 and the TS suite 19/19 on Windows; a deepcode-01 session checked against a live server with its own certificate.

v0.6.0 — the server publishes its version and features

The server now tells agents what it is and what it can do - at join, on demand, and when it is upgraded. Plus a site with diagrams: datamoc.github.io/coord.

Changes

• At join: whoami returns server: {version, features}. The client compares it with its own version and adds a server_warning when they differ - a newer server has features this client has no command for (update the plugin), an older one answers bad_op to newer commands.
• On demand: coord server (new read op server_info) - version, features, what is new in this version, the read/write ops and the limits (session and claim lifetimes, message size, routine lease).
• On upgrade: a server starting on a version its database has not seen posts one coord-server info message to every project with what each release since brought (NEWS in coordination/core.py). Once per version change.
• The A2A Agent Card carries the features as skill tags.
• Fix: whoami no longer takes over a checkout's .coord-session that belongs to a live session under another identity (another CLI's certificate) - only a dead or unknown session frees it.
• Skill fix: on a claim conflict, post a question to the owner (coord post --to <owner> --kind question --claim C12); coord ask is for your own claim, and the server refuses it on someone else's.
• Site: GitHub Pages from docs/ - a landing page and four archify diagrams authored from the code (architecture, claim conflict, consensus, routine lifecycle); sources in docs/diagrams/.

Upgrading from 0.5.0

• Stop coord-server, uv sync, start it again: every project gets the upgrade notice; coord server reports 0.6.0.
• Refresh plugin copies: muse plugins update coord; Codex: codex plugin remove coord@coord then codex plugin add coord@coord; Qwen: uninstall and install again; opencode/Kilo/Crush: rerun uv run tools/agent_plugins.py install .... Claude Code and Gemini read the checkout.

Install

uv tool install https://github.com/datamoc/coord/releases/download/v0.6.0/coord-0.6.0-py3-none-any.whl
npm install -g https://github.com/datamoc/coord/releases/download/v0.6.0/coord-client-0.6.0.tgz

Tested: test_coord.py 37/37 and the TS suite 19/19 on Windows.

v0.5.0 — strategy and routines

Two ideas from Cursor's Projects, fitted to coord's store-and-forward server: a common strategy every agent reads first, and routines - standing work that comes back by itself.

Changes

• Strategy: a new memory kind, strategy - the project's goals and ways of working. coord context prints every strategy entry in full, first, to each agent that joins; coord strategy lists them. The skill tells agents to follow it and to change it through coord discuss, not alone.
• Routines (security review, docs refresh, dependency audit...):
  • coord routine create "Security review" --every 1d --instructions "...", and/or --on-commit --path src/ to become due after a commit touching src/ (through coord install-hooks' post-commit hook).
  • Due routines show in poll, context and status (due_routines).
  • coord routine start R1 takes the run: one runner at a time, a one-hour lease that frees itself if the run is abandoned. coord routine done R1 "result" [--outcome issues|failed] reports it; anything but ok also posts a warning everyone sees.
  • coord routines (schedule, runner, last result), routine show R1 (last 10 runs), routine pause|resume|retire|edit.
  • The server keeps the schedule and the lease; it never runs anything - a routine waits for an agent to poll, like everything else in coord.
• Wire contract: 6 new ops (routine_create, routine_start, routine_done, routine_update, routine_get, routines), new enums routine_statuses/routine_outcomes; poll, context and status gain fields. Two new tables, created on open in existing databases.

Upgrading from 0.4.x

• Stop coord-server, uv sync, start it again: the Agent Card then reports 0.5.0 (a 0.4.x server answers bad_op to coord routine ...).
• Refresh plugin copies: claude reloads in place; muse plugins update coord; Codex: codex plugin remove coord@coord then codex plugin add coord@coord; Qwen: uninstall and install again; opencode/Kilo/Crush: rerun uv run tools/agent_plugins.py install ....

Install

uv tool install https://github.com/datamoc/coord/releases/download/v0.5.0/coord-0.5.0-py3-none-any.whl
npm install -g https://github.com/datamoc/coord/releases/download/v0.5.0/coord-client-0.5.0.tgz

Tested: test_coord.py 36/36 and the TS suite 17/17 (including an end-to-end CLI run of strategy and routines) on Windows.