See where the work goes

Compare daily activity, recorded tokens, commits and changed lines by project or repository. Switch between token and commit activity, keep only relevant cards visible and restore them from Hidden. Native token history also works without a Git repository. Recorded 91-day totals keep older work visible; partial history stays explicit. The Deployment map connects hosts, containers, repositories and agents, with separate views and Mermaid export.

How it works

  1. Dashboard

    Read current configuration problems and their actions in Doctor, with saved reports kept in history. Compare project activity, native token totals and Git changes. Inspect CPU, RAM and disk I/O timelines, or open Attention for sessions and requests that need you.

  2. Map environments and agents

    See how hosts, containers, repositories and agents connect. Switch the deployment map between infrastructure, projects and agent providers.

  3. Current configuration problems

    Open current problems from Dashboard. Each finding names the affected target, observed and expected state, impact and a relevant action. Opening Doctor does not run an AI task.

  4. Open the setting behind a finding

    Follow the catalog finding to its actual settings. Missing or stale evidence is separate from a failed configuration, and the sample never claims to repair a real server.

  5. Keep past reports in history

    Current problems stay separate from saved evidence and optional analysis. Open an older report with an explicit historical label.

  6. Token and commit activity

    Switch metrics to see when tokens were last consumed or Git last changed. Large native token totals use m; incomplete history stays marked.

Read the documentation

Try the interface

INTERACTIVE DEMO

Explore the sample projects, accounts, files and access requests. Live sessions and file transfers are available in your own console.

Watch the workflow

DashboardREAL UI

Loading the recorded terminal…

Walkthrough paused

Release videos

YOUR AGENTS. YOUR INFRASTRUCTURE.

Put your server to work.

Give your agents persistent remote workspaces. Start with one repository and server, then add projects, developers and resources from the same console.