Self-host the web UI

The CLI is complete on its own. The web UI is what turns Boba from a terminal tool into an operator’s console: live transcripts from anywhere, a terminal and diff view over what your agents are doing, a work board, notes, and memories — on your phone as readily as your desk.

The part that makes it different from an ordinary agent front-end: it runs on your backend, not ours. There is no Boba cloud, no account to create, no tenancy to trust. You point it at a Supabase project you own and that is the whole hosted story.

What that buys you

• Your data stays yours. Sessions, documents, memories, and transcripts live in your Postgres. You can query it, back it up, and delete it.
• No vendor in the path. The agent on your laptop and the browser on your phone meet through your project. Nothing routes through a third party.
• Real-time, not polling. Supabase Realtime carries live transcripts, PTY output, and presence over private per-user channels.
• It is just Postgres. The schema is a documented contract, shipped as one SQL file. Nothing is hidden behind an API you cannot inspect.

How the pieces fit

   your machine                    your Supabase project              any browser
┌──────────────────┐            ┌────────────────────────┐        ┌──────────────┐
│  boba daemon     │◀──────────▶│  Postgres + Realtime   │◀──────▶│  web UI      │
│  (owns sessions) │  realtime  │  + Storage             │        │  (Next.js)   │
└──────────────────┘            └────────────────────────┘        └──────────────┘
         ▲                                  ▲
         │  supabaseBridge extension        │  the web app mints short-lived
         │  publishes + subscribes          │  JWTs for headless clients

The daemon stays the owner of every session. Supabase is the meeting point, not the brain: if it goes away, your agents keep running and the TUI keeps working.

Setup, in four steps

Budget about twenty minutes, most of it waiting on Supabase to provision.