{"version":"2.1.280","anchor":"default-filename-generator-for-conversation-export","canonical_anchor":"default-filename-generator-for-conversation-export","heading":"Conversation and debug-report exports get a default filename","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/default-filename-generator-for-conversation-export","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Conversation and debug-report exports get a default filename\n\nExporting a conversation or a debug report now generates a sensible default filename automatically\n\n**Unclear.** Two slightly different filename formats appear in the evidence (slug-based vs. title-based), so the exact naming scheme isn't fully settled.\n\n**What**\n\n- A new default-filename generator builds a name for exported conversation text: `<timestamp>-<slug>.txt` when a slug can be derived from a user message, otherwise `conversation-<timestamp>.txt`. It's used by an export\/save function that returns both the text and this `default_filename`.\n\n- 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`.\n\n**Why**\n\nThis 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.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}