The web interface
bazilion dashboard runs the web UI on http://127.0.0.1:4322 and connects it to the daemon on
127.0.0.1:4321. The web UI and the CLI offer the same management features.
Sign in and first-run setup
Section titled “Sign in and first-run setup”Sign in on /login with the bootstrap token (bazilion token show-local prints it) or a device
token. The daemon gives the browser a session cookie; the token itself is not stored. A session
ends after 30 days without use.
Until one provider is enabled with a saved model, every page leads to /welcome and the setup
page. Connect ChatGPT or paste an API key, enable the provider and pick a model; Bazilion then
creates a default Profile and a default Team and offers to spawn your first Agent.
Navigation
Section titled “Navigation”The top bar has Chat, Agents and Teams, a Manage menu with Templates, Skills and Setup, the Attention badge, the theme toggle and logout.
Chat (/)
Section titled “Chat (/)”The sidebar lists Agents grouped by Team. Its + menu spawns an Agent from a Profile or a whole Team from a Team template. The main pane streams the selected Agent’s conversation: Markdown, tool calls with a live output tail, delivered files and generated images.
- Attach files with the button, by pasting or by dragging them in. Images reach the model as images; other files are saved for the Agent to read.
- While a turn runs, Send becomes Queue follow-up and Stop cancels the turn (follow-up queue).
- A question from the Agent appears under the chat (questions).
- With
BAZILION_BASH_APPROVAL=dangerous, a flagged shell command shows Allow once and Deny. - Conversations lists earlier conversations and starts a new one (conversations).
- Composer commands:
/new(conversations),/compact(summarise older history) and/context(what the next turn would carry).
Agents (/agents)
Section titled “Agents (/agents)”The list shows active and archived Agents and a spawn form with the destination Team. Each Agent has these tabs:
- Chat: the conversation.
- Inbox: messages from other Agents, with unread state.
- Triggers: interval and cron schedules and their run history.
- Learning: reviewed learning settings and lesson proposals (daily operations).
- Settings: model and reasoning, Team, skills, Telegram, the managed browser, archive and delete.
Teams (/teams)
Section titled “Teams (/teams)”Register a team creates a workspace at ~/.bazilion/teams/<slug>/, or links one to an existing
project directory. Each Team has these tabs:
- Context:
USER.md, Telegram topic names, Docker sandbox defaults and spawning a Team template. - Members: the Team’s Agents.
- Policy: the open/restricted toggle and the allow edges in a Flow or Matrix editor; Save as Team template saves the Team as a new template (Team Policy).
- Memory: search, read and edit the shared Markdown notes.
- Review: Git changes since a base, diffs and file feedback (reviewing what changed).
- Results: saved files and images (results).
Templates (/templates)
Section titled “Templates (/templates)”- Agent templates (
/templates/agents) are Profiles: the default model, skills and theSOUL.md,IDENTITY.md,BOOTSTRAP.md,AGENTS.mdandTOOLS.mdfiles new Agents start with. Edits affect future spawns only. - Team templates (
/templates/teams) are rosters: one slot per Agent (Profile, name, optional model and reasoning), allow edges between slots and a policy mode.
Skills (/skills)
Section titled “Skills (/skills)”Import skills from a local OpenClaw install, a directory or a .zip, see their scan findings, and
remove them. Attach skills through a Profile or on one Agent’s Settings tab.
Setup (/config)
Section titled “Setup (/config)”- Providers (
/config): search the provider list, add credentials or a local endpoint, enable the provider, choose models and run a connection test. Connect ChatGPT signs in with your ChatGPT account. Download backup saves an archive of the home. - Services (
/config/services): the shell sandbox and approval, web search, image generation, Firecrawl and the managed browser. - MCP (
/config/mcp): stdio and Streamable HTTP servers (MCP). - Integrations (
/config/integrations/telegram): Telegram credentials, preflight, pairing, the allowlist and Attention notifications (Telegram). - Tokens (
/config/tokens): device tokens and browser sessions.
A blank secret field keeps the stored value; removing a credential is a separate action.
Attention (/attention)
Section titled “Attention (/attention)”What needs you: lesson proposals, failed learning reviews and triggers, stopped message loops and queues paused after a restart. See daily operations.