Dashboard
The dashboard is Imprint’s local web interface. It shows what your AI tools remember and where it came from, adds new sources, and runs the same commands as the CLI through the queue. imprint ui open opens it in a browser; the desktop app shows the same pages in its own window. Every action goes through the HTTP API, and every job runs in the active workspace.
Layout
Section titled “Layout”Sidebar. Dashboard, Graph, Search, Chat, Voice, Topics, Projects, Sources, Sync, Settings, Commands and Queue, with the installed version at the bottom. On narrow screens it shows icons only, each with a hint naming the page.
Top bar, on every page:
- While a job runs, a pill shows it, for example
Learn conversations · embedding · 3/112 conversations, and links to Queue. - While Echo is being set up, a pill shows its progress and links to Voice.
- In the desktop app, while Imprint listens for “Hey Echo”, a pill says so, with 1 hour (pause) and Off (Echo voice).
- Update to vX.Y.Z appears when a newer release exists on the update channel: stable releases, or dev builds as well once Settings → Updates is set to dev, which the dialog marks as a dev build (ADR 0108). Its dialog explains the steps for this kind of installation, starts the update, shows the updater’s log and reloads once the new version runs. Memories, workspaces and settings are kept, and running jobs finish first. An installation that cannot update itself says why (ADR 0023, ADR 0050).
- The workspace switcher names the active workspace. Its menu switches to another one (the dashboard reloads), creates one with New workspace… and switches to it, and opens Manage workspaces….
Connection and job notices. When the local service stops answering, a banner says so and offers Retry connection; the dashboard reconnects on its own. A job this tab saw waiting or running is announced when it finishes, fails or is cancelled, whichever page is open; a failure links to Queue.
Dashboard
Section titled “Dashboard”- Add to memory indexes something new: a Folder, a Document, an Audio file, a Web page (with an optional project, fetch-again and link-following options) or Conversations (
imprint learn). Each choice shows the command it runs. The job is queued; the card says whether it started now, waits at a position, or joined an identical job that was already waiting (ADR 0068). Refresh, retag and the rest live in Commands. - The running job is shown with its phase, progress, time so far and left, and Cancel.
- Totals of memories, projects, languages and topics, and their breakdown by project, language, domain and type.
- An empty workspace shows the steps to build a first memory. A memory index built with a different embedding model says it needs rebuilding.
Search
Section titled “Search”- A query box (Ctrl/⌘+K focuses it) with filters for project, memory type, and method: Semantic + exact terms (hybrid, the default) or Semantic only.
- Results show their match type, project and type; the first is selected. Its details show when the source was modified, its content fingerprint, the semantic similarity (a ranking signal, not confidence) and a warning when the source may be stale.
- Open full memory shows the whole memory, and Read in context opens its source at that point.
- Chats are listed by date; each can be renamed or deleted (deleting asks first). The last open chat is reopened.
- Replies come from the configured chat model, local or a provider. Memory searches and reads it makes show as rows that expand to their results. The first message to a local model sets it up and shows the download and load progress.
- A notice says when the model chats without tools, with a link to the chat settings. A reply can be stopped, copied or retried.
- When a long chat no longer fits the model’s context, its oldest exchanges are summarized (“Summarizing the earlier conversation…” shows meanwhile). A divider after the last summarized exchange, Summary of earlier conversation, opens the summary the model now reads in their place. The model can still look up anything said earlier in the chat; that step shows as “Searched earlier in this conversation for …” (ADR 0141).
Topics
Section titled “Topics”- Topics with their memory counts, and a filter. Choosing a topic lists the conversations and files it came from, named by a conversation’s first question, with a project filter when the topic spans projects.
- Read conversation (or Read source) opens the source whole with the topic’s passages marked; clicking an excerpt opens it at that passage.
- Graph shows the topic in the graph; Migrate… copies or moves its memories to another workspace.
?topic=NAMElinks to a topic.
Core memories
Section titled “Core memories”Short statements about you that every agent session receives at its start: preferences, standing instructions, facts about you (ADR 0129). They reach sessions through the MCP server’s handshake instructions and sync to paired devices.
- The strip under the title shows how much of a session’s 2,000 characters the ones for every project take, and says when some no longer fit.
- Add core memory (
n) writes one, active at once, for every project or one project. - Proposed (opens first while any wait) lists suggestions from agents (a stored
preference) and from Organize, with the quote they rest on, where they came from and, for every-project ones, how many characters they would take. Each can be edited, given another kind or scope, approved or rejected. - Active and Retired list the rest; edit or retire an active one, restore a retired or rejected one.
- The lists work like Organize’s: search, a Kind filter and Scope and From selects, 20 rows a page, select several for Approve, Reject, Retire or Restore, and Undo in the toast or
z. Undoing an approval or a rejection returns the core memory to the proposals (ADR 0136)./core/#proposed,#activeand#retiredlink to a tab.
Organize
Section titled “Organize”Run Organize queues a job that writes a short profile of each project, finds a project for memories sitting in catch-alls (no project, Desktop, Code, unassigned, URLs, desktop conversations), and proposes core memories (ADR 0130); its menu runs it without the local helper, which keeps to the folder-path and project-name evidence. With organize.background on, Organize also runs by itself when the queue is idle, after background tagging, and looks only at what changed (ADR 0132).
The strip under the title says whether it runs by itself and when it last passed, whether strong matches move by themselves, the progress of a running pass, and what holds moves back. It also gives the last run and links to the core memory proposals waiting on Core memories. When a run ends, its proposals come in by themselves. The page reviews in four tabs (ADR 0136); /organize/#review, #moved, #decided and #profiles link to one.
- To review lists the proposals that wait, by target project: a rail of projects by count (a select in a narrow window), the largest open first. Each row shows the conversation’s first question or the source, where it is from, the evidence (the project’s folder path, its name, or a quote the local model found, with the project’s name marked) and, with
organize.auto_moveoff, Strong evidence. Move or Keep here decides one; Move all or Keep all the project’s group; a finished group offers the next. Click a row or press Enter for its preview, the whole quote, the project’s profile and Read source. A move is a placement rule, so it holds through refreshes. - Moved automatically lists the sources Organize moved by itself because the evidence was strong: the source names exactly one project’s folder, or one distinctive project name at least twice and no other, early in what it says (ADR 0133). New since you last looked shows those after the last Mark all as seen in this browser. Move back moves one back and keeps it there; Move back all a project’s group, after a confirmation.
organize.auto_moveoff sends these to review instead. - Decided lists your moves and keeps, and moves back, newest first; Reopen returns one to review, moving it back first if it was moved.
- Profiles shows what Organize thinks each project is, with links to the sources waiting to move there and those moved there by themselves; search and chat find the profiles too.
- Every list has a search, filters, 20 rows a page (10 or 50 are remembered in this browser) and checkboxes for deciding many rows at once. A decision shows at once with Undo in its toast; writes go to the server one request at a time, and one that fails comes back with its error and Retry. While a job holds the ingestion lock, Move and Move back wait; Keep here still works.
- Keyboard:
j/kmove between rows,amoves,rkeeps,umoves back or reopens,xselects, Enter opens a row,oreads its source,zundoes,[/]change page,/searches,1–4switch tabs, and?lists them all, with a switch that turns single-key shortcuts off. - Moves, proposals and decisions reach paired devices (ADR 0134).
Projects
Section titled “Projects”Projects and Sources work like Organize: tabs linked from the address, paged lists with a search, filters and checkboxes, and the same keys (ADR 0139).
- A rail lists the projects by memory count (a select in a narrow window), with a filter. The open project is in the address (
/projects/?project=NAME); without one, the last project opened in this browser opens, else the largest.JandKstep through them. - The project’s line gives its memories and sources, Graph, Move or merge…, which moves or merges the whole project into another after a review of what moves (ADR 0036), and Migrate…, which copies or moves it to another workspace.
- Overview (
#overview) shows what Organize’s profile says the project is, its sources by kind (each opens them on the Sources tab), and its topics (each opens in Topics), kinds of memory, domains and languages as proportional bars. - Sources (
#sources) lists the project’s sources as the Sources page does, with Move N to… for the selected ones. A source linked from another project shows where it belongs and cannot be moved from here. - Project associations… lists suggested links from sources to other projects; each can be accepted, rejected or removed, and Analyze existing sources queues a new analysis (ADR 0099). A source’s menu opens them for just that source.
Sources
Section titled “Sources”Three tabs, linked as /sources/#indexed, #excluded and #roots; they act on the workspace the top bar shows.
- Indexed lists every source of the workspace, largest first, 20 a page (10 or 50 are remembered in this browser): a conversation by its first question, a file by its name and folder, with its project, kind, age and chunks. Search titles and paths; filter by kind (conversations, files, documents, web pages, pasted content, and memories without a snapshot) and project; sort by size, recency or name.
- Read (
o) opens the source whole. A click or Enter opens its details: where it was recorded, its tags and topics, and its chunks a few at a time, each readable in place. Its menu shows it in the graph, moves it to another project, links it to another, copies or moves it to another workspace, or purges it. - Select sources of one project to move them together. When an ingest, a move or sync changes the workspace while the list is open, a note offers Refresh instead of moving rows under the cursor.
- Excluded lists what purges keep out of ingestion, each with Allow re-ingestion. Purge a path…, or Purge… in a source’s menu, previews what matches a source key or a file or directory path, and applies once the workspace’s name is typed (ADR 0015).
- Roots edits the folders the workspace may ingest from.
- Keyboard:
j/kmove between rows,xselects, Enter opens a row,oreads it,mmoves it,aallows an excluded path again,[/]change page,/searches,1–3switch tabs, and?lists them all.
- Projects, topics, sources and chunks as a graph. Click selects a node and shows its details; double-click opens it. Breadcrumbs lead back up, and the scope is in the URL (
?scope=project:X,topic:X,source:Xorchunk:X), so back, forward and links work. - Find in graph (
/focuses it) highlights matches; Enter and Shift+Enter step through them and Escape clears. - The details list a node’s connections by kind, copy a source’s path, read a source in full and can limit the graph to a node’s connections. On phones they are a bottom sheet.
- The legend hides or shows each kind of node. The toolbar zooms, fits, re-runs the layout and opens display and layout settings, which this browser remembers.
Imprint runs one job at a time (ADR 0064).
- Running shows the current job with its progress, newest output line, full output on request and Cancel.
- Up next lists waiting jobs; each can be removed. A job that absorbed identical requests shows how many.
- Background work shows the state of LLM tagging and background Organize, which fill idle time: memories waiting for tagging, workspaces Organize has not seen as they are, and Resume now when it waits after a cancel or failure (ADR 0067, ADR 0132).
- History lists finished jobs. Any job opens a panel with its parameters, workspace, times, process, command and output.
Commands
Section titled “Commands”The CLI’s commands as forms, grouped as the CLI lists them. The catalog comes from the server (GET /api/commands), so a command added to the CLI appears here without a dashboard change.
- Index: Find project associations, Learn conversations, Ingest directory (a folder or a file), Refresh files, Ingest URL, Refresh URLs.
- Maintain: Retag memories, Scrub secrets, Export snapshot.
- Clients: Connect clients and Disconnect clients, for one client or all, with each client’s connection state. They only change client settings: connecting installs and starts nothing, and disconnecting stops neither the dashboard nor Qdrant (ADR 0053). Disconnecting asks first.
- Inspect: Status, Diagnose and Show config.
Run queues the command, and its output streams into the panel beside it. Leaving the page does not cancel the job.
- Live sync serves a workspace (two-way, send only or receive only, optionally through a relay) and shows a code to enter on the other device, or receives with such a code. The serving device approves each request once or trusts the device; a push asks before it sends (sync).
- Paired devices lists devices paired for automatic sync, with their state and when each was last seen. Automatic sync can be paused and resumed; a device can be forgotten on both devices or removed from this one, each confirmed first (ADR 0020, ADR 0073).
- Snapshots downloads a workspace snapshot or imports one. Desktop App Exports scans Downloads for Claude Desktop and ChatGPT Desktop exports and lists those indexed.
Settings
Section titled “Settings”One section at a time, chosen from a list; #settings-chat, #wsl and the other section ids link to a section. The filter searches every section and counts the matches in each.
Each setting has a one-line description and, under What is this for?, what it controls, what changing it does (speed, memory, what leaves the machine, what has to be reindexed) and a worked example. The text lives in imprint/config_help.py, which a test keeps complete for every setting; the filter searches it too. Settings that currently have no effect say so.
- Configuration edits the same values as
imprint config, in this device’sconfig.json(configuration). A value set by an environment variable is read-only. Reset (Remove, for a secret) deletes theconfig.jsonoverride. Running servers apply changes when they restart. - This device: Workspaces creates, switches, edits the roots of, wipes and deletes workspaces, and copies or moves memories between them; wiping and deleting are confirmed by typing, and the default and active workspaces cannot be deleted. WSL profiles appears only on a Windows installation; macOS and Linux omit it from navigation and settings search and ignore its deep link. On Windows it checks each distribution’s clients (checking starts stopped distributions) and enrolls or removes them through the queue.
Recordings
Section titled “Recordings”Records a call or meeting: your microphone and, if you choose, what this computer plays (ADR 0131).
- Start recording needs a title and project (default
meetings) and your confirmation that everyone on the call knows it is being recorded. On Windows the desktop app records what the computer plays directly; a browser asks which tab or screen to share, with its audio. Without it, only the microphone is recorded, and the page says so. - While recording, the top bar shows the time and Stop on every page. Stopping queues the transcription.
- In the desktop app, with the dashboard hidden, the floating Imprint button’s Record satellite opens a small panel with the same title, project, computer-audio switch and confirmation. The dashboard records in the background, moving to Recordings first. While recording, the button shows the time and a red rim, and its actions offer Stop and the levels. Quitting during a recording asks first and saves what was recorded (ADR 0135).
- Each recording lists its state, its transcript (“You” for the microphone, “Others” for the computer’s audio, with times), Listen, Transcribe again, Delete audio (keeping the transcript) and delete. A recording whose window closed shows Finish and transcribe.
- The audio stays in
data/recordings/on this device; the transcript is the sourcerecording/<id>and syncs like other memories.
Echo, the voice companion (live voice).
- The first visit sets Echo up: Download & set up Echo fetches its runtime and models, with its progress.
- Start conversation starts talking, by push to talk or hands-free; a reply can be interrupted, and a thought can also be typed.
- Companion settings picks the reasoning model (the chat model, or the small LFM voice model), the microphone and speaker, and the microphone options; the picker chooses Echo’s look and voice.
- Float Echo opens Echo in its own small window: the desktop companion window, or a browser popup. Voice stops when the page is hidden.
Shared behavior
Section titled “Shared behavior”Approving a root. Ingest and refresh only read inside a workspace’s approved roots. When a job from any page asks for a folder outside them, the dashboard asks “Approve
Reading a whole source. Topics, Projects, Sources, Graph and a memory’s Read in context open a conversation or file whole from its stored snapshot. A conversation shows its messages in order, with tool calls and their output, thinking and injected context folded between them; opened for a topic, its passages are marked and stepped through (ADR 0094).
Lists and details. Topics, Commands and Settings show a list beside the details; Projects shows its rail beside the open project. On wide screens both scroll on their own and the header stays put; below that they stack and the page scrolls.
Picking a path. Folder and file pickers browse the server’s filesystem, so paths are the service’s own: on a Windows installation, WSL folders are under \\wsl.localhost\<distribution>.
Copying or moving between workspaces. Migrate… on Topics and Projects, Copy or move to a workspace… in a source’s menu on Projects and Sources, and Copy / move memories… in Workspaces, copy (the default) or move memories by project, topic or source, with a dry run first.
Desktop app
Section titled “Desktop app”- The window opens a splash while the local service starts, with the startup log and Try again when it fails (ADR 0025).
- Closing or minimizing hides the window to the tray and leaves Imprint running, with a small floating button to open it again. Hidden, the dashboard leaves the taskbar, and on macOS the Dock; the floating button and Echo never show there. Quit Imprint (sidebar, tray, or the floating button’s menu) stops the app and its background service.
- The tray opens the dashboard, floats Echo or quits; while “Hey Echo” is on, its first line says whether Imprint listens, with pause, resume and off. The top bar’s Floating Echo switch shows or hides Echo’s window.
- The window’s empty top bar and the sidebar header move it. While a dialog, menu or popover is open they do not, so the overlay stays usable (ADR 0039).
Design and tests
Section titled “Design and tests”The dashboard uses one component kit, vendored shadcn components on Base UI (ADR 0039), with a light, black-and-white theme and the bundled Inter font (ADR 0008). Playwright tests under imprint/ui/tests drive the pages against mocked API responses, at desktop, tablet and phone widths. They are not an accessibility certification or a native desktop check; see platform validation for what has run on each platform.