Hindsight is a memory server for AI agents. Your agents save what they work out to it and search it back later, so they stop re-deriving the same decisions every session. It speaks MCP, so anything with MCP support can talk to it: Claude Code, Cursor, Codex, Pi, Grok CLI, and the rest.

I put a template together for it. It runs the official upstream image, which carries the API, the web dashboard, the search models and its own PostgreSQL, so there is nothing else to stand up alongside it.

Setup guide: https://github.com/PikkonMG/unraid-docker-templates/blob/main/docs/HINDSIGHT.md
Project: https://github.com/vectorize-io/hindsight
Upstream docs: https://hindsight.vectorize.io

Do this before you hit Apply

The container runs as uid 1000 and will not chown its own appdata, so make the folder yourself first. On the Unraid terminal:

mkdir -p /mnt/user/appdata/hindsight
chown -R 1000:1000 /mnt/user/appdata/hindsight
chmod 700 /mnt/user/appdata/hindsight

Skip it and the container comes up, then immediately says /home/hindsight/.pg0 is not writable. Stop it, run those lines, start it again. It does not use the usual PUID and PGID variables.

It needs a model

Hindsight uses a language model of its own to pull facts out of whatever your agents send it. That is separate from whatever model your agents are running on, and it never talks to you directly.

Point it at an Ollama box on your LAN, or paste in a key for OpenAI, Anthropic, Gemini, Groq, OpenRouter, DeepSeek or Ollama Cloud. Going the Ollama route, the model has to support tool calling or the reflect feature will not work. Use your server IP in the endpoint field, not localhost, since localhost inside the container is the container.

Ports and keys

8888 is the API and the MCP endpoint. 9999 is the dashboard.

There are three keys. Memory API key and Web UI backend key have to hold the same value, and that is the one your agents send as a bearer token. Web UI login key is a separate one, and it is what you type to get into the dashboard.

Connecting your agents

Upstream ships an installer that detects the agents you already have and wires them all up. Run it on the machine you code from, not on the server. I have only run this on Linux, so I cannot tell you how it behaves on Windows or Mac.

npx @vectorize-io/hindsight-coding-agents install all \
  --server self-hosted \
  --api-url http://MY-UNRAID-IP:8888 \
  --api-token MY-MEMORY-API-KEY

That covers Claude Code, Codex, Cursor, opencode, Pi and a few more. After it runs, each repo gets its own memory bank automatically, seeded from your commit history.

Anything it does not cover is a plain MCP endpoint. One bank per project, named in the URL:

http://MY-UNRAID-IP:8888/mcp/MYBANK/

with an Authorization: Bearer MYTOKEN header. The guide has the config block for Cursor, Oh My Pi, plain Pi, Grok CLI and Claude Desktop, which is the one awkward case because its connector dialog has nowhere to put a bearer token.

First save on a cold model takes a while, mine was about half a minute on a local one, because Ollama has to load the model before it can do anything. It settles down after that.

Backups

Storage lives at /mnt/user/appdata/hindsight. The database runs inside the container but writes out to there, so it survives restarts, updates and rebuilds. Stop the container before you back that folder up.

---

Post here if something breaks on the Unraid side and I will take a look. Bugs in Hindsight itself are better raised on their tracker: https://github.com/vectorize-io/hindsight/issues

Reserve.