CLI: integrations and evals

These commands connect Memory Layer to humans, agents, MCP clients, and evaluation suites.

memory tui

Open the main terminal interface.

memory tui
memory tui --project memory

The TUI gives humans a dense view of memories, query evidence, replacement proposals, agents, watchers, activities, embeddings, errors, and project status.

memory watcher

Watchers attach to active agent sessions and record useful runtime state.

memory watcher manager enable --dry-run
memory watcher manager status
memory watcher run --project memory
memory watcher status --project memory
memory status --project memory

The watcher manager is the preferred local automation path for Codex-linked sessions. Legacy per-project watcher services and foreground watcher runs remain compatibility paths.

memory mcp

Run the local stdio MCP server or inspect service-mounted HTTP MCP.

memory mcp run --project memory
memory mcp status --project memory
memory mcp status --project memory --json

Stdio mode is the normal local Codex/Claude path and must write only MCP JSON-RPC messages to stdout. HTTP MCP is local-first and should require token-bearing clients.

memory eval

Run repeatable memory-quality suites.

memory eval doctor --suite evals/examples/memory-smoke
memory eval run --suite evals/suites/memory-improvement-v1 --condition full-memory --dry-run
memory eval compare --baseline target/memory-evals/no-memory.json --candidate target/memory-evals/full-memory.json --text
memory eval gate --comparison target/memory-evals/comparison.json --policy evals/gates/research-v1.toml

Use dry-runs before shell-enabled suites. Evaluation artifacts are evidence for bounded claims about the suite, model, commit, configuration, retrieval settings, token cost, and latency.