Skip to content
Web UI tour

Web UI layout

A top bar plus three panes. Numbers map to the cards below.

RECALL/ search 150,000 messagesrefreshPROJECTSSESSIONSTRANSCRIPTstatscopy1234
  1. Top bar

    Counters, search box (press / to focus), all-projects toggle, manual refresh.

  2. Projects pane

    Every directory you ran Claude Code in, ordered by recency. Click to filter the middle pane.

  3. Sessions pane

    Sessions in the active project. Pin with star, alias, opening prompt preview, badge if a note exists.

  4. Transcript pane

    Full message replay. Header has alias, stats, action buttons. Notes section is collapsible.

Web UI

The default view is a three-pane browser. Beyond it there are nine more full-screen views, every one reachable from the top bar.

#The tri-pane browser (the default)

Projects on the left, sessions in the middle, transcript on the right. This is what recall open gives you when no view is selected.

  • Search: full-text across every message; #tag-name filters by tag; press / to focus
  • Source: a segmented All / Claude Code / Codex control in the sessions pane header; it narrows the history list, the search results and the live terminal rows to one agent
  • Sessions list: row densities adjust to viewport; load more after 500 messages
  • Transcript: per-code-block copy on hover; markdown via strict DOMPurify allowlist
  • Resize: grab the right edge of the sessions pane; Cmd+\ collapses to a rail

#The Codex badge and the Source filter

A Codex chip marks every session Codex wrote. Claude Code rows carry no chip, because they are the default and the large majority; a row from a source Recall does not recognise gets no chip either, rather than an invented label. The chip follows the session everywhere it is listed: the sessions list, search results, the transcript header, the command palette, the Cognitive Graph, the bug-pattern views and the thread dialogs.

The Source control is URL-addressable. Your choice rides in the address bar as src=claude or src=codex, so a filtered view survives a reload and can be pasted to someone else; All is the default and is left out of the URL. A URL with an unrecognised src value falls back to All instead of showing you nothing. One vocabulary runs all three surfaces: all, codex, and claude (which the CLI and MCP also spell claude-code).

#Live terminal rows

Terminals running right now sit above the history list, newest first, marked Open. A tab that has launched but has not been typed in yet reads "Waiting for conversation". Recall checks these against the real process table, so a row disappears when the process does. They are hidden while a search, collection or date filter is active, and a session shown as live is never also listed as history.

#The other nine views

ViewWhere it livesWhat it is for
StatsInsights menuCost and token dashboard: daily spend rolling up to weeks and months, token composition, your ten costliest sessions, busiest repos. 7d / 30d / all.
ThreadsTop barTwo-pane thread workspace: threads grouped by project on the left, the selected thread's session tree on the right. Rename, close, archive, add a session, title a whole thread in one go.
BucketsTop barYour own folders of documents, encoded once and searchable from any repo. One card per bucket with document and passage counts, an open / local-only switch, and an ask box that answers from passages and shows a receipt.
Cognitive GraphTop barEvery indexed session in a project drawn as a star, with thread families joined into constellations. See below for what fills it.
PatternsTop barRecurring bug fingerprints: how often each recurred, over what date span, with an example error and the sessions it came from. Mark a fix as working, split a cluster, reopen one.
Review queueTop barProposed links between sessions waiting for your yes or no: source, target, link type, confidence, and the evidence behind each. Approve or reject singly or in bulk.
DecisionsInsights menuHow many prompts you personally typed, by day and by repo, with average, peak and active hours.
Auto-collectionsCollections areaRules that file sessions into collections by folder, project, tag, plan file or git branch. Suggested rules come with a preview before you accept.
FleetInsights menuContext-window gauges for sessions whose terminal is still open, fullest first, grouped by repo. Refreshes every 5 seconds.

Fleet and the live rows answer different questions. A live row means Claude Code or Codex is running in that tab at this moment. A Fleet row means that terminal's shell is still open, which is a weaker claim, and without the editor extension Fleet falls back to "active in the last 30 minutes" and labels itself as such.

#What fills the Cognitive Graph

The stars are automatic, the connections are not. Every indexed session in the project is already a node; one with no thread link simply floats free. What you have to run is the part that draws the lines:

bash
recall thread scan --apply     # infer parent-child links and write them
recall thread scan             # preview only, writes nothing
recall thread sync             # link terminals running in this repo now

Threads you build by hand in the Threads view count too. An empty graph means the project has no visible sessions yet, not that inference is missing.

Semantic search is unrelated to this view: turning vectors on or off changes nothing here, and thread scanning works with or without them.

Last updated