Context docs
Each feature on the WorkMap keeps a running context doc, written from the work that has already run on it. Attach it to a prompt and the agent starts with what earlier prompts settled.
What a context doc is
A context doc is a short Markdown file that the app puts together when you attach it. You never have to keep it up to date yourself. It has two parts.
- A header taken from the WorkMap as it is now, with the feature name, the project, the description and the requirements with their statuses.
- A Notes section of dated lines, one per run, recording the decisions that came out of the work. A feature keeps its latest 200 notes.
A context doc comes in three sizes.
| Size | What it covers |
|---|---|
| Feature | One card and its notes. |
| Path | A whole column, with each feature and its notes. |
| Project | The whole map, one line per path and feature, with the notes under them. |
Nothing is filled in from the project's history when a map is generated. A new doc reads (no work recorded yet) and grows from the work that runs after that.
How it fills
When a run finishes cleanly, the fallback model reads your request and the run's final answer in the background. It writes one sentence naming a decision worth keeping, or nothing when there is none. That sentence is added as a dated note on the feature the terminal was bound to. Work that is not bound to a feature is kept as notes on the project instead of being dropped.
None of this is added to your prompt, and the terminal never waits for it. A feature's doc starts the moment work is bound to it. That happens when a run starts on a bound feature, when a first prompt gets placed on the map, or when you open a terminal on a path.
Attaching one
Context docs are attached like any other file. They are named after the feature and end in .context.md, and the attachment dock marks them CTX.
- Right-click a card or a path in the WorkMap and choose Add to request on terminal. The doc drops into the project's terminal, ready to go with the next prompt.
- Copy context on the same menu copies a reference instead. Paste it into any terminal, or into the orchestrator's input box, and the doc is attached rather than pasted as text.
- Right-click the project box at the top of the map for the same two choices for the whole project.
- Open terminal on this path attaches the feature's doc by itself. A feature with no notes yet starts building its doc from that terminal's work.
A copied reference works in any open project, so you can attach one project's context to another project's prompt. The file name then starts with the project it came from, as in Project 1: Feature 1.context.md.
The Attachments tab of the node panel lists every doc that went with a prompt, marked FEATURE CONTEXT or PROJECT CONTEXT, so you can see the exact version a run was given. See Nodes and requirements.
Where they are kept
Notes are kept in the app's own encrypted store, not in your project folder, and nothing on disk ties a project's name or folder to its notes. The store works with no network and no account. Writing notes, attaching a doc and pasting a reference into another project all work offline.