gaia CLI, run gaia up, and finish setup in your browser.
Install and start
1
Install the CLI
Other ways to install
Other ways to install

The installer carries straight on into gaia up and downloads GAIA
2
Start GAIA
~/gaia, writes the settings and starts everything. Git is not needed.3
Finish in the browser
Open http://localhost:3000/setup, create the admin account and pick an AI provider.
Everyday commands
Every flag and command is in the CLI reference.

gaia status: every dependency and container
Update
gaia update. If the download fails, nothing changes.
Something broke?

gaia doctor on a fresh install, before the admin account exists
Good to know
Port 3000 is taken
Port 3000 is taken
GAIA opens one port. If it is busy,
gaia up shows what uses it and suggests another. The choice is saved in packages/cli/selfhost/.env inside ~/gaia. To change it later, edit that file, then run gaia stop && gaia start.Try a beta
Try a beta
Betas are early versions, numbered like Expect rough edges, and run
0.7.0-beta.1. Add GAIA_CHANNEL=beta to the install command, then run gaia up:gaia backup first if you rely on the install.What is in ~/gaia
What is in ~/gaia
packages/cli/selfhost/: the Compose files and proxy settings- Your files:
apps/api/.env,apps/bots/.env,packages/cli/selfhost/.envandbackups/ gaia-selfhost.json: the list of files that came with the release
Installs made by an older gaia up
Installs made by an older gaia up
These were git checkouts. The next
gaia update converts them: the tracked files and .git are removed, and your settings and backups stay. A checkout on a branch, or with local edits, is refused and pointed at gaia update --git.
