> ## Documentation Index
> Fetch the complete documentation index at: https://toolkit.astralsolutions.tech/llms.txt
> Use this file to discover all available pages before exploring further.

# Web Dashboard: Visual Interface for All Toolkit Features

> The All-In-One Toolkit web dashboard gives you a visual UI for ports, disk cleanup, proxy routes, and hosts management with full CLI parity.

The web dashboard is a React-based interactive UI that mirrors everything available in the Toolkit CLI. It runs entirely on your local machine and is accessible at `http://toolkit.localhost` (the named proxy URL) or directly at `http://localhost:3100` on the default port. Whether you prefer a visual interface or the terminal, every feature is available in both — you can switch between them freely at any time.

<Frame>
  <img src="https://mintcdn.com/astralsolutions-cc9affb5/4-CRZwcGLZj5Cbor/images/dashboard-overview.png?fit=max&auto=format&n=4-CRZwcGLZj5Cbor&q=85&s=8ed255bf8e8f01d85b64573f6007cdd5" alt="All-In-One Developer Toolkit dashboard showing the Ports Monitor view" width="1909" height="1127" data-path="images/dashboard-overview.png" />
</Frame>

## Launching the Dashboard

<Steps>
  <Step title="Start the dashboard server">
    Run the `toolkit ui` command to start both the Toolkit daemon and the web UI server:

    ```bash theme={null}
    toolkit ui
    ```

    The server starts on port `3100` by default and registers the dashboard at `http://toolkit.localhost`.
  </Step>

  <Step title="Open the dashboard in your browser">
    The dashboard opens automatically in your default browser at:

    ```text theme={null}
    http://toolkit.localhost
    ```

    You can also reach it directly at `http://localhost:3100` if you prefer bypassing the proxy.
  </Step>

  <Step title="Start on a custom port (optional)">
    Use the `--port` flag to bind the UI server to a different port:

    ```bash theme={null}
    toolkit ui --port 3200
    ```

    The dashboard will then be available at `http://localhost:3200` and also at `http://toolkit.localhost:3200` via the proxy.
  </Step>

  <Step title="Suppress automatic browser launch (optional)">
    If you don't want the browser to open automatically — for example in a headless or remote environment — pass the `--no-open` flag:

    ```bash theme={null}
    toolkit ui --no-open
    ```

    The server starts as usual; you can navigate to the dashboard manually whenever you're ready.
  </Step>
</Steps>

## Dashboard Sections

The dashboard is organized into four functional areas, each corresponding directly to a CLI module:

<CardGroup cols={2}>
  <Card title="Ports" icon="ethernet">
    Inspect all ports currently listening on your system. View the protocol (TCP/UDP), PID, process name, and associated service metadata. Kill processes by port number directly from the UI — with the same safety barrier that protects system-critical ports (e.g., SSH on 22, DNS on 53).
  </Card>

  <Card title="Cleaner" icon="trash">
    Scan your project directories for heavyweight dependency folders — `node_modules`, `.venv`, `venv`, `env`, and `conda`. Preview the disk space you'll reclaim with a dry-run before committing to any deletions, and identify orphaned environments that lack a corresponding project manifest.
  </Card>

  <Card title="Proxy Routes" icon="arrow-right-arrow-left">
    View and manage all active `*.localhost` proxy routes registered with the Toolkit daemon. Add a clean subdomain URL to any locally running server, remove routes you no longer need, or inspect which port each subdomain is forwarding to — all without touching configuration files manually.
  </Card>

  <Card title="Hosts" icon="server">
    Browse, add, and remove custom domain mappings in your system hosts file. All entries created through Toolkit are isolated inside clearly delimited blocks, so your existing hosts configuration is never overwritten or corrupted.
  </Card>
</CardGroup>

<Info>
  **CLI Parity:** Every action available in the CLI is also available in the dashboard — use whichever you prefer. There is no feature gap between the two interfaces.
</Info>

## `toolkit ui` Options

| Flag               | Default | Description                      |
| ------------------ | ------- | -------------------------------- |
| `-p, --port <num>` | `3100`  | Port for the web UI server       |
| `--no-open`        | `false` | Disable auto-opening the browser |

<Note>
  The dashboard requires the Toolkit daemon to be running in the background to handle proxy routing and API requests. The `toolkit ui` command starts both the daemon and the UI server together, so you don't need to start them separately.
</Note>