What is ADHDev?
ADHDev is the control plane for your local coding agents.
It runs a daemon on each of your machines, attaches to whatever CLI agents are already there — Claude Code, Codex, Cursor CLI, or any PTY agent — and gives you one place to control them from the web, scale across machines, and land the work safely on main.
Three core pillars
1. Web control of any local CLI agent
Drive any CLI agent from your browser or phone: send prompts, approve tool calls, and steer sessions without touching the terminal. The v1 Provider SDK connects any PTY CLI or CDP IDE session — vendor-neutral by design.
2. Repo Mesh + Refinery (parallel orchestration)
Dispatch tasks across isolated git worktrees on your machines in parallel. The Refinery validates each worktree against your repo's own gates (typecheck, tests, lint), verifies patch equivalence, publishes submodule commits, rebases finished work onto main and merges it only if main hasn't moved, and cleans up — automatically. No force-push, ever.
3. P2P-first — code stays on your machine
Chat, commands, screenshots, and file ops flow directly between your browser and your daemon over WebRTC. The server handles auth, signaling and a small status summary. The one deliberate exception: on the cloud edition it receives the approval prompt (the command and button labels) to build the push notification, which shows up to 80 characters of it.
Two ways to run it
| Mode | Description |
|---|---|
| Standalone (OSS) | AGPL, no account required. Runs entirely on localhost:3847. A fully local dashboard for the machine in front of you (and the rest of your LAN). |
| Cloud (adhf.dev) | Account-linked multi-machine management, push notifications, and remote access. Reach any machine from anywhere. |
When to use which
- Standalone — local dev workflow, LAN-only access (machines that can reach each other directly can pair), no cloud account dependency, or self-hosted automation
- Cloud — account-linked multi-machine fleet, remote access outside your LAN, mobile approvals