hindsight-continue
Continue.dev integration for Hindsight — persistent long-term memory for your coding assistant.
Continue has no plugin hook that runs before a message is sent, but it does support two native extension points that this integration uses:
- HTTP context provider — type
@hindsight <query>(or a bare@hindsight) in chat and relevant memory is recalled and injected into the model's context at query time. This package ships a tiny adapter server that implements Continue's HTTP context-provider contract on top of Hindsight recall. - MCP server + rules (optional) — wire the Hindsight MCP server into
Continue's agent mode for
retain/recall/reflecttools, with a rules file that tells the agent to recall automatically.
Prerequisites
- A running Hindsight instance (self-hosted via Docker or Hindsight Cloud)
- Continue (VS Code or JetBrains extension)
- Python 3.10+
Installation
pip install hindsight-continue
Quick start (HTTP context provider)
1. Run the adapter, pointing it at your Hindsight instance and bank:
export HINDSIGHT_API_KEY=hsk_... # omit for a local self-hosted server
export HINDSIGHT_API_URL=http://localhost:8888 # defaults to Hindsight Cloud
export HINDSIGHT_CONTINUE_BANK_ID=my-project
hindsight-continue # serves on 127.0.0.1:8123
2. Register it in Continue's config.yaml (~/.continue/config.yaml or a
workspace .continue block):
context:
- provider: http
params:
url: "http://127.0.0.1:8123/"
title: hindsight
displayTitle: Hindsight
description: Recall long-term memory from Hindsight
3. Use it. In Continue chat, type @hindsight (optionally followed by what
you want to recall) and the matching memories are added to the model's context.
The adapter receives Continue's request ({query, fullInput, options, workspacePath}),
recalls from Hindsight, and returns context items shaped {name, description, content} —
exactly what Continue expects.
Per-request bank override
The configured HINDSIGHT_CONTINUE_BANK_ID is the default. A request may target
a different bank by sending options.bankId:
context:
- provider: http
params:
url: "http://127.0.0.1:8123/"
options:
bankId: another-bank
Optional: automatic recall via MCP + rules
For hands-off recall/retain in agent mode, point Continue at the Hindsight
MCP server and add a rule telling the agent to call it. Example assets are in
examples/.continue/:
examples/.continue/mcpServers/hindsight.yaml— the MCP server blockexamples/.continue/rules/hindsight.md— "always recall first" rule
Configuration
| Env var | Description | Default |
|---|---|---|
HINDSIGHT_API_KEY |
Hindsight API key | (none; required for Cloud) |
HINDSIGHT_API_URL |
Hindsight API URL | https://api.hindsight.vectorize.io |
HINDSIGHT_CONTINUE_BANK_ID |
Default memory bank to recall against | (none) |
HINDSIGHT_CONTINUE_HOST |
Adapter bind host | 127.0.0.1 |
HINDSIGHT_CONTINUE_PORT |
Adapter listen port | 8123 |
These can also be set programmatically via configure(...). See hindsight-continue --help
for CLI flags.
Development
uv sync
uv run pytest tests -v -m 'not requires_real_llm' # deterministic suite
uv run pytest tests -v -m requires_real_llm # gated live E2E (needs a Hindsight server)
License
MIT
Metadata
Release files for hindsight-continue 0.1.1
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_continue-0.1.1.tar.gz | 94.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hindsight_continue-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 107.0 kB
Release files / hindsight_continue-0.1.1.tar.gz
| Download URL | hindsight_continue-0.1.1.tar.gz |
|---|---|
| Size | 94.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b15f5b0add5eee215578b569432f55e60d827a5e5228682ce090e70c75b91825
|
|
BLAKE2b-256 checksum How to use checksums |
2e5e309a368b26b85b4e5f28b181477faa62cd073c1a8e835f5376192d7db360
|
| 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 30, 2026.
Transparency logRelease files / hindsight_continue-0.1.1-py3-none-any.whl
| Download URL | hindsight_continue-0.1.1-py3-none-any.whl |
|---|---|
| Size | 12.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a351eb431874887c206160f31b67f49b3cd55e8e9cdb8811b0df6ec2808de718
|
|
BLAKE2b-256 checksum How to use checksums |
d8380bf6c92a4d17b15ab47bc5a6d43a3ff5e9a1c0f4974c7e86ce69c4f22279
|
| 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 30, 2026.
Transparency log