Skip to content
Maestro Documentation

Configuration

Maestro reads environment configuration from .env.local (or .env) and applies safe defaults. The packaged app keeps this file under %APPDATA%\Maestro; a source checkout normally keeps it at the checkout root.

Core settings

Section titled “Core settings”
MAESTRO_DB_PATH=.maestro/maestro.db
MAESTRO_EXECUTION_ROOT=C:\MaestroRuntime\octomynd-maestro
MAESTRO_WORKTREES_PATH=C:\MaestroRuntime\octomynd-maestro\worktrees
MAESTRO_DASHBOARD_HOST=127.0.0.1
MAESTRO_DASHBOARD_PORT=4787
MAESTRO_DASHBOARD_ENABLED=true

Keep execution and worktrees outside synced folders. The UI dev server uses port 4788; the application API uses 4787.

Autopilot and runtime

Section titled “Autopilot and runtime”
MAESTRO_AUTOPILOT_ENABLED=true
MAESTRO_AUTOPILOT_POLL_MS=30000
MAESTRO_AUTOPILOT_MAX_CONCURRENT=1
MAESTRO_TOKEN_RUNTIME_ENABLED=true
MAESTRO_WORK_GRAPH_MODE=off
MAESTRO_SKILLS_ENABLED=false

Work Graphs and Skills are opt-in controls. Provider-specific model and inactivity settings are also available in .env.example; prefer the Dashboard control plane for per-provider routing.

Secrets

Section titled “Secrets”

Use placeholders in documentation and .env.example. Never commit .env.local, API keys, OAuth artifacts, Telegram tokens, database files or runtime logs.