Install, update, uninstall

Install

curl -fsSL https://gaia-agent.com/install.sh | bash

That one line:

ensures uv and git are present (installs uv if missing),
creates a self-contained venv at ~/.gaia/venv and installs gaia with every feature (gaia[all] — browser, OpenAI, MCP, web tools, memory),
sets up the browser runtime (Camoufox — the anti-detect Firefox for the default native backend; bun + playwright-mcp are only fetched if you opt into browser.backend: mcp),
links the gaia command into ~/.local/bin,
and, on a real terminal, walks you through gaia setup (pick a model + connectors).

By default it installs the latest release (a known-good version). macOS and Linux are supported. On Windows, install under WSL.

Flags

curl … | bash -s -- <flags>:

Flag	Effect
`--ref <git-ref>`	install a specific ref instead of the latest release: `--ref main` (bleeding edge), a tag, or a commit
`--no-browser`	skip bun + Chromium
`--no-setup`	don’t run `gaia setup` at the end
`--non-interactive`	no prompts (implies `--no-setup`)

Everything lives under ~/.gaia (the venv) and ~/.local/bin/gaia (the launcher). Your config, memory, and users are in ~/.gaia (config in ~/.gaia/gaia.yaml, secrets in ~/.gaia/.env).

Update

gaia update

Re-installs gaia from git into ~/.gaia/venv and, if the daemon is running, restarts it so the new code takes effect. gaia update --ref <ref> pins a specific version.

Uninstall

gaia uninstall

Stops the daemon, removes the boot service (if installed) and the gaia launcher, then asks whether to also delete ~/.gaia (your config, memory, users, logs). By default your data is kept, so a reinstall picks up where you left off. Non-interactive: gaia uninstall --purge deletes everything; --keep keeps the data.

Run on boot (optional)

gaia start runs the daemon detached, but it doesn’t survive a reboot. To run gaia as a real OS service — starts at login, restarts on crash:

gaia service install     # launchd (macOS) / systemd --user (Linux)
gaia service status
gaia service uninstall

On Linux, loginctl enable-linger keeps it running without an active login session.

Something broke?

gaia report

Bundles the latest crash (~/.gaia/crashes), a recent error-log tail, and your environment into a redacted GitHub bug report — shows it, then files it via gh or a prefilled issue URL you review and submit. A fatal daemon crash is captured automatically; if the service restarts after one, gaia DMs the admin to run gaia report.