Unclear Two slightly different filename formats appear in the evidence (slug-based vs. title-based), so the exact naming scheme isn't fully settled.
What
- A new default-filename generator builds a name for exported conversation text:
<timestamp>-<slug>.txtwhen a slug can be derived from a user message, otherwiseconversation-<timestamp>.txt. It's used by an export/save function that returns both the text and thisdefault_filename. - A new debug/feedback report builder assembles a three-section report ('Session', 'Environment', 'Internal') from account status, the main-loop model, MCP state, and permission mode, leaving out any empty sections. A companion function produces a text export of this report using the same default-filename approach and a transcript-export helper with
welcomeHeader: false.
Why
This means exporting a conversation or a debug report no longer requires typing a filename by hand, and the generated name is still meaningful (based on timestamp and content) rather than generic.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
Two slightly different filename formats appear in the evidence (slug-based vs. title-based), so the exact naming scheme isn't fully settled.