Copilot CLI

Copilot CLI can search notes that MemIndex has already recorded. This connection does not capture Copilot CLI conversations automatically.

Complete Install, then run:

npx memindex@latest install --ide copilot-cli

The installer adds a local memory search connection to ~/.copilot/mcp-config.json (or the folder COPILOT_HOME names), which is where Copilot CLI reads it. It keeps the servers you already have there. If an earlier version put the entry in ~/.github/copilot/mcp.json, the installer removes it from that file. It also writes a memory placeholder to .github/copilot-instructions.md in the current project. That placeholder is not a recording mechanism.

Run the installer from the project where you want that instruction file.

Restart Copilot CLI after installation. Keep the local MemIndex service available.

Ask a specific question about recorded work. For example: “Search MemIndex for our decision about the sign-in flow.” Name the project when you know it. For local memory, the agent starts with search, checks nearby work with timeline, then reads selected notes with get_observations.

To verify the connection, search for something you can already see in the MemIndex viewer. New work in Copilot CLI will not appear just because search is connected. Record that work through another supported agent or save an explicit note through the available memory tools.

If the tools do not appear after restarting, run npx memindex doctor. Check that the configured program and installed MemIndex files exist. See Troubleshooting.