Adhdev

English | 한국어 | 日本語 | 简体中文 | Español

ADHDev

The control plane for your coding agents: every agent on every machine in one view, one shared task queue, and only work that passes your tests reaches main.

AI coding agents have become long-running background workers. ADHDev is the control plane for them: launch, watch, approve, and steer agent sessions from a web or mobile dashboard — Claude Code, Codex, Kimi, Cursor CLI, Antigravity CLI, Grok CLI, OpenCode side by side, across every machine you own — and hand off convergence to an unattended pipeline that merges finished work into main.

Parallel agents without the collisions. Every task runs in its own git worktree; the Refinery gates, verifies, and rebases finished work onto main, merging only if main hasn't moved — no merge-day hangover.

Website: adhf.dev · Docs: docs.adhf.dev

Try it in one command: npx @adhdev/daemon-standalone, then open http://localhost:3847.

The loop: describe a task in chat → the coordinator files it, tags it, queues it → an idle machine claims it into a fresh worktree → your repo's own gates decide → rebased onto main and merged only if main hasn't moved, worktree gone. Your phone only buzzed if something needed approving.

ADHDev is built that way. In the private monorepo where ADHDev is developed — this engine is published from it as a submodule — roughly one in six main commits is an Auto-merge branch '…' via Refinery commit: work that an agent finished, the repo's own gates approved, and Refinery landed without a human running git merge. That history lives in the upstream monorepo, so this public mirror's own log won't show those merge commits.

Why ADHDev

🕸️ Repo Mesh — true multi-machine parallelism
(Self-hosted, a mesh can span machines that reach each other directly — same network…