What it is: agent-harness-kit (ahk) is a thin CLI + library you drop into any repo to give your AI agents structure. It scaffolds a 4-role workflow (Lead → Explorer → Builder → Reviewer), a local SQLite task backlog with atomic claiming, lifecycle health gates, and a full audit trail — all without touching any cloud service or requiring API keys.
Why: Every time I handed a task to Claude Code or OpenCode, the agent would just… roam. It had no memory of what it already explored, no way to coordinate with a second agent, and no gate to check if the codebase was even in a healthy state before it started writing. I wanted something closer to how senior engineers actually work: a clear role per agent, a shared task list, and a mandatory verification step before anything is marked done.
The architecture is deliberately boring: one agent.harness.ts config file, a .harness/ directory with a SQLite DB (using Node ≥ 22's built-in node:sqlite — zero native deps), and markdown agent definitions your LLM reads at session start. It works with Claude Code, OpenCode, Cursor, or any tool that can read files.
npx ahk init # scaffold the harness into your repo
npx ahk health # verify the environment before agents start
npx ahk status # see task backlog and agent activity
Website: https://stack.cardor.dev/ahk
Link: https://github.com/enmanuelmag/agent-harness-kit
Would love to hear your thoughts, especially if you've tried other approaches to multi-agent coordination!
No responses yet.