Skip to main content

hindsight-copilot

Long-term memory for GitHub Copilot in VS Code, powered by Hindsight.

hindsight-copilot init wires the Hindsight MCP server into VS Code's .vscode/mcp.json and adds a recall/retain rule to .github/copilot-instructions.md. Copilot's agent mode then has recall / retain / reflect tools and — guided by the rule — recalls relevant memory at the start of a task and retains durable facts as it works.

How it works

VS Code Copilot supports two things this integration uses:

  • MCP servers in .vscode/mcp.json (agent mode), including HTTP servers with headers — so the Hindsight MCP endpoint connects directly:

    {
      "servers": {
        "hindsight": {
          "type": "http",
          "url": "https://api.hindsight.vectorize.io/mcp/my-project/",
          "headers": { "Authorization": "Bearer hsk_..." }
        }
      }
    }
    
  • .github/copilot-instructions.md, which Copilot applies to every chat in the workspace — that's where the recall/retain rule lives.

Install

pip install hindsight-copilot
cd your-project
hindsight-copilot init --api-token YOUR_HINDSIGHT_API_KEY --bank-id my-project

init merges the servers entry into ./.vscode/mcp.json and writes the rule into ./.github/copilot-instructions.md. Reload VS Code, open Copilot Chat in agent mode, and start the hindsight MCP server from the chat's tools menu.

Use a Hindsight Cloud key, or a self-hosted server with --api-url http://localhost:8888 (no token needed for an open local server). If mcp.json has comments, init prints the snippet to paste instead of touching the file — or run hindsight-copilot init --print-only anytime.

Commands

Command Description
hindsight-copilot init Add the MCP server + recall/retain rule
hindsight-copilot status Show whether the server + rule are configured
hindsight-copilot uninstall Remove the server + rule

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_COPILOT_BANK_ID copilot

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-copilot 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for hindsight-copilot 0.1.0
File Size Uploaded
hindsight_copilot-0.1.0.tar.gz 19.7 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for hindsight-copilot 0.1.0
File Interpreter ABI Platform
hindsight_copilot-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 29.5 kB

Release files / hindsight_copilot-0.1.0.tar.gz

Download URL hindsight_copilot-0.1.0.tar.gz
Size 19.7 kB
Tags Source
SHA-256 checksum
How to use checksums
f3708c1193390e3753eacd96378d0bc2ddda71b522b79c2975b463609a125bed
BLAKE2b-256 checksum
How to use checksums
04bec2606a4feb4aed485da52be1070ce47b4fb46551718756e519bedf69f326
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Aug 11, 2026.

Transparency log

Release files / hindsight_copilot-0.1.0-py3-none-any.whl

Download URL hindsight_copilot-0.1.0-py3-none-any.whl
Size 9.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a66aa22086da1a931c826cba5fed409c969e9602bdcec9bd56d2efd1aa199898
BLAKE2b-256 checksum
How to use checksums
921401f69d5571b20b822c4bbbf6c4b8ea7215542b4acdf5f40de88620ca5139
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Aug 11, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page