Skip to main content
Every session starts from zero unless you give it something to start from. 9P.md is that file.

​
Two files

Both are loaded automatically. Create them with:

​
What belongs in it

Standing instructions — the things you’d otherwise retype every session:
9P.md
What works: conventions that aren’t obvious from the code, commands you always want run, and hard rules (“never do X”). What doesn’t: restating what the code already says. That goes stale and 9p will trust it over the source.
Memory is capped at 8,000 characters. Past that it’s truncated — and a bloated 9P.md crowds out the actual conversation. Keep it tight.

​
Keeping it current

A useful line to include:

​
Beyond a single file

For anything larger than standing instructions — decisions, per-feature notes, daily logs — use a vault, which is a folder of linked markdown 9p can navigate rather than load wholesale.

​
Precedence

Global loads first, project second. Where they conflict, the project file wins by appearing later. Both are injected as standing instructions, not as conversation, so they survive /clear.