Memory is good at durable facts about you. It is not the right home for "we decided against Postgres on the 14th because of the hosting constraint." That is what Checkpoints are for — a deliberate ledger of the things future work depends on, each linked back to where it came from.
Find them under Flow -> Checkpoints.
Four kinds of checkpoint
- Decision — a choice that has been made, so it is not relitigated every conversation.
- Constraint — a boundary the work has to respect: a budget, a deadline, a platform, a rule.
- Open loop — a question you have not answered yet and must not forget.
- Insight — something you learned that changes how the rest of the work should go.
Saving one
Select Save Flow checkpoint from a conversation, or Add checkpoint on the Checkpoints tab. You give it two things:
- A checkpoint line — what the next conversation must know, in one sentence.
- A source note — the decision, constraint, insight, or open question in full, up to 12,000 characters.
Because a checkpoint carries its source, you can tell later not just what was decided but why — which is the part that usually goes missing.
Working through them
Counters at the top track Active, Open loops, and Decisions. Filter by Active, Resolved, or All, and search across everything you have saved. Resolve an open loop once you have answered it; it stays readable under Resolved rather than disappearing.
What makes a good checkpoint
- Write the reason, not just the conclusion. "Chose X" ages badly; "chose X because Y ruled out Z" does not.
- Save it when the decision is made, while you still remember the alternatives.
- Keep them few. A ledger of two hundred checkpoints is another scrollback.