Nicolò Boschi
6f2799569f
* docs: link every integration changelog from its doc page The release script has written a changelog page per integration since 0.4.20 (src/pages/changelog/integrations/<slug>.md), but nothing reliably linked them: 16 of 61 doc pages carried a "View Changelog" link, and the only index was a hand-written table at the bottom of /changelog listing 6 of the 48 pages, stale since the release that introduced them. coding-agents was one of the 31 pages with a changelog nobody could reach except by guessing the URL. Adds the link to the 30 pages missing one, plus a third invariant in check-integrations.mjs so the next one can't ship unlinked: every changelog page whose integration has a gallery entry must be linked from its doc page. coding-agents.md is generated, so its link goes in the README as an absolute hindsight.vectorize.io URL — the sync script rewrites our own absolute URLs to site-relative, so it resolves on npm, GitHub and the docs site. It sits outside the skill:begin regions, so SKILL.md is unchanged. Claude-Session: https://claude.ai/code/session_01DNWFQn8AUN6SApcswHG3aN * docs(integrations): compact grouped gallery with Docs/Changelog buttons The Integrations Hub listed 60 three-line cards with a repeated "Hindsight Team" byline and an OFFICIAL badge on 52 of them, running 6092px tall — scanning it meant scrolling past what you came for. Cards are now a compact row (icon, name, two-line description) grouped by category, with the featured three using the same row tinted rather than a second card design: 4352px, and the shape of the catalogue is visible at a glance. Each card carries Docs and Changelog buttons. Which integrations have a changelog comes from a new build-time plugin that indexes src/pages/changelog/integrations/*.md and joins integrations.json on the link slug (vercel-ai-sdk -> /sdks/integrations/ai-sdk -> ai-sdk.md), so an integration grows the button on its first release with nothing to update by hand. The card is a <div> now — nested anchors are invalid — so the name and the pills are the links, not the whole card. /changelog's first line points here instead of carrying its own listing. Also drops the 14 CSS classes the old card owned, and shares CATEGORY_LABELS / groupByCategory from src/lib/integrations.ts so the taxonomy has one definition. Claude-Session: https://claude.ai/code/session_01DNWFQn8AUN6SApcswHG3aN
2.7 KiB
sidebar_position, title, description
| sidebar_position | title | description |
|---|---|---|
| 36 | Continue.dev Persistent Memory with Hindsight | Integration | Add long-term memory to the Continue.dev coding assistant with Hindsight. Recall project memory into chat with @hindsight, plus optional automatic recall/retain via the Hindsight MCP server. |
Continue
Long-term memory for the Continue.dev coding assistant, powered by Hindsight. Recall relevant project memory directly into chat, and optionally let the agent recall and retain automatically in agent mode.
How It Works
Continue has no hook that runs before a message is sent, but it supports two native extension points that hindsight-continue uses:
- HTTP context provider (precise recall): type
@hindsight <query>(or a bare@hindsight) in Continue chat and relevant memory is recalled and injected into the model's context at query time. The package ships a small adapter server that implements Continue's HTTP context-provider contract ({query, fullInput, options, workspacePath}→ context items) on top of Hindsight recall. - MCP server + rules (automatic): point Continue's agent mode at the Hindsight MCP server for
retain/recall/reflecttools, with a rules file that instructs the agent to recall at the start of every task and retain durable facts.
Memory is scoped per bank — use one bank per project so context from one codebase doesn't leak into another.
Setup
pip install hindsight-continue
Run the adapter, pointing it at your Hindsight instance and bank:
export HINDSIGHT_API_KEY=hsk_...
export HINDSIGHT_CONTINUE_BANK_ID=my-project
hindsight-continue # serves on 127.0.0.1:8123
Then register it in Continue's config.yaml:
context:
- provider: http
params:
url: "http://127.0.0.1:8123/"
title: hindsight
displayTitle: Hindsight
description: Recall long-term memory from Hindsight
Use a Hindsight Cloud key, or point at a self-hosted server with HINDSIGHT_API_URL=http://localhost:8888.
Automatic recall (optional)
For hands-off recall and retain in agent mode, wire the Hindsight MCP server into Continue and add a "recall first" rule. See the examples/.continue/ assets in the integration directory.
Limitation
Continue has no pre-prompt hook, so memory cannot be injected fully passively on every message. The @hindsight provider gives precise, query-time recall on demand; the MCP + rules setup gives automatic recall in agent mode, subject to the agent following the rule.