Give your agent your markdown notes
Use casesYou already write the decisions and research your agent needs. The problem is that it has never read any of it.
The situation
A solo builder keeps decisions, research, and project notes in markdown — and their agents start every session blind. With Lyt (Link Your Think™), those notes remain markdown inside a vault, while the agent searches the reachable pod through its installed workflows. A decision the agent captures once — lyt capture underneath — is available to later searches wherever that vault and its index are available.
How you do it
You ask. Before you get into the work itself, have the agent read the vault's primer — a whole-vault aggregation of keywords, active arcs, and recent activity — and report back what it found.
Needs: Lyt initialized.
Using Lyt, brief yourself on my research/notes vault before we start working: read that vault's primer without writing a primer file, and tell me its active arcs, its top keywords, and what changed recently. Then say which of those threads is closest to what I am about to ask about, and name the vault you read it from.
Use your own vault name in place of research/notes. The primer aggregates a whole vault — keywords, active arcs, recent activity — rather than answering one query; --dry-run prints it instead of writing the primer file. Assumes Lyt is installed and initialized on this machine.
lyt primer --scope vault --target research/notes --dry-runWhat changes
The agent works from your decisions, notes, and documentation — not from what it can guess. The notes stay ordinary markdown you can open in any editor; what the agent gains is a way to find them. If you do not have a vault yet, the quickstart creates one, and adopting a folder you already have is the route in for existing notes.