Sessions¶
Each conversation is a session, and it persists across restarts. Session focus is the single biggest performance lever in AI-assisted firmware development: accuracy degrades as a conversation accumulates file reads, tool outputs, and aborted attempts.
Manage a session¶
| Action | Command |
|---|---|
| Start fresh, carrying current input | /new or /clear |
| List and resume previous sessions | /sessions, /resume, /continue |
| Summarise history to free context | /compact or /summarize |
| Revert the last user turn | /undo |
| Fork at the current message | /fork |
| Jump to a specific message | /timeline |
| Rename | /rename |
| Copy the full transcript | /copy |
From the CLI, press Ctrl+X then n for a new session, l to list and switch, or c to compact.
Session discipline¶
Course-correct early. Esc interrupts generation but preserves context. The cost of letting Hydron finish down a wrong path is that its flawed reasoning stays in the context window and shapes the next attempt.
Start fresh when stuck. If you have corrected Hydron more than twice on the same point, run /new. A clean session with a sharper prompt beats a long session full of corrections.
One session, one scope. Do not carry a session across unrelated tasks.
Compact when context fills. A summarised session keeps Hydron sharp on long debug work.
Next¶
- Slash commands for the full command list.
- Best practices for the patterns behind these rules.