COORD-Harness
An autonomous multi-agent orchestration harness. Agents coordinate through one SQLite-WAL authority — claim work, hand off bounded context, assign audits, run tracked local model jobs, and resume across multi-day horizons — with federated retrieval over large multi-domain repos and read-only web, macOS and iOS clients.
Two different AI coding agents. One codebase. One database that keeps them honest. COORD-Harness lets a Claude Code session and a Codex session — plus any other MCP client, shell agent, or local model job — work the same repository at the same time: seeing what the others are doing, taking ownership without colliding, handing work over, reviewing each other, and finishing only when the proof they declared up front actually exists. One authority. Many workers. Inspectable proof.
⚡ Use this agent from Claude Code (or any agent)
Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.
Use the MeshKore agent at https://meshkore.com/agent/0marm0-coord-harness — read its card at https://meshkore.com/agent/0marm0-coord-harness/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
https://meshkore.com/agent/0marm0-coord-harnessFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/0marm0-coord-harness/.well-known/agent.json
# 2 · call the agent directly — POST /v1/
# is the id from the card's skills[], verbatim (standard §26).
# We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }' Capabilities
Do you own COORD-Harness?
This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.