Dashboard

The dashboard is mission control for an owner — a read-only window onto your treasury, plus the one red button. It is deliberately not a place to deploy or fund (agents do that); the design principle is "no dashboards in the critical path." A human's job here is to observe and veto, not to drive.

Signing in

On a hosted instance, the dashboard opens to a sign-in gate:

Connect wallet — Phantom, Backpack, or Solflare (any injected Solana provider).
Sign the session message — a one-time signature of olbos.tech session\nwallet: …\nexpires: …. This costs nothing and authorizes no transfer — it only proves you hold the wallet. (See Security — owner auth.)
You're in. The session is cached locally for 24h and replayed as headers; the server verifies the signature on every request.

You see only the treasuries owned by your wallet. If you own none, you'll see an empty state — that's correct, not an error. If you own several agents' treasuries, a switcher appears in the top bar.

Deep link: app.olbos.tech/?strategy=<id> jumps straight to one treasury.

Reading your treasury

AUM (gold) — total managed capital. One of only two places gold appears; it's the single most important number on screen.
APY — your blended, position-weighted net yield.
Strategy — the policy name and template.
Allocation bar — where your capital sits: a solid segment per venue (each venue keeps a stable identity color across every panel), with the liquid buffer shown as hatched glass.
Exposure — each venue's share vs its policy cap, so you can see headroom and any approach to a limit.
Decision feed — plain-English narration of every engine decision for your strategy: APYs sampled, moves proposed, the risk gate passing or blocking, simulations, on-chain confirmations (with explorer links), payouts. This is the audit log, made legible. It's tenant-isolated — you never see another owner's activity.
x402 receipts — the payments made on your treasury.

The kill ring (break-glass)

The torc ring in the top bar is the kill switch. Killing capital should be deliberate, so it's a hold — press and hold ~1.2 seconds and the ring closes (seals shut) around the treasury. Releasing early cancels. When you seal it:

the dashboard asks your wallet to sign olbos:kill:<strategyId>:<ts>;
the engine halts all activity for that strategy and refuses every action until you clear it (a single click to resume, also signed).

Because kill state lives in the event log, even a restarted engine stays sealed.

Beyond the kill switch

The kill switch is fast and reversible. For the terminal option — removing the engine's authority entirely, on-chain, in a way that works even if Olbos is down — use revoke_engine_custody from an owner MCP session or revokeCustody from the SDK. See Custody — break-glass.

Design language (why it looks the way it does)

The dashboard aims to feel like something a professional would pay for — "sleek, premium, minimalist, like a spa in Switzerland." The discipline behind it:

Gold is scarce — it appears about twice per screen (the mark, and AUM). Scarcity is what makes it read as precious rather than gaudy. Everything else is navy-and-mist grayscale.
Liquid glass cards float over an animated aurora light field with film grain — depth without noise.
Icons, never emojis. Every event type has a custom glyph.
Venue identity colors are stable — a venue is the same color in every panel, so the eye tracks it without relabeling.

Two modes

The dashboard serves two postures, set by NEXT_PUBLIC_OLBOS_REQUIRE_AUTH:

Hosted (=1) — wallet sign-in, per-owner scoping, the public product. The market-simulator panel (a localnet demo lever) is hidden.
Operator/localnet (unset) — no sign-in, shows the engine's activity globally, includes the market simulator. This is for running your own single-tenant engine and watching it; it is not the multi-tenant posture.

Next: Custody · Agents · Operations.