Core concepts
Sessions and context
What belongs to the project, what belongs to a conversation and what the model sees.
Projects and conversations
A project is your firmware folder, with its target, components and settings. A conversation is one task with its own history. Start a new conversation for each independent task.
What the agent sees
For each request, Flash combines the conversation, FLASH.md, the relevant source and your hardware information. Point it at what matters with @.
Explain @src/main.c and the board initialisation sequence.Long conversations
As a conversation grows, Flash compacts what the model sees and keeps your request, decisions and evidence. Run /compact to do it yourself, or /clear to start again. Compaction is not project memory.
Interrupt and steer
Press Esc to stop a running turn and correct the direction; the conversation stays. One task per conversation gives the most reliable results.
Resume a conversation
Conversations are saved on your computer, with no cloud sync. Reopening one never repeats its hardware operations.
flash sessions listflash resumeflash resume <session-id>