Getting Started
Get ADHDev up and running in under 5 minutes.
Cloud Version (adhf.dev)
The cloud version gives you remote access from anywhere, plus the hosted dashboard, account system, notifications, and automation features.
1. Create an Account
Go to adhf.dev and sign in with GitHub or Google.
TIP
Cloud sign-in only works when GitHub or Google gives ADHDev an email address that the provider has already verified. If the provider account you used does not have a verified email, ADHDev blocks the sign-in instead of guessing which account to link.
2. Install the CLI
The publicly tested install paths today are macOS and Windows.
The fastest macOS install path is the one-line installer:
curl -fsSL https://adhf.dev/install | shThis is the current public install path for macOS. It automatically installs Node.js if needed, installs the CLI, and runs the setup wizard.
Linux may work with the same shell flow, but Linux has not yet been publicly validated enough to call it a supported install path.
On Windows, use the platform installer instead:
irm https://adhf.dev/install.ps1 | iexAlternatively, install via npm directly:
npm install -g adhdevWARNING
On Windows, global npm install/startup under Node.js 24+ is temporarily unsupported. The one-line PowerShell installer will bootstrap a portable Node.js 22 runtime for setup when needed.
3. Set Up Authentication
adhdev setupThis opens a browser window for device authentication. Follow the prompts to link your machine to your account.
4. Start the Daemon
adhdev daemonThe daemon will:
- Detect running IDEs automatically
- Connect to the ADHDev server
- Establish P2P connections for fast data transfer
- Start monitoring AI agent activity
5. Open the Dashboard
Go to adhf.dev — your connected machines and sessions should appear within seconds.
TIP
If you want the clearest first IDE path, start by launching Cursor with CDP enabled:
adhdev launch cursorSelf-hosted Option (Local Network)
If you do not want the cloud account flow, use the dedicated self-hosted docs section instead:
Those OSS docs now own the standalone install, runtime flags, and local API details.
Recommended First Paths
If you want the safest first impression of the current product, start with one of these:
adhdev launch cursor- Codex extension inside a supported host IDE
adhdev launch claudeoradhdev launch codex
For the current public verification picture, check Compatibility & Caveats and Supported Providers before you depend on a specific workflow.
Launching IDEs with CDP
ADHDev connects to your IDE via Chrome DevTools Protocol (CDP). Most IDEs need to be launched with a specific CDP port.
# Launch (or relaunch) with CDP enabled
adhdev launch cursor # Cursor on port 9333
adhdev launch antigravity # Antigravity on port 9335
adhdev launch windsurf # Windsurf on port 9336
# With a specific workspace
adhdev launch cursor -w ~/my-project
# New window
adhdev launch cursor -nWARNING
adhdev launch will close and reopen the IDE to enable CDP. Save your work first!
Inventory is broader than current public promotion. Treat IDE launch availability as a discovery surface, not a blanket support promise.
Adding CLI Agents
CLI agents can be managed directly from the dashboard through the hosted PTY/session-host stack.
# Launch recommended starting points
adhdev daemon
adhdev launch claude
adhdev launch codexOnce launched, you'll see an interactive terminal view in the dashboard where you can type commands and see output in real time.
Other CLI providers exist in the built-in inventory, but Claude Code and Codex CLI currently have the clearest public validation evidence.
Uninstalling ADHDev
To completely remove ADHDev from your system:
adhdev uninstallThis stops the daemon, removes the OS background service, and deletes all data in ~/.adhdev/.
To also remove the CLI tool itself:
npm uninstall -g adhdevTIP
If you only want to switch accounts, use adhdev logout instead — it keeps your IDE and workspace settings intact.