---
title: "Hindsight"
type: "AI Tool"
url: "https://aidemos.com/tools/hindsight"
description: "We tested Hindsight's panel and graph views on preferences, client context, and continuity. Older memories still appeared after forget requests."
category: "developer-tools"
website: "https://ui.hindsight.vectorize.io"
published: "2026-07-15T08:37:13.591802+00:00"
updated: "2026-07-15T08:37:13.591802+00:00"
evidenceCount: 39
verifiedCount: 0
coverage: "partial"
---

# Hindsight

Selective, inspectable memory for real agent workflows, with strong retrieval and scope control.

`User, client, and project memory` · `Scope isolation` · `Graph observability` · `Free signup credits`

**Website:** [Visit Hindsight](https://ui.hindsight.vectorize.io)

## Evidence (first-party, tested)

*39 tested cells · 0/39 artifact-verified. Scores are out of 5. Cite a cell by its Evidence ID, e.g. `ev:hindsight·team-handoff-project-continuity-memory·correct-application`.*

| Criterion | Scenario | Verdict | Score | Tested | Proof | Evidence ID |
| --- | --- | --- | --- | --- | --- | --- |
| Correct application | Team Handoff / Project Continuity Memory | ✓ worked | — | — | 🧾 [proof](https://d3epheqghktydj.cloudfront.net/hindsight-hindsight-input3-handoff-note-generated-ef0b99841217.png) | `ev:hindsight·team-handoff-project-continuity-memory·correct-application` |
| Correct Application | Personal Work Brain Memory | ✓ worked | — | — | 🧾 [proof](https://d3epheqghktydj.cloudfront.net/hindsight-hindsight-input1-formal-email-boundary-c-239af8501813.png) | `ev:hindsight·personal-work-brain-memory·correct-application` |
| Correct Application | Client Relationship Memory | ✓ worked | — | — | 🧾 [proof](https://d3epheqghktydj.cloudfront.net/hindsight-hindsight-input2-acme-sso-followup-no-re-205dd01f1a75.png) | `ev:hindsight·client-relationship-memory·correct-application` |
| Correct Application | Team handoff and project continuity memory | ✓ worked | — | — | — | `ev:hindsight·team-handoff-and-project-continuity-memory·correct-application` |
| Correct Application | Delete / Forget Memory Control | ◐ mixed | — | — | — | `ev:hindsight·delete-forget-memory-control·correct-application` |
| Dashboard / UI | cross-scenario | ✓ worked | — | — | 🧾 [proof](https://d3epheqghktydj.cloudfront.net/hindsight-hindsight-experience-graph-b0a30605da35.png) | `ev:hindsight·cross·dashboard-ui` |
| Delete / Forget Support | Delete / Forget Memory Control | ◐ mixed | — | — | 🧾 [proof](https://d3epheqghktydj.cloudfront.net/hindsight-hindsight-input4-forget-request-submitte-8109cb97a1e2.png) | `ev:hindsight·delete-forget-memory-control·delete-forget-support` |
| Delete / Forget Support | Delete or forget memory control | ◐ mixed | — | — | — | `ev:hindsight·delete-or-forget-memory-control·delete-forget-support` |
| Developer Integration | cross-scenario | ✓ worked | — | — | — | `ev:hindsight·cross·developer-integration` |
| Memory capture quality | Client Relationship Memory | ✓ worked | — | — | 🧾 [proof](https://d3epheqghktydj.cloudfront.net/hindsight-hindsight-input2-acme-client-memory-crea-6141d2a6a3ca.png) | `ev:hindsight·client-relationship-memory·memory-capture-quality` |
| Memory capture quality | Delete / Forget Memory Control | ✓ worked | — | — | 🧾 [proof](https://d3epheqghktydj.cloudfront.net/hindsight-hindsight-input4-formal-tone-memory-crea-4cb0175ddc49.png) | `ev:hindsight·delete-forget-memory-control·memory-capture-quality` |
| Memory capture quality | Team Handoff / Project Continuity Memory | ✓ worked | — | — | 🧾 [proof](https://d3epheqghktydj.cloudfront.net/hindsight-hindsight-input3-project-rules-retrieved-2adbc5e879dc.png) | `ev:hindsight·team-handoff-project-continuity-memory·memory-capture-quality` |
| Memory Capture Quality | Personal Work Brain Memory | ✓ worked | — | — | 🧾 [proof](https://d3epheqghktydj.cloudfront.net/hindsight-hindsight-input1-founder-work-preference-23e99e40f8f0.png) | `ev:hindsight·personal-work-brain-memory·memory-capture-quality` |
| Memory Capture Quality | Team handoff and project continuity memory | ✓ worked | — | — | — | `ev:hindsight·team-handoff-and-project-continuity-memory·memory-capture-quality` |
| Observability | Client Relationship Memory | ✓ worked | — | — | 🧾 [proof](https://d3epheqghktydj.cloudfront.net/hindsight-hindsight-input2-acme-update-handled-wit-e6d659eaba02.png) | `ev:hindsight·client-relationship-memory·observability` |
| Observability | cross-scenario | ✓ worked | — | — | 🧾 [proof](https://d3epheqghktydj.cloudfront.net/hindsight-hindsight-input2-acme-update-handled-wit-e6d659eaba02.png) | `ev:hindsight·cross·observability` |
| Observability | Delete / Forget Memory Control | ✓ worked | — | — | — | `ev:hindsight·delete-forget-memory-control·observability` |
| Observability and Debugging | cross-scenario | ✓ worked | — | — | — | `ev:hindsight·cross·observability-and-debugging` |
| Observability and Debugging | Delete / Forget Memory Control | ✓ worked | — | — | — | `ev:hindsight·delete-forget-memory-control·observability-and-debugging` |
| Observability and Debugging | Team Handoff / Project Continuity Memory | ✓ worked | — | — | — | `ev:hindsight·team-handoff-project-continuity-memory·observability-and-debugging` |
| Privacy and Safety | cross-scenario | ◐ mixed | — | — | — | `ev:hindsight·cross·privacy-and-safety` |
| Relevant retrieval | Client Relationship Memory | ✓ worked | — | — | 🧾 [proof](https://d3epheqghktydj.cloudfront.net/hindsight-hindsight-input2-acme-sso-followup-no-re-205dd01f1a75.png) | `ev:hindsight·client-relationship-memory·relevant-retrieval` |
| Relevant retrieval | Team Handoff / Project Continuity Memory | ✓ worked | — | — | — | `ev:hindsight·team-handoff-project-continuity-memory·relevant-retrieval` |
| Relevant Retrieval | Personal Work Brain Memory | ✓ worked | — | — | 🧾 [proof](https://d3epheqghktydj.cloudfront.net/hindsight-hindsight-input1-internal-update-memory--1dc2911e7f3a.png) | `ev:hindsight·personal-work-brain-memory·relevant-retrieval` |
| Reliability across sessions | cross-scenario | ◐ mixed | — | — | 🧾 [proof](https://d3epheqghktydj.cloudfront.net/hindsight-hindsight-input1-founder-work-preference-23e99e40f8f0.png) | `ev:hindsight·cross·reliability-across-sessions` |
| Reliability across sessions | Team Handoff / Project Continuity Memory | ✓ worked | — | — | — | `ev:hindsight·team-handoff-project-continuity-memory·reliability-across-sessions` |
| Reliability across sessions | Client Relationship Memory | ✓ worked | — | — | — | `ev:hindsight·client-relationship-memory·reliability-across-sessions` |
| Reliability across sessions | Delete / Forget Memory Control | ◐ mixed | — | — | — | `ev:hindsight·delete-forget-memory-control·reliability-across-sessions` |
| Reliability Across Sessions | Personal Work Brain Memory | ✓ worked | — | — | 🧾 [proof](https://d3epheqghktydj.cloudfront.net/hindsight-hindsight-input1-founder-work-preference-23e99e40f8f0.png) | `ev:hindsight·personal-work-brain-memory·reliability-across-sessions` |
| Reliability Across Sessions | Delete or forget memory control | ◐ mixed | — | — | — | `ev:hindsight·delete-or-forget-memory-control·reliability-across-sessions` |
| Scope Control | Team Handoff / Project Continuity Memory | ✓ worked | — | — | 🧾 [proof](https://d3epheqghktydj.cloudfront.net/hindsight-hindsight-input3-unrelated-project-scope-413787ca4ea3.png) | `ev:hindsight·team-handoff-project-continuity-memory·scope-control` |
| Scope Control | Client Relationship Memory | ✓ worked | — | — | 🧾 [proof](https://d3epheqghktydj.cloudfront.net/hindsight-hindsight-input2-betacorp-scope-isolatio-5008d90d2a2b.png) | `ev:hindsight·client-relationship-memory·scope-control` |
| Scope Control | Team handoff and project continuity memory | ✓ worked | — | — | — | `ev:hindsight·team-handoff-and-project-continuity-memory·scope-control` |
| Scope Control | Personal Work Brain Memory | ✓ worked | — | — | — | `ev:hindsight·personal-work-brain-memory·scope-control` |
| Update and Correction Handling | Client Relationship Memory | ✓ worked | — | — | 🧾 [proof](https://d3epheqghktydj.cloudfront.net/hindsight-hindsight-input2-acme-memory-update-ackn-f37e5822de00.png) | `ev:hindsight·client-relationship-memory·update-and-correction-handling` |
| Update and Correction Handling | Team handoff and project continuity memory | ✓ worked | — | — | — | `ev:hindsight·team-handoff-and-project-continuity-memory·update-and-correction-handling` |
| Update and Correction Handling | Team Handoff / Project Continuity Memory | ✓ worked | — | — | — | `ev:hindsight·team-handoff-project-continuity-memory·update-and-correction-handling` |
| Update handling | Team Handoff / Project Continuity Memory | ✓ worked | — | — | 🧾 [proof](https://d3epheqghktydj.cloudfront.net/hindsight-hindsight-input3-project-direction-updat-3f60edff97dc.png) | `ev:hindsight·team-handoff-project-continuity-memory·update-handling` |
| Update handling | Client Relationship Memory | ◐ mixed | — | — | 🧾 [proof](https://d3epheqghktydj.cloudfront.net/hindsight-hindsight-input2-acme-update-handled-wit-e6d659eaba02.png) | `ev:hindsight·client-relationship-memory·update-handling` |

> 🧾 = artifact-verified (proof captured) · 👁 = observed (noted, no artifact) · verdicts: worked / mixed / struggled / failed.

> **Strong memory workflows, but delete/forget still needs repeat validation.**
>
> Hindsight handled user preferences, client context, project continuity, and scope isolation well, and its panel and graph views make retrieval easy to inspect. The main caveat is that older memories still remained visible after update and forget requests, so deletion and retirement are only partially proven in this report.

## Demo Recording

[Video: Hindsight demo recording](https://d3epheqghktydj.cloudfront.net/hindsight-hindsight-demo-walkthrough-6802b881208f.mp4)
*Video — Screen recording of the Hindsight workflow and memory panel used during testing.*

## Feature-by-Feature Breakdown

### Persistent Memory Capture and Retrieval

**Verdict:** Pass

Hindsight stores durable working-style preferences and client troubleshooting context, then reuses them later to shape replies and avoid repeating basics. In the founder_001 flow it kept the user's short/direct, proof-first, safe-next-step, non-motivational style; in ACME it kept SSO/login history and steered later replies toward IdP/configuration checks.

**Input:**

```
Session 1 under user_id founder_001: the user asked Hindsight to remember how they work — keep outputs short, direct, and copy-paste ready; avoid polished or motivational writing; always mention what proof or artifact is needed before making strong claims; and give the safest next step when something is risky or unclear.
```

**Output:**

**Input:**

```
Session 2 under user_id founder_001: the user asked for a short internal update about what they worked on today and what the team should test next.
```

**Output:**

**Input:**

```
Session 3 under user_id founder_001: the user asked for a formal email to a potential enterprise partner about a product demo next week.
```

**Output:**

**Input:**

```
Session 1 under account_id client_acme_001: ACME was already a support client, had tried password reset, clearing browser cache, and switching browsers, and the remaining issue was only affecting users with SSO enabled.
```

**Output:**

**Input:**

```
Session 2 under account_id client_acme_001: ACME asked what to try next because users still could not log in with SSO.
```

**Output:**

**Input:**

```
Session 3 under account_id client_acme_001: the client memory was updated to say ACME was no longer using SSO for this rollout and had moved to email-password login for the first launch.
```

**Output:**

**Input:**

```
Session 4 under account_id client_acme_001: ACME said some users were still unable to log in during launch testing and asked for the next support reply.
```

**Output:**

**Input:**

```
Follow-up evidence for the same ACME update case after the rollout change and login complaint.
```

**Output:**

**Bottom line:** Strong capture and reuse of working-style memory, with good boundary control; Session 2 was slightly more structured than the user's strict shortest-tone preference.

### Project-Scoped Memory and Scope Control

**Verdict:** Pass

Hindsight preserves project-specific direction and handoff rules while keeping unrelated projects separate. In the AI Demos project it retained the shift from QA-style inputs to real workflows, the proof-first rule set, and the handoff-note requirements, while leaving the sales project unaffected.

**Input:**

```
Session 1 under project_id ai_demos_memory_use_case: the project was defined as Memory for AI Agents, focused on real continuity across personal work brain, client relationship memory, and team handoff workflows.
```

**Output:**

**Input:**

```
Session 2 under project_id ai_demos_memory_use_case: the project rules emphasized proof-first observations, screenshots and artifacts as primary evidence, ranking value, practical user-facing writing, and evaluation of retrieval, update handling, scope control, deletion or retirement, and observability.
```

**Output:**

**Input:**

```
Session 3 under project_id ai_demos_memory_use_case: the direction changed from QA-style inputs to real workflows such as personal work brain memory, client relationship memory, and team handoff/project continuity.
```

**Output:**

**Input:**

```
Session 4 under project_id ai_demos_memory_use_case: create a handoff note for an intern who needs to continue the use case and explain the use case, current testing direction, observation rules, and artifacts to capture.
```

**Output:**

**Input:**

```
Session 5 under project_id unrelated_sales_agent_project: create a short kickoff note for a different sales email agent project.
```

**Output:**

**Bottom line:** Strong project memory and scope isolation: it preserved the working rules, captured the direction change, and kept the unrelated sales project separate.

### Memory Update and Forget Handling

**Verdict:** Pass with caution

Hindsight accepts corrections and retirement requests, and later outputs reflect the updated instruction even if older memories were still visible in this report's custom test panel. In the ACME rollout correction it switched from SSO to email-password login, and it later marked the formal-tone preference as discontinued.

**Input:**

```
Session 3 under account_id client_acme_001: update the client memory to say ACME is no longer using SSO for this rollout and has moved to email-password login for the first launch; do not keep treating SSO as the active issue unless they mention it again.
```

**Output:**

**Input:**

```
Follow-up evidence after the ACME rollout update: ACME said some users were still unable to log in during launch testing and asked for the next support reply.
```

**Output:**

**Input:**

```
Session 1 under user_id delete_memory_001: remember this preference — whenever you write updates for me, use a very formal corporate tone.
```

**Output:**

**Input:**

```
Session 2 under user_id delete_memory_001: forget this preference and do not keep using the formal corporate tone anymore.
```

**Output:**

**Input:**

```
Session 3 under user_id delete_memory_001: write a short internal update about today's memory-tool testing work.
```

**Output:**

**Bottom line:** Pass with caution: newer instructions influenced later outputs, but the old ACME SSO and formal-tone memories were still visible after update and forget requests, so retirement was not fully proven.

### Memory Observability and Graph Inspection

**Verdict:** Pass

Hindsight surfaces stored memory state and relationships in the UI for inspection. The Experience and Observations graph views show nodes, link counts, and type breakdowns so users can audit what memory is being held.

**Input:**

```
Inspect the Experience graph view for the active memory bank.
```

**Output:**

**Input:**

```
Inspect the Observations graph view for the active memory bank.
```

**Output:**

**Bottom line:** Strong observability: the graph views make stored memories, links, and type counts visible enough to audit and compare.

## Usage-based credits with free signup credits

The report says Hindsight uses a credit model and applies free credits automatically at signup.

| Plan | Price | Notes |
| --- | --- | --- |
| Free signup credits ★ (tested) | ~$5 | Automatically applied at signup; the report says all testing was done on free credits. |
| Usage-based credits | 1 credit = $1 USD | Core billing model described in the report. |
| Credit packs | $10 / $25 / $50 / $100 | Reported packs include a 33% bonus credit offer. |
| Enterprise | Sales pricing | Available for high-volume usage. |

*Reported operation rates: Retain $15.00/M tokens, Recall $0.75/M, Reflect $3.00/M, Iris Extract $7.50/M, Mental Model Retrieve $0.25/M, and Mental Model Refresh $3.00/M. Free signup credits were reported at about $5, and the test used free credits.*

## Is It Right For You?

**Use it if**
- You need a memory layer that remembers user preferences, client history, and project direction across sessions.
- You want support replies that skip repeated basics and move to the next useful step.
- You need strong scope isolation between users, clients, or projects.
- You want a UI or graph surface that makes stored memories and retrieval visible for debugging.

**Skip it if**
- You need fully proven delete or forget semantics where old memories disappear from visible context.
- You need repeat-run validation of update or forget corrections before trusting the memory in production.
- You only want hidden chat memory with no inspection or graph surface.

## Classification

- **Category:** developer-tools
- **Subcategory:** agent-platforms
- **Type:** text

## Frequently Asked Questions

**Q: Does Hindsight remember user preferences across sessions?**

Yes. In the founder_001 flow, it stored a short, direct, copy-paste-ready style preference, a non-motivational tone, a proof/artifact expectation, and a safest-next-step preference, then reused that memory in a later internal update.

**Q: Does Hindsight avoid repeating basic support troubleshooting?**

Yes for the ACME support flow. After the customer had already tried password reset, clearing cache, and switching browsers, Hindsight moved the reply toward IdP, SAML/OIDC, and configuration checks instead of repeating the basics.

**Q: Does Hindsight keep different clients and projects separate?**

Yes. ACME did not bleed into BetaCorp, and the unrelated sales-email project stayed separate from the AI Demos memory-for-agents project.

**Q: Can Hindsight update or forget old memories?**

Partially. Newer instructions influenced later replies, but the older ACME SSO context and the formal-tone preference were still visible in the memory panel after the update and forget requests.

**Q: What does Hindsight show in its memory UI?**

Hindsight's own native dashboard (ui.hindsight.vectorize.io) shows Experience and Observations graph views with node counts, link counts, and link-type breakdowns. During chat testing, a 'memory panel' also appeared in this report's custom test interface, showing which memories were used in each reply — that panel is part of the custom harness, not Hindsight's own product screen.

**Q: What does Hindsight pricing look like?**

The report describes a credit model: 1 credit equals $1 USD, free signup credits of about $5, reported credit packs of $10, $25, $50, and $100, and enterprise pricing via sales.

**Q: Was a custom interface used to test Hindsight?**

Yes. Test prompts were sent through a custom-built chat interface for this benchmark — Hindsight's own native dashboard (graphs, Recall Analyzer, memory browsing by type) was used separately to verify stored memory and capture the graph screenshots in this report.

## Similar Tools

AI tools similar to Hindsight:

- [Zep](https://aidemos.com/tools/zep) — Developer-first memory for AI agents that captures workflow context well, but still needs stronger stale-memory and forget control.
- [Mem0](https://aidemos.com/tools/mem0) — Mem0 remembers useful agent context across sessions and makes retrieved memory visible, but stale context can linger after updates or forget requests.
- [Supermemory](https://aidemos.com/tools/supermemory) — Hosted agent memory with strong capture and scoping, but mixed retrieval and weak forget behavior.
- [Cognee](https://aidemos.com/tools/cognee) — Inspectable graph-backed memory for AI agents, with strong provenance tracing but cautious update/delete behavior.