Memory
Seeing what it knows
Open the panel that shows exactly what the current turn is working from.
CtrlK opens the context panel. /context does the same, and /context <query> opens it filtered.
What's in it
Three tabs, moved between with Tab or the arrow keys:
- Session — this conversation: what's been discussed, what's been edited, what's still open.
- Project — the repository: scope, index state, structure.
- Knowledge — the memory in play: decisions, lessons, and past sessions the current turn is drawing on.
↑/↓ move within a tab. Enter pushes the highlighted entry into the chat as a reference card, so you can point at it and say "this one is wrong" or "follow this".
Why look
When an answer surprises you, the panel usually explains it: a decision from March you'd forgotten, a lesson doing more work than you expected, or an empty Knowledge tab that tells you it's working from the code alone.
It's the difference between "why did it do that" and knowing.
Correcting from the panel
Push an entry into chat and say what's wrong with it. Corrections made this way supersede the original — the history stays, the current answer changes.
If it doesn't work
The Knowledge tab is empty. Nothing in memory matched this turn. Normal on a new project or a mechanical change.
It's showing something irrelevant. Push it into chat and say so. That feedback affects what surfaces next time.
CtrlK does nothing. Some terminal multiplexers capture it. /context
is the same panel.