I Made the Agent's Memory Visible and It Changed How Everyone Understood the Product

Roopa Ravi — Sun, 12 Apr 2026 14:24:12 +0000

Nobody believed the memory was working.

We had Hindsight integrated, decisions were being retained, recalls were firing — but when you looked at the app, it just looked like a chatbot. You'd ask a question, get an answer, have no idea whether the agent had actually pulled from your history or was just making something up.

The memory was invisible. And an invisible memory layer is indistinguishable from no memory layer at all.

What Retrospect Does

Retrospect is a personal decision memory agent. You log decisions and their outcomes. The agent retains every one using Hindsight agent memory and recalls the most relevant ones when you ask for advice. Gemini 2.5 Flash reasons over the recalled memories to give you personalised, pattern-based guidance.

My job was the frontend. Dashboard, log form, chat interface, insights page. The part everyone sees. And the most important UI decision I made was one I almost didn't make at all.

The Split Layout

The Ask Agent page has two columns. Left: the chat interface. Right: the Hindsight Memory Feed.

The memory feed shows every stored decision as a card. When the agent recalls specific memories to answer a question, those cards highlight. You can see exactly which past decisions the agent pulled and why they were relevant.

This screenshot shows the agent mid-process — "Recalling memories..." before Gemini generates a word. The memory feed on the right shows what it's working with. That moment of visible recall is the entire argument for why memory-powered agents are different from regular chatbots.

I built this layout last. That was a mistake.

Why Visibility Matters More Than I Expected

Before the memory feed existed, we'd demo the agent and people would nod politely. "Interesting." The responses were good — personalised, specific, pattern-based — but nobody could see why they were good. The memory was doing real work invisibly.

After the memory feed: people leaned forward. They'd ask "so it actually pulled those three decisions and used them?" Yes. That's exactly what happened. You can see it right there.

The visibility didn't change what the agent did. It changed whether people believed it.

There's a UX lesson here that applies beyond this project: if your system does something clever under the hood, find a way to surface it. Not in a log file. In the interface. Users don't trust what they can't see.

The Dashboard: Making Confidence Visible

The second most important UI decision was the confidence ring on the dashboard.

That ring sits at 55% with 17 decisions logged. It wasn't always there. Originally the dashboard just showed counts — decisions logged, positive outcomes, patterns found. Informative, but it didn't communicate the most important thing about a memory-powered agent: it gets better over time.

The confidence ring communicates a feedback loop. Log more decisions, the ring grows. Ask more questions, patterns are found. The number isn't mathematically rigorous — it's calculated from recalled memory count and decisions logged — but it tells users something true: the agent isn't fully useful yet, keep going.

Setting that expectation in the UI saved us from having to explain it verbally every time.

The Log Decision Form

The form is deliberately simple.

Four fields: what you decided, which category, what the outcome was, what happened as a result. The category pills are single-select. The outcome selector uses large tap targets — Positive, Neutral, Negative — because the friction of logging needs to be as low as possible. If logging a decision feels like filling out a form, people stop doing it. If it feels like tapping three things and writing two sentences, they keep going.

The result field is the one most people want to skip. I made it required. The result is what makes recall useful — without it, Hindsight is retaining surface descriptions, not outcomes. That field is where the memory actually lives.

The Insights Page

The insights page doesn't use charts. It uses plain English pattern cards: "Your Operations decisions succeed 60% of the time." "Your best performing category is Marketing." "Your most common mistake involves Finance."

I tried charts first. They looked impressive and communicated less. A bar chart of category performance requires the user to interpret it. A sentence that says "your most common mistake involves Finance" doesn't. The goal is pattern recognition, not data visualisation.

What I'd Do Differently

Build the memory feed first, not last.** It's the most important UI element in the entire app. Everything else is scaffolding around it. I spent two days building the dashboard and log form before touching the memory feed, which meant we had a working backend with no visible proof it was working.

Make logging frictionless above everything else.** The agent is only as good as what's been logged. Every field you add to the log form, every extra tap you require, costs you data quality downstream. Design for speed of logging, not completeness of logging.

Confidence is a UX feature.** The number on the ring isn't the point. The behaviour it drives is the point — users who see 55% want to get to 70%. That progress loop is what turns the app from a tool into a habit.

Retrospect gave me agent memory to build on top of. My job was making sure users could see it working. That turned out to be more than half the product.

DEV Community: Roopa Ravi

I Made the Agent's Memory Visible and It Changed How Everyone Understood the Product