Installation & Setup

Prerequisites

• OpenCode CLI installed and available on your PATH
• At least one model provider connected — Fleet spawns OpenCode sessions that need LLM access. If you haven't connected a provider yet, run /connect inside OpenCode to authenticate with Anthropic, OpenAI, or another supported provider. See the OpenCode provider docs for details.

TIP

Fleet ships as a self-contained bundle with its own Node.js runtime — no separate Node.js installation required.

Install

macOS / Linux

curl -fsSL https://get.tryweave.io/agent-fleet.sh | sh

Windows (PowerShell)

irm https://github.com/pgermishuys/weave-agent-fleet/releases/latest/download/install.ps1 | iex

First Run

weave-fleet

Fleet starts a local server and opens the dashboard:

Fleet running at http://localhost:3000

Open http://localhost:3000 in your browser.

Security: Local-Only by Design

Fleet is a local development tool. Key security characteristics:

• No authentication required — Fleet is intended for single-user local use; no login or API keys are needed to access the dashboard
• Data stays local — all session state is stored in SQLite at ~/.weave/fleet.db. Nothing is sent to external services
• Default bind address — Fleet defaults to WEAVE_HOSTNAME=0.0.0.0, which accepts connections from any network interface

Network Exposure

The default WEAVE_HOSTNAME=0.0.0.0 binding means Fleet is accessible from other machines on your local network. If you're on a shared or untrusted network (e.g., a coffee shop, a university network, or a shared office), bind to localhost only:

WEAVE_HOSTNAME=127.0.0.1 weave-fleet

This restricts access to only your local machine.

Managing Your Installation

Command	Description
weave-fleet	Start the Fleet server
weave-fleet update	Update to the latest version
weave-fleet version	Check installed version
weave-fleet uninstall	Remove Fleet

Configuration

Fleet is configured via environment variables. All have sensible defaults.

Variable	Default	Description
PORT	3000	Server port
WEAVE_HOSTNAME	0.0.0.0	Server bind address
WEAVE_DB_PATH	~/.weave/fleet.db	SQLite database path
WEAVE_INSTALL_DIR	~/.weave/fleet	Installation directory
ORCHESTRATOR_WORKSPACE_ROOTS	Home directory	Colon-separated list of allowed workspace root directories
OPENCODE_BIN	Auto-detected	Full path to the opencode binary (if not on PATH)

Example: Custom Port and Workspace Roots

PORT=8080 ORCHESTRATOR_WORKSPACE_ROOTS="/home/dev/projects:/home/dev/oss" weave-fleet

Workspace Roots

Fleet restricts session creation to directories under configured workspace roots. By default, your home directory is the only root. You can add additional roots via the ORCHESTRATOR_WORKSPACE_ROOTS environment variable (colon-separated on Unix, semicolon on Windows) or through the Settings UI.

Security

Workspace roots control which directories Fleet can access. Avoid setting roots to / or C:\ — keep them scoped to your project directories.

Troubleshooting

"Directory is outside the allowed workspace roots"

This error occurs when you try to create a session in a directory that isn't under any of your configured workspace roots. By default, Fleet only allows access to directories under your home directory.

To fix this, set the ORCHESTRATOR_WORKSPACE_ROOTS environment variable to include the directories you want to work with:

# Unix / macOS — colon-separated
ORCHESTRATOR_WORKSPACE_ROOTS="/home/dev/projects:/mnt/repos" weave-fleet

# Windows (PowerShell) — semicolon-separated
$env:ORCHESTRATOR_WORKSPACE_ROOTS="C:\Users\dev\projects;D:\repos"; weave-fleet

TIP

If your projects live outside your home directory (e.g. on a different drive on Windows, or under /mnt or /opt on Linux), you'll need to configure this before Fleet can access them.

Data Storage

Fleet persists all state to a SQLite database at ~/.weave/fleet.db. This includes workspaces, instances, sessions, notifications, and workspace roots. The database is created automatically on first run.

To reset Fleet completely, stop the server and delete the database:

rm ~/.weave/fleet.db