The web console
Read the memory in a browser as yourself: what the console shows, who sees what, and how it stays current.
The memory service serves a web console at its own address — http://127.0.0.1:39142/
with the container from Getting started. It is part of the
service binary, so there is nothing else to install or run.
Signing in
Sign in with the name and passphrase you were registered with. The first owner is the
one the container created from TESSARI_AM_OWNER; anyone else is registered by an
administrator (see People and authority).
From then on the console reads as you: every screen shows only what your grants reach, exactly as the MCP and REST surfaces would answer you. Signing out ends the console's token on the service, not only in the browser.
What it shows
The overview spans everything you can read; the other screens show the scope — an identity, a group or a project — picked in the scope picker.
| Screen | What it shows |
|---|---|
| Overview | counts wherever you can read, scope by scope, and the trend of activity |
| Work | the scope's goals and its task board |
| Agents | the sessions working here and what each one holds |
| Activity | what happened, newest first, attributed to the session that did it |
| Documents | artifacts — reports, snapshots, research — read in place |
| Memory | what agents remember, private and team memories included where they reach you |
| Knowledge | facts the project vouches for, with their evidence |
| Search | one search over all of it; / jumps to the search box |
Every record opens with its history and the records it links to. From a record, a task can be moved and a question answered; both are written as you and show up in the activity like any agent's change.
An administrator of an identity also sees Administration: the identity's people, their grants, and its teams.
Staying current
The open screen updates itself when its scope changes — an agent writes, a task moves, a session starts working — without reloading the page. The footer says which state it is in: Live, Reconnecting…, or Live updates stopped, with a button to try again. A grant that is revoked while the console is open closes its live updates within about half a minute.
Behind TLS
The console keeps no cookie: its tokens are bound to a key the browser holds and cannot
export. When the service sits behind a TLS terminator, set TESSARI_AM_PUBLIC_HTTPS=1
so it names itself with https:// and asks browsers to keep to it.