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
3.2 KiB
sidebar_position, title, description
| sidebar_position | title | description |
|---|---|---|
| 7 | Zed Persistent Memory with Hindsight | Integration | Add long-term memory to the Zed editor's AI assistant with Hindsight via MCP. One command wires up the Hindsight MCP server plus a recall/retain rule, so memory works automatically in the Agent Panel. |
Zed
Long-term memory for the Zed editor's AI assistant, powered by Hindsight. One command connects Zed's Agent Panel to the Hindsight MCP server and adds a rule telling the agent to use it — so it recalls relevant memory at the start of a task and retains durable facts as it goes. Recall happens at query time against your actual message, and from your seat it's automatic.
How It Works
Zed has no pre-prompt hook, but it supports two things this integration uses:
- MCP context servers: Zed runs MCP servers configured under
context_serversinsettings.jsonand surfaces their tools in the Agent Panel.hindsight-zedregisters the Hindsight MCP server there, giving the agentrecall/retain/reflecttools. - A global instructions file (
~/.config/zed/AGENTS.md) that Zed includes in every conversation. The integration adds a small rule there telling the agent to recall first and retain what it learns.
Zed doesn't yet have native HTTP-MCP transport, so the server is connected through the mcp-remote stdio bridge (run via npx), which means Node.js must be installed.
Setup
hindsight-zed is a zero-dependency Node CLI — Node.js is the only requirement (already needed for the mcp-remote bridge). Run it straight from npm with npx:
npx @vectorize-io/hindsight-zed init --api-token YOUR_HINDSIGHT_API_KEY --bank-id my-memory
Or install it globally for a persistent command:
npm install -g @vectorize-io/hindsight-zed
hindsight-zed init --api-token YOUR_HINDSIGHT_API_KEY --bank-id my-memory
init adds the hindsight MCP server to ~/.config/zed/settings.json and the recall/retain rule to ~/.config/zed/AGENTS.md. Restart Zed, open the Agent Panel, and the hindsight server should show a green dot.
Use a Hindsight Cloud key, or point at a self-hosted server with --api-url http://localhost:8888 (no token needed for an open local server). If your settings.json has comments (JSONC), init prints the entry to paste rather than rewriting the file — or run hindsight-zed init --print-only anytime.
Commands
| Command | Description |
|---|---|
hindsight-zed init |
Add the MCP server + recall/retain rule |
hindsight-zed status |
Show whether the server + rule are configured |
hindsight-zed uninstall |
Remove the server + rule |
Note
Recall and retain run through MCP tools the agent calls, guided by the always-on rule. This makes recall query-time precise (no lag), with the tradeoff that it relies on the agent following the "recall first" instruction rather than the editor enforcing it.
See the package README for full configuration options.