Mindex

Folder context

One context file per folder, rewritten in the background as the folder changes.

Assistant CLIs read a context file from the directory they are working in. Claude Code reads CLAUDE.md, Codex reads AGENTS.md, Gemini CLI reads GEMINI.md. Keeping those current by hand is work nobody does for long.

Mindex maintains them for you. A background job watches the vault, notices when a folder's notes have moved on from its context file, and rewrites the file to describe what is in there now.

Why it exists

An assistant that opens your folder cold has to read everything to learn what it is looking at. A folder that describes itself — what lives here, what the conventions are, what matters — means the assistant starts from the current picture instead of reconstructing it every time.

The filename follows the assistant

Assistant File
Claude Code CLAUDE.md
Codex AGENTS.md
Gemini CLI GEMINI.md

Switching assistants in Settings → General → AI renames the existing files, so the context you have accumulated is not orphaned under a name the new CLI never looks at.

Status

A folder's context is one of three things:

  • Current — the file describes the folder as it is.
  • Behind — notes are newer than the context file.
  • Missing — the folder has no context file yet.

Folders that are behind or missing are surfaced so you can regenerate them.

The template

The generated file follows a template you can change, kept at .mindex/templates/context-template.md. It is yours, not the CLI's — no assistant reads it directly, so its name does not change when you switch assistants.

It is an ordinary file

The context file sits in the folder as plain Markdown. Edit it by hand if you want; it is committed to Git like everything else.