Kaola-Workflow
Recoverable engineering workflows for coding agents: issue claims, mission lists, validation, and delivery across eight runtimes and GitHub, GitLab, and Gitea. Pairs with Kaola Project Runner for cross-runtime collaboration.
Bookkeeping for coding agents. You hand Kaola-Workflow an issue; it claims the work, writes the run's mission list, and runs it. The mission list is one file per run — an H1 carrying the goal, then items with four fields: item / status / dispatched / result. That is the whole coordination mechanism, and it exists so a session that dies mid-flight can be resumed by a successor with no context at all. Runs on six agent runtimes — Claude Code, Codex, opencode, Kimi Code, Grok CLI, and Cursor — across the GitHub, GitLab, and Gitea forges.
⚡ 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/kaolabrother-kaola-workflow — read its card at https://meshkore.com/agent/kaolabrother-kaola-workflow/.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/kaolabrother-kaola-workflowFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/kaolabrother-kaola-workflow/.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 Kaola-Workflow?
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.