The control plane

The web app at /app is Engram's governance surface — the place for what can't be embedded in your existing tools: the org canvas, the review queue, administration, and analytics. It's also a full reference client: everything the API can do, you can do here.

The canvas: your organization as a living tree#

The main view renders the workspace as a spatial tree: unit cards for the org and its departments, shelf cards for memory folders, person cards for members, and agent cards for registered agents — connected by edges that mirror the folder hierarchy. Click any node to open it: a unit opens its overview, a shelf opens its memories, a person opens their profile and grants.

Because folders are the permission model, arranging this tree is doing real work: placing a member on a team provisions their folder grant; flagging a folder restricted seals its subtree off from inherited access.

The chat panel#

The right-hand panel is an agentic chat over your memory. It runs on the same persisted conversation service as every other chat surface (/v1/chat), with the full 33-tool registry — so it can search, read, capture, browse the tree, and (for members with the rights) do governance work: list pending approvals, approve a draft, mint a token, check usage stats.

• Answers are cited. Each claim carries a citation chip naming the memory it came from; click through to the node. If nothing accessible covers the question, you get an explicit refusal.
• Mutating actions confirm first. When the chat wants to approve a version, change a role mapping, or mint a token, it files a pending action and renders a confirmation card — nothing executes until you click confirm, and execution re-checks your live permissions at confirm time.
• Conversations persist and are private to you, shared across your devices.

The omnibar and the desktop bubble#

Press ⌘K anywhere in the web app to open the omnibar — quick capture and quick ask without leaving what you're doing. The same component ships inside the desktop bubble (a macOS-first Tauri app in apps/desktop): a floating, always-available capture-and-chat surface authenticated with your personal token. Both are thin frontends over the same chat service — a memory captured from the bubble goes through the identical pipeline as one captured anywhere else.

The review queue#

The approval surface for folders you manage: a queue of draft and reviewed versions, oldest first, with an inline word-level diff against the current approved version (side-by-side toggle available). Actions per item:

• Mark reviewed — a peer-checked signal (contributor+).
• Approve — promote into the trusted corpus (manager only).
• Request changes — back to draft with a note.
• Deprecate — reject or retire; history stays browsable.

Batch selection covers bulk-import review. Drafts that came out of agent task runs carry their task context, so you see what work produced this memory before you sign off on it. Rollback (flipping a node to an older version) is manager-gated and recorded as a lifecycle event, not a deletion.

Library & search#

Browse memories by kind, status, tags, and path, or search across everything you can see. Search is hybrid — semantic (catches paraphrases: “customer refunds” ≈ “returning payments”) fused with full-text (catches exact terms, codes, names) — and permission-trimmed inside the query. Every result shows kind and status badges; an approved-only toggle restricts to the trusted corpus.

Analytics & gap detection#

The org root's Overview is the analytics dashboard: usage, capture and approval throughput, reuse signals, spend per agent job. Its most actionable panel is gaps: failed and low-confidence queries are clustered by meaning, surfacing things like “12 people searched refund workflow — nothing found.” Each gap cluster can be assigned as a documentation stub, turning unanswered questions into a backlog.

Settings#

• Members & teams — invite, set workspace roles, place people on teams (which provisions their folder grants).
• Integrations — org-level connectors: connect with OAuth or pasted credentials, pick scope (teams/repos/projects/channels), choose the destination folder and import mode. See Connectors.
• Account — your personal connected accounts (imports land in your private folder) and personal tokens.
• Tokens — mint and revoke API tokens; secrets are shown once and stored hashed. See API reference.
• Role mappings — translate your company's existing role model into Engram grants for on-behalf-of callers. See Admin & governance.