Skip to content

v0.13.0 — humans and agents together

Choose a tag to compare

View all tags
@datamoc datamoc released this 25 Sep 06:41
· 31 commits to master since this release
v0.13.0
f836ca2

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.

Assets 6
Loading