TUI
TUI Guide
The terminal UI is the fastest way to inspect what Memory Layer knows before you act on it. It combines cited query results, stored memory, project health, agent activity, watcher state, proposals, and diagnostics in one local surface.
Start the TUI
memory tui
memory tui --project <project-slug>The header identifies the active project and the footer reports TUI, service, watcher, and skill health. A source checkout uses an isolated dev profile; its header is marked [dev] so it is not confused with a packaged installation.
Shared navigation
| Key | Action |
|---|---|
Tab, Right, or l | Next tab |
Shift+Tab or Left | Previous tab |
h | Open or close help for the active tab |
? | Switch to Query and start a question |
/ | Edit the global text filter |
r | Refresh current project state |
Ctrl+C | Exit |
Choose a tab
| Need | Tab |
|---|---|
| Read or filter known memory | Memories |
| Ask a cited project question | Query |
| Review replacement proposals | Review |
| See active coding sessions | Agents |
| Check watcher liveness | Watchers |
| Inspect the managed skill bundle | Skills |
| See loop state | Automations |
| Generate a handoff briefing | Activity or Resume |
| Maintain semantic retrieval | Embeddings |
| Diagnose a failure | Errors |
| See the whole project at a glance | Project |
The TUI is for human inspection. Agents should prefer structured CLI output such as memory query --json when another tool will parse the result.
See also: Daily workflow and the Web UI.