Getting started
Bazilion ships as one npm package, bazilion, with the CLI, the daemon and the web UI. The daemon
creates its home on first start; there is no separate init step.
What you need
Section titled “What you need”- Node.js
^26.12.1(26.12.1 or a later 26.x). The CLI refuses any other Node version before it starts. - A model provider: a ChatGPT account, an API key (OpenAI, Anthropic, Google and many others) or a local server (LM Studio, Ollama, llama.cpp).
- Linux is the tested platform; macOS runs commands on the host and is untested.
Install and open the dashboard
Section titled “Install and open the dashboard”The one-line installer installs Node 26.12.1 through Volta when no supported Node is found, then
the bazilion package:
curl -fsSL https://bazilion.com/install.sh | bashbazilion dashboardWith a supported Node already installed, use npm (or run each command as npx bazilion …):
npm install -g bazilionbazilion dashboardbazilion dashboard starts the daemon on 127.0.0.1:4321 and the web UI on 127.0.0.1:4322,
and opens your browser (--no-open skips that). On first start the daemon creates ~/.bazilion
(or $BAZILION_HOME) with its database and a bootstrap token in auth.json. bazilion serve
starts only the daemon.
Sign in and connect a provider
Section titled “Sign in and connect a provider”Sign in to the web UI with the bootstrap token; bazilion token show-local prints it. The CLI
reads it by itself.
Until one provider is enabled with a saved model, every page leads to setup. On /config,
connect ChatGPT or paste an API key, enable the provider and pick at least one model. The
connection test sends one real request, which the provider may bill. Bazilion then creates a
default Profile and a default Team.
The same from a terminal:
bazilion auth openai login # ChatGPT account (--device-code when headless)bazilion config set ANTHROPIC_API_KEY sk-ant-… # or an API key, stored encryptedbazilion provider enable anthropicbazilion provider models-set anthropic claude-opus-5bazilion auth openai login opens a browser and waits for the callback on localhost:1455; use
--device-code on a remote or headless machine. A key passed to config set can land in your
shell history; the /config page avoids that.
First Agent
Section titled “First Agent”Spawn one from the Agents page or the chat sidebar, or:
bazilion agent spawn --profile default --name firstbazilion agent chat <agent-id> --message "say hi"agent chat runs one turn and streams it; the web chat is the conversational client. Next, read
Core concepts and the web interface tour.
Upgrade to 0.26.0
Section titled “Upgrade to 0.26.0”There are no database migrations. A release opens a home only when its schema matches the one it ships; otherwise the daemon refuses to start and leaves the home untouched. 0.26.0 reset the schema, so a home from 0.25.0 or any earlier release is refused. To move to 0.26.0:
-
Stop the daemon and copy the whole home somewhere safe, with any project a linked Team points to. A
bazilion backup createarchive works too, but only the release that wrote it can restore it.Terminal window cp -a ~/.bazilion ~/.bazilion-0.25 -
Install the new release and reset the home.
uninstallkeeps installed skills;--allremoves them too.Terminal window npm install -g bazilion@0.26.0bazilion uninstall --yes -
Start Bazilion again; it bootstraps a fresh home. Connect a provider and recreate the Teams and Agents you need.
Terminal window bazilion dashboard
Nothing is imported from the old home. Keep the copy, and the release that wrote it, for as long as you need the old data. A refusal caused by the Node version means upgrading Node, never resetting the home.
Reset a home
Section titled “Reset a home”bazilion uninstall # asks once, then resets the homebazilion uninstall --yes # reset without askingbazilion uninstall --yes --all # also delete installed skills, then the emptied homeThe reset deletes bazilion.db, auth.json, profiles/, agents/, teams/ and browsers/,
and keeps skills/. It refuses while the daemon runs. Linked Team slots are unlinked; the
projects they point to are not touched. Provider keys and the Telegram setup must be entered
again afterwards.
Work on the source
Section titled “Work on the source”git clone https://github.com/rullopat/bazilion && cd bazilionmise install # Node 26.12.1 and pnpm 12.15.0 from mise.tomlpnpm installpnpm tsx apps/cli/src/index.ts serve # the daemon from source, no build stepcd apps/web && pnpm dev # the web UI on http://127.0.0.1:4322From a checkout every bazilion <cmd> is pnpm tsx apps/cli/src/index.ts <cmd>. After switching
Node versions, run pnpm rebuild better-sqlite3 (or pnpm install --force).
Where to next
Section titled “Where to next”- Core concepts: Profiles, Agents, Teams, policy, memory and the mailbox.
- The web interface: a tour of every page.
- Tools & integrations: web research, the browser, MCP and files.
- Coding with Agents: host or Docker, and repository instructions.
- Connecting Telegram: one topic per Agent.
- Configuration: providers, settings, tokens and the on-disk layout.
- How Bazilion is different: if you are coming from OpenClaw.