hindsight-zed
Long-term memory for the Zed editor's AI assistant, powered by Hindsight.
hindsight-zed init wires 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 (no lag), and from your seat it's automatic.
How it works
Zed has no pre-prompt hook, but it does support two things this integration uses:
- MCP context servers — Zed runs MCP servers configured under
context_serversinsettings.jsonand exposes their tools in the Agent Panel. We register the Hindsight MCP server there, giving the agentrecall/retain/reflecttools. - A global instructions file (
~/.config/zed/AGENTS.md) that Zed includes in every conversation. We add 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) — that means you need Node.js installed.
Install
pip install 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.jsoncontains comments (JSONC),initwon't rewrite it — it prints the exactcontext_serversentry for you to paste instead. Usehindsight-zed init --print-onlyany time to see the snippet without writing.
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 |
hindsight-zed init --print-only |
Print the config to add manually |
What gets written
~/.config/zed/settings.json:
{
"context_servers": {
"hindsight": {
"source": "custom",
"command": "npx",
"args": [
"-y", "mcp-remote",
"https://api.hindsight.vectorize.io/mcp/my-memory/",
"--header", "Authorization: Bearer YOUR_HINDSIGHT_API_KEY"
]
}
}
}
~/.config/zed/AGENTS.md (inside a fenced <!-- HINDSIGHT --> block that leaves
the rest of the file untouched): a short rule telling the agent to recall at
the start of each task and retain durable facts.
Configuration
| Setting | Env var | Default |
|---|---|---|
| API URL | HINDSIGHT_API_URL |
https://api.hindsight.vectorize.io |
| API token | HINDSIGHT_API_TOKEN |
(none; required for Cloud) |
| Bank id | HINDSIGHT_ZED_BANK_ID |
zed |
These can also live in ~/.hindsight/zed.json (written by init).
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 MCP-endpoint check
License
MIT
Metadata
Release files for hindsight-zed 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_zed-0.1.0.tar.gz | 20.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hindsight_zed-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 31.0 kB
Release files / hindsight_zed-0.1.0.tar.gz
| Download URL | hindsight_zed-0.1.0.tar.gz |
|---|---|
| Size | 20.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bdf1a6ce6cf59b1c6048670eac41978c784d1ccabc26ad041346589b6b782dc2
|
|
BLAKE2b-256 checksum How to use checksums |
477a1bc87e8c6440ddd0b32a0e084ecaa684bec34b60284bee702aa8cbdd51e9
|
| 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 17, 2026.
Transparency logRelease files / hindsight_zed-0.1.0-py3-none-any.whl
| Download URL | hindsight_zed-0.1.0-py3-none-any.whl |
|---|---|
| Size | 10.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
883c4b400b36c067f0f72e59cd914990f6d8be3a058637e511cb44cac0bb37ab
|
|
BLAKE2b-256 checksum How to use checksums |
38480d74ff946d0102a378d6f59b5567010bf496b7b5abcebd290c2102bc943d
|
| 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 17, 2026.
Transparency log