note.md + Codex

Why this pairing works

Codex reads AGENTS.md from the directory it runs in — that's its native convention, no configuration. A note.md vault publishes its file rules (sidecar pairing, outline format, date links, block citations) in exactly that file. So the integration is: cd vault && codex. Done.

Codex is strongest as a working agent: ask it to draft, refactor documents, batch-process notes, or build the small scripts your vault accumulates (importers, link checkers, report generators). Everything it writes is markdown in the vault, which means everything it writes flows into your reading-annotation loop.

Setup

1. Copy the conventions summary from llms-full.txt into AGENTS.md at your vault root.
2. Add vault-specific rules — e.g. "never modify *.note.md", "new research goes under research/ with a date prefix".
3. Run codex in the vault directory. It picks up the rules automatically.
4. Review its output in note.md; annotate; tell the next run to read the sidecars.

FAQ

Does Codex need an MCP server to use the vault?

No. The vault is plain files in the working directory — Codex's home turf. An MCP endpoint exists for the share worker (publishing pages), not for basic vault work.

What should I forbid in AGENTS.md?

The one hard rule: agents don't write into your .note.md sidecar files — those hold human judgment. Everything else (naming, folders, link style) is house preference.