Use Hindsight to recall past context, save reusable facts, and reason across accumulated memories. Supports continuity between conversations by preserving preferences, project decisions, and lessons learned, while helping explain the reasoning behind earlier choices.
Long-term memory for the agent via Hindsight. Use to recall relevant past context before answering, retain durable facts as you learn them, and reflect over accumulated memory for the "why" behind a decision. Load whenever continuity across sessions matters — the user refers to earlier work, states a lasting preference, or asks a question that prior context could answer.
Review the instructions the agent will receive before you install.
This plugin connects the agent to Hindsight, a long-term memory engine. Memory
persists across sessions in a bank (scoped by HINDSIGHT_BANK_ID), so what you
retain now is available to recall in future conversations.
The hindsight MCP server exposes the tools below. Prefer these over guessing from
scratch when the answer might live in past context.
Call recall at the start of a task, or whenever the user:
recall(query: "how do we deploy the API and which region")
recall runs semantic + keyword + graph + temporal retrieval and returns the most
relevant memories. Ground your answer in what comes back, and say when nothing
relevant was found rather than inventing continuity.
Call retain when you learn something durable and reusable — worth having in
a future session, not just this one:
main only"),retain(content: "The user deploys the API to us-east-1 via GitHub Actions on push to main.")
Do not retain transient chatter, secrets, or anything the user asked you to keep out of memory. Retain the fact, not the whole transcript.
Call reflect when a single recall is too shallow and you need synthesized
reasoning over everything remembered — the why behind a behavior, or a judgment that
weighs many facts together:
reflect(query: "What has repeatedly caused our CI to flake, and what should we standardize?")
reflect is slower and disposition-aware; use it deliberately, not for lookups.
All tools operate on the bank selected by the connection (HINDSIGHT_BANK_ID, default
default). One bank = one memory store — keep a project's or a user's memory in its
own bank so context stays isolated and relevant. You never pass a bank id to a tool;
it is implicit from the endpoint.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Record task handoffs between Bots in shared Hindsight memory, including progress, remaining work, sources, and caveats. Other Bots can retrieve the record later, continue unfinished work, and report the outcome back through shared memory.
Review changed code against project rules and report missing tests, unused code, typing problems, and style violations. It also checks API design and data isolation, helping developers identify issues after implementation.
Create a specialized Claude Code subagent with Hindsight long-term memory. Start with an empty agent or import prepared documents, then equip it with knowledge pages and memory search to reuse information across sessions.
Create an animated diagram showing request flows, background jobs, or feature changes. The result is a single SVG image for README files, pull requests, issues, or blog posts, with support for light and dark themes.
Plan how an AI application should use Hindsight memory. Identify useful information to retain, define user-scoping tags and memory bank settings, and specify how retrieved facts and synthesized knowledge should reach the model.
Store project conventions, task outcomes, and troubleshooting lessons in a shared Hindsight Cloud memory bank. Retrieve relevant context before new work, or synthesize past experience to guide decisions and help teammates reuse what has been learned.