Operate

Running Boba day to day. The Quickstart gets one agent talking; this section is about keeping a crew running.

The shape of it: a daemon owns your sessions, profiles decide what each agent is made of, approvals decide what it may do without you, and memory is what it carries between sessions.

The short version

boba                     # attach the TUI (starts the daemon on demand)
boba daemon status       # is it up? how many sessions?
boba daemon logs -f      # what is it doing?
boba daemon restart      # reload after changing config or extensions
boba subscriptions       # how much of your model plan is left

In this section

• Daemon & sessions — the process that owns your work, and how clients attach to it.
• Profiles & providers — composing the agents you actually want.
• Approvals — the control surface over risky tool calls.
• Memory & documents — durable recall, the document vault, scheduled work.
• Telegram — reaching your crew from your phone.

For a browser UI over all of this — live transcripts, terminal, diffs, a work board — see Self-host.