Dashboard

The dashboard is the main place where ADHDev brings together your IDE sessions, CLI runtimes, and approvals.

What You See First

The top bar is no longer just a flat list of chats. It is a working session surface with a few distinct areas:

• Active tabs for sessions you are using right now
• Hidden tabs for sessions you want to keep around without leaving them in the main strip
• Activity inbox for sessions that need attention, such as approval requests or completed tasks you have not reviewed yet
• Start or recover session for launching a fresh IDE, CLI, or ACP workflow, resuming saved history, or recovering hosted runtimes from the dashboard
• Saved History for reopening earlier conversations or resumeable CLI history

On desktop, the dashboard uses a dockable workspace so you can monitor multiple sessions without losing the main layout.

Session Types

The dashboard can show sessions from several sources in the same workspace:

• IDE sessions such as Cursor or Windsurf
• Extension sessions such as Codex, Cline, or Roo Code inside a host IDE
• CLI sessions such as Claude Code, Gemini CLI, or Codex CLI
• ACP sessions for providers that expose a structured protocol instead of a terminal

Each session keeps its own chat state, status, and available controls.

Desktop Workspace

On desktop, the main dashboard uses a docked pane layout rather than a single chat column.

You can:

• drag tabs between panes
• split work into multiple reading panes
• float a tab as a detached panel
• pop a tab into a separate window
• dock a floating or popped-out tab back into the main grid
• assign per-tab shortcuts from the tab context menu

This is the best layout when you want one active session for input while keeping other sessions visible for supervision.

Hidden Tabs And Inbox

These two surfaces are important if you use ADHDev heavily:

• Hidden tabs reduce clutter without closing a session
• Activity inbox collects sessions that are waiting for approval or have finished something you have not reviewed yet

A good default workflow is to keep the main strip focused on active work, hide the rest, and use the inbox as the place you check for interruptions.

CLI View Toggle

CLI sessions can switch between two views without relaunching the runtime:

• Terminal view when you want the full PTY output and prompt behavior
• Chat view when you want a cleaner conversation-style read of the same session

This is especially useful when a CLI tool is still running but you only need to review output or answer a prompt from mobile.

Saved History And Launch Flow

The dashboard can open more than the live turn stream:

• recent chat history for the active session
• saved history for CLI providers that expose resumable sessions
• launch flows that start from machine/workspace selection and let you choose Start fresh, Resume saved history, or Recover hosted runtime

If a session is not in your active strip, check hidden tabs, then the inbox, then history.

Git Status Surface

When a session is attached to a Git workspace, the dashboard can show daemon-owned Git state next to the session instead of relying on agent self-reports.

Current Git Surface behavior:

• Git pills and dialogs are driven by daemon git_* commands and workspace.git topic updates.
• Cloud receives rich Git state over the P2P data channel; the Worker/UserSession WebSocket carries only lightweight routing/status metadata.
• Standalone uses the same daemon-core Git command contract through local REST/WS.
• Work summary system bubbles are synthesized from daemon-derived compact Git summaries, not by parsing the agent transcript.
• Mutating actions such as checkpoint, stash, pop, and checkout are explicit guarded commands; arbitrary Git shell execution is not exposed.

The main command names are git_status, git_diff_summary, git_diff_file, git_snapshot_create, git_snapshot_compare, git_log, git_checkpoint, git_stash_push, git_stash_pop, git_checkout_files, and git_remote_url.

Mobile Dashboard

On mobile, the dashboard uses a simplified flow instead of the full desktop dock layout.

Expect three main patterns:

• an inbox-first view for things that need attention
• a focused chat view for the selected session
• a machine view when you want to launch or inspect sessions on a specific machine

This keeps approvals, short replies, and session recovery practical on a phone without forcing the full desktop layout.

Machine Detail

When you open a specific machine, ADHDev groups machine-level tools into dedicated tabs:

• Workspace for active IDE, CLI, and ACP sessions
• Hosted Runtimes for hosted CLI runtime diagnostics and recovery
• Providers for provider-specific settings, machine activation, detection, and provider source reloads
• System for machine health and runtime details
• Logs for machine and daemon logs

If a CLI runtime gets stuck after a restart or disconnect, the Hosted Runtimes tab is the place to inspect live runtimes, recover snapshots, restart wedged sessions, or prune duplicate runtimes. If a CLI/ACP provider is missing from launch, use Providers to enable it, run detection, adjust executable path/args, or apply a provider source config reload. If you need saved workspaces or machine health details, look in System rather than the live workspace tab.

Notifications And Approvals

Approvals and alerts are woven into the dashboard rather than living in a separate monitoring-only view.

You can:

• answer approval requests from the active session
• use the inbox to jump straight to sessions waiting on you
• configure browser and push notifications from the Notifications page
• adjust provider-level alert behavior such as approval alerts or long-generation alerts

Sidebar

The standard cloud navigation usually includes:

• Dashboard
• Burrows
• Notifications
• Account
• Settings

Additional surfaces such as Rafts, Team, API Keys, and Webhooks can be plan-gated or rollout-gated, so they may not appear for every account.

Next Steps

• Remote View →
• CLI Agents →
• Multi-Machine →
• Troubleshooting →