Pi Hindsight Extension

Persistent memory for Pi backed by Hindsight.

Documentation: https://luxus.github.io/pi-hindsight/

Pi Hindsight recalls relevant project memory before model calls, retains structured session deltas after completed agent runs, and exposes explicit memory tools for direct retain/recall/reflect operations.

The extension is inspired by noctuid/pi-hindsight. This version keeps the same useful idea, then tightens project isolation, queue durability, diagnostics, and release hardening.

Install

Install from GitHub:

pi install https://github.com/luxus/pi-hindsight

For local development, install a checkout path instead:

pi install /path/to/pi-hindsight

Package name: @luxusai/pi-hindsight.

Quick start

1. Start or choose a Hindsight server:
   • Hindsight Cloud signup
   • Self-hosted Hindsight installation; use Hindsight's built-in llama.cpp/local-LLM option when you want a no-LLM-API-key private setup
2. Open Pi in your repo and run /hindsight.
3. Configure the Hindsight API URL. The default self-hosted URL is http://localhost:8888.
4. Choose the narrowest memory profile that fits the repo: Project + User, Project Only, User Only, or Recall Only.
5. Start coding. Recall happens before provider calls; retain happens after completed agent runs when the selected profile allows automatic retain.

See the getting started guide for setup details.

Safety defaults

• Project memory stays in a project bank by default.
• Global/user memory is opt-in and explicitly configured.
• Recall injection is ephemeral; recalled memory is not written back into transcripts.
• Automatic retain redacts common secrets before writing memory.
• Exact document deletion requires exact bank ID, exact document ID, and confirm: true.

See memory behavior and session memory modes for details.

Documentation

• Start — install and first setup
• Concepts — memory model, banks, queue, imports, safety
• Guides — task workflows for setup, diagnostics, imports, and recovery
• Reference — tools, commands, config, hooks, generated surface
• Development — contributor setup, checks, release, docs workflow

Development

npm install
npm run check

npm run check includes npm run docs:check, which verifies generated surface-reference freshness, generated code-map freshness, internal docs links/sidebar routes, packaged Markdown links, GitHub Pages base-prefixed docs links, and docs-site build.

Run Pi with the local extension:

pi -e ./extensions/index.ts

For maintainer details, see Development setup and Release process.