Kimi Code

MemIndex records work from Kimi Code. It brings past notes into the first prompt of a session. You can also ask Kimi to search your memory.

Install Kimi Code and complete its own setup first. Then run:

npx memindex@latest install --ide kimi

Choose how MemIndex should write notes when the installer asks. See Install for the shared requirements and choices.

The installer adds MemIndex rules to ~/.kimi-code/config.toml. It adds the memory search connection to ~/.kimi-code/mcp.json. It keeps other settings. If you use KIMI_CODE_HOME, it writes there instead. It keeps a dated backup of an existing config.toml, creating at most one backup per day.

An existing mcp-search entry in mcp.json is left alone. Check that it connects to MemIndex if search is unavailable after setup.

Start a new Kimi session after installation. MemIndex records prompts, tool calls, and failed tool calls. It can add notes about a file before Kimi reads it. At the end of a turn, it requests a summary.

Past notes arrive through the first prompt. After Kimi shortens a long conversation, MemIndex can bring in fresh notes again. Your own MEMORY.md stays under your control.

Ask Kimi something specific, such as “What did we decide about the sign-in flow?” Check the MemIndex viewer after a small task to confirm that new notes appear.

To inspect or remove the connection:

npx memindex kimi status
npx memindex kimi uninstall

Status checks the installed hook block. It does not prove that work has been recorded. If notes do not appear, use Troubleshooting.