Console

The console is the surface for humans: a small, fast web app — not a chat app — to browse and manage everything in the cabinet. It's served by the API on the same origin, so if the service is up, the console is up.

// Where it lives

Opening the console #

After install, open http://127.0.0.1:7437. The console is a static Preact bundle that talks to the same REST API you'd curl. Every mutation refreshes the affected views, and a record drawer fetches the full record by typed ID.

// What's inside

The views #

Each screen does one job. The console follows your system's light or dark setting, or you can pick one, and it fits a narrow window as well as a wide one.

Is it healthy?

Home

Service, storage and search status at a glance, anything that needs you, and recent sessions.

Your memory

Review

Facts, sessions and vision in one place. Add, edit, pin and delete, with search and project focus.

Startup

Brief

The exact startup context an agent receives, and how full each lane's budget ran.

Find

Search

Recall across every lane, with score and matched-by on each result.

Wiring

Agents

Connect an agent once; after that it reads and writes memory without you.

This PC

Machines

Where the memory lives, what is stored, and whether search by meaning is on.

Structured data

Databox

Box status, re-index, a schema browser, and a SQL runner with a copyable citation. Appears when Databox is on.

// One cabinet, many projects

Project-aware #

A project switcher scopes the console to the repo you're actually in, derived from recent sessions and remembered across visits. All projects shows the whole cabinet.

// A design rule you can see

Facts stay explicit #

Editing a fact in the console — changing its text, pin, scope, or importance — is an explicit edit in place by id: only the fields you touch change, and a fact re-embeds only when its text does, exactly as the API and MCP do it.