hindsight-roo-code
Persistent long-term memory for Roo Code via Hindsight.
Run the installer once and every Roo Code session automatically recalls past context before tasks and retains learnings after.
What It Does
- Before each task — Roo Code recalls relevant memories from Hindsight and includes them as context
- During a task — agents can store important decisions and discoveries immediately via
retain - After each task — agents summarize and retain what was accomplished for future sessions
Prerequisites
✨ Recommended: Hindsight Cloud — sign up free, get an API key, and skip the self-hosting setup entirely.
Self-hosting alternative — run Hindsight locally:
pip install hindsight-all
export HINDSIGHT_API_LLM_API_KEY=your-openai-key
hindsight-api # starts on http://localhost:8888
Installation
pip install hindsight-roo-code
Then, from your project directory:
hindsight-roo-code install
Or with a custom API URL:
hindsight-roo-code install --api-url https://my-hindsight.example.com
Install globally (applies to all projects):
hindsight-roo-code install --global
This writes two files:
.roo/mcp.json— registers the Hindsight MCP server with Roo Code.roo/rules/hindsight-memory.md— rules injected into every system prompt
How It Works
New task starts
└─ Roo Code rules instruct agent to call recall
└─ Relevant memories injected into context
Agent working…
└─ retain stores decisions/discoveries immediately
Task ends
└─ Roo Code rules instruct agent to call retain with summary
└─ Summary stored for future sessions
Hindsight exposes recall and retain as MCP tools via its built-in /mcp endpoint. The rules file in .roo/rules/ tells Roo Code when to call them.
Configuration
The installer writes to .roo/mcp.json:
{
"mcpServers": {
"hindsight": {
"type": "streamable-http",
"url": "http://localhost:8888/mcp",
"timeout": 30,
"alwaysAllow": ["recall", "retain"]
}
}
}
To change the API URL after installation, edit .roo/mcp.json directly or re-run the installer:
hindsight-roo-code install --api-url https://new-url.example.com
Verifying Setup
- Start Hindsight (
hindsight-apior Hindsight Cloud) - Open Roo Code in your project
- Check Settings → MCP Servers —
hindsightshould show as connected - Start a task — you should see
recallcalled automatically
Development
uv sync
uv run pytest tests/ -v
Metadata
Release files for hindsight-roo-code 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| hindsight_roo_code-0.1.0.tar.gz | 18.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hindsight_roo_code-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 26.2 kB
Release files / hindsight_roo_code-0.1.0.tar.gz
| Download URL | hindsight_roo_code-0.1.0.tar.gz |
|---|---|
| Size | 18.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3a2d5473637e9dc9b43dc9e80552452908257f9d0c0dddb8ed0d1a0830c0f104
|
|
BLAKE2b-256 checksum How to use checksums |
4dd57e156d7e12da857d6728008d929360a6eafddea6b91321f2fe4afaee69e7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 8, 2026.
Transparency logRelease files / hindsight_roo_code-0.1.0-py3-none-any.whl
| Download URL | hindsight_roo_code-0.1.0-py3-none-any.whl |
|---|---|
| Size | 7.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
33fb0cc22b318d8732888df42aea1b2bac33df3244df8b7140f7407c7c423c27
|
|
BLAKE2b-256 checksum How to use checksums |
5b4d5de1db4cf506c517c66918447cca416d5493c5358ffdf3dac6c7c2a34ae3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 8, 2026.
Transparency log