What is ADHDev?

ADHDev (Agent Dashboard Hub for Dev) is a cloud-connected dashboard for IDE, extension, CLI, and ACP coding agents.

The main product shape is ADHDev Cloud: your local daemon runs on the dev machine, while the dashboard, account system, notifications, and automation features live in the hosted service. A self-hosted standalone path is also available when you want the same local runtime stack without the cloud account layer.

The Problem

You're using coding agents like Cursor, Codex extension, Claude Code, or Codex CLI on your own machine. Once the agent is running, visibility becomes fragmented:

Is it still working?
Did it finish?
Is it waiting for approval?
Which workspace or session is it attached to?
Can you recover the session if the local daemon restarts?

The Solution

ADHDev gives you one dashboard for the agent surfaces it can observe and control. Depending on the provider, you can:

Read live chat and status updates
Send messages and resolve approval actions
Launch and monitor CLI or ACP runtimes
View supported IDE surfaces and, when available, control them remotely
Inspect runtime metadata, diagnostics, and workspace state from one place

Cloud-first Architecture

Cloud

The default ADHDev flow looks like this:

Your machine: IDE / extension / CLI / ACP
                    |
                    v
              local daemon
                    |
                    v
      auth + metadata + signaling + dashboard

In this mode you get:

remote access outside your LAN
multi-machine views
API keys and webhooks
push notifications
account-linked machine management

Self-hosted

The self-hosted path keeps the same daemon/session-host/runtime stack but serves a local dashboard instead of using the hosted account layer.

Use it when you want:

a fully local deployment
LAN-only dashboard access
local REST/WebSocket automation
no cloud account dependency

Self-hosted is a supported option, but not the center of the public product docs.

Cloud vs Self-hosted

Feature	Self-hosted (OSS)	Cloud (adhf.dev)
IDE/CLI agent chat & control	✅	✅
Hosted CLI runtimes	✅	✅
Local standalone REST/WebSocket API	✅	❌
Hosted cloud REST API	❌	✅
Remote access (outside LAN)	❌	✅
Multi-machine management	❌	✅
API keys + hosted webhooks	❌	✅
OAuth / account system	❌	✅
Push notifications	❌	✅

Built-in Integrations

Current built-in inventory includes:

8 IDE integrations
8 CLI providers
4 extension streams
35 ACP adapters

Important distinction:

built-in means the integration exists in the shipped inventory
supported means it has explicit verification evidence

Do not treat inventory presence as a blanket support promise. If you want the safest current public starting points, begin with Cursor, Codex extension, Claude Code, or Codex CLI. Use these pages before making compatibility claims:

Typical Use Cases

OSS / standalone users

Run a local dashboard on your workstation
Monitor Cursor, Windsurf, Cline, Roo Code, or CLI agents from another browser tab or device on the same LAN
Launch CLI agents and recover them after daemon restarts through the session-host stack
Use the local API for scripts or personal automation

Cloud users

Reach the same machine from outside your network
Manage more than one machine in one dashboard
Trigger automations with API keys and webhooks
Use push notifications for approval and completion events

What is ADHDev? ​

The Problem ​

The Solution ​

Cloud-first Architecture ​

Cloud ​

Self-hosted ​

Cloud vs Self-hosted ​

Built-in Integrations ​

Typical Use Cases ​

OSS / standalone users ​

Cloud users ​

Next Steps ​