Memory Grows a Front End
TestRelic Team
Memory has always done real work in TestRelic — durable, repo-scoped context that powers the MCP server's memory tools and every AI assistant's starting point. What it hasn't had, until this week, is a front end that shows you what it actually knows.
On the platform: a Lifecycle console and a Knowledge workbench
The Memory tab now leads with what your AI assistants have learned from test runs, instead of a bare KPI strip. The new Lifecycle console and Knowledge workbench map memory directly to the tests and conversations it came from — so instead of a list of facts, you get a trail back to why a piece of context exists. A lane switcher pinned to the top makes moving between views faster, now that the six-tile summary strip it replaced is gone.
In the CLI: a read side, finally
The CLI side gets its own read-side UI: a chat memory strip so you can see what's in context without leaving the conversation, and the Memory view itself split into Brief, Suggested, and Settings — a summary, things worth saving, and the toggles that control what gets saved automatically.
The same idea, two surfaces
Neither addition changes what Memory stores or how it's used by MCP tools and the command-line map command — both were already durable and repo-scoped. What changes is that you can now see it, on the web and in the terminal, instead of trusting that it's working.
Get started
Open the Memory tab on any repository, or the Memory view in Studio. See Memory for the platform side and Memory for the CLI/Studio side.