OpenParable
Skip to content
← Back to skills

Hindsight Recall

Research
hindsight-recall

Hindsight Recall is an Agent Skill for research published in the vectorize-io/hindsight repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Search long-term memory for relevant context from past coding sessions using Hindsight MCP tools

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/vectorize-io/hindsight/blob/HEAD/hindsight-integrations/cursor/skills/hindsight-recall/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/hindsight-recall, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Hindsight Recall

Trigger

Use when the user explicitly asks about past decisions, project context, preferences, or anything that may have been discussed in prior sessions.

Workflow

  1. Identify the key topic or question from the user's request.
  2. Check if <hindsight_memories> in the current context already contains relevant results from the automatic session-start recall.
  3. If session memory already covered it, use those memories directly.
  4. If the user needs more specific or deeper recall, use the Hindsight MCP recall tool to search for additional memories.
  5. If you want to reason over accumulated memories for architectural decisions, use the reflect tool.

Guardrails

  • Only use MCP tools for deeper recall when the session-start memory was insufficient.
  • When memories conflict with current context, prefer current context and note the discrepancy.
  • Do not expose raw memory metadata to the user unless asked.

Output

  • Relevant memories integrated into the response
  • If MCP tools are not available, advise the user to check their .cursor/mcp.json configuration