Bazilion documentation

Bazilion is a personal, open-source, local-first multi-agent runtime built on Pi’s coding agent as its core engine. Pi runs the per-turn loop, stores the JSONL transcript, handles replay and compaction, executes providers and tools, and supplies the coding tools.

Bazilion wraps that engine with a small daemon on your own machine, a workspace under ~/.bazilion, Agent templates, revisioned Team Templates, Teams, live communication policy, shared files, memory, and messages — all under your own control, with your own provider keys.

It is not a hosted platform. It is a daemon, a CLI, and a web UI you run yourself, published under the MIT license.

Bazilion 0.22.0 gives protected Agents eyes: image generation with honest spend, and opt-in bounded web discovery. 0.21 ended the alpha clean-install era — schema migrations run forward on startup behind a verified pre-migration snapshot, web tokens carry per-device scopes, and a bazilion-pair:// setup code pairs a new device in one paste. The engine is Pi 0.87.1. 0.20.x homes upgrade automatically; 0.19.x and earlier are refused cleanly and need a reset. Bazilion remains alpha. Read what changed in 0.22.0.

• Coding during an Agent task: repository context and scoped commands.
• Saved results and conversations.
• Follow-up queue and Agent questions.

Getting started Install the daemon, boot it, and finish first-run setup.

Core concepts Agent templates, Team Templates, Teams, policy, approvals, and memory.

Tools & integrations Shell isolation, command approval, browser automation, MCP, and files.

Configuration Providers, secrets, tokens, and the on-disk layout.

Operate your installation

• Daily operations — diagnose failures, inspect schedules, decide approvals, and review lessons.
• Backup and recovery — protect the home and linked projects, rehearse restores, and recover credentials.
• Private access and mobile pairing — prepare the protected runtime, publish through Tailscale Serve, and pair each device.

How the pieces fit

Agent templates become agents

A Profile is an Agent template — SOUL.md, IDENTITY.md, tools, skills mode, and a default model. Spawning it creates a permanent live Agent.

Pi runs the agent loop

Bazilion is based on Pi’s coding agent for the session loop, transcript, compaction, provider/tool execution, and coding tools.

One reusable Team roster

A Team Template owns revisioned stable slots and directed communication edges. Spawning a reviewed revision materializes its Agents atomically.

One effective live policy

Every Team owns exactly one revisioned policy. Edges allow directly or hold one typed attempt for approval; a missing edge denies during enforcement.

A mailbox between them

Agents coordinate through a durable mailbox: send_message, read_inbox, and wait_for_reply in the loop, plus CLI, API, and web surfaces.

Shared memory, indexed

Each Team has one memory rooted at <team>/memory, indexed with qmd (BM25 over markdown) so every member can search it.