Self-hosting

Self-hosting Dash Bot

Run the harness and desktop app on infrastructure you control.

Dash Bot is local-first by default: the harness listens on loopback, agent CLIs run on your machine, and application state lives under ~/.dashbot.

Typical self-hosted setup

Run Dash Bot on your personal macOS, Windows, or Ubuntu computer.
Install and authenticate the agent CLIs you want to use.
Add optional third-party keys only for the services you need.
Keep the harness on loopback.
Use the paired companion sidecar or Tailscale when another device needs access.

What is still third party

Self-hosting Dash Bot does not self-host every optional provider:

Agent providers authenticate and bill through their own CLI or API.
Composio owns connected-app OAuth grants unless you replace that integration.
Box owns managed cloud computers.
ElevenLabs synthesizes speech when voice is enabled.

These services are optional. Local chat through a locally installed agent CLI does not require them.

Run headless during development

pnpm install --frozen-lockfile
pnpm dev:server

The main harness listens on 127.0.0.1:8799 by default. Keep it private; it owns agent processes, approvals, computers, and workspace configuration.

USB Android control

Let a bot inspect and operate a physically connected Android phone.

Networking

Understand the harness, webhook, and companion network boundaries.

On this page

Typical self-hosted setup What is still third party Run headless during development