{"version":"2.1.314","anchor":"compaction-and-too-long-error-strings-split","canonical_anchor":"compaction-and-too-long-error-strings-split","heading":"Compaction errors now say whether the conversation or attached media is too large","tier":"notice","area":"Compaction","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/compaction-and-too-long-error-strings-split","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Compaction errors now say whether the conversation or attached media is too large\n\nFailed compaction now shows 'Could not compact' with either 'conversation too long' or 'attached media too large', each suggesting `\/clear`\n\n**What**\n\nCompaction summarizes older parts of a conversation to free up room. Its error text used to be a single hint, \"\/clear to start fresh\". It is now split into:\n\n- \"Could not compact\"\n\n- \"conversation too long \u00b7 \/clear to start fresh\"\n\n- \"attached media too large \u00b7 \/clear to start fresh\"\n\n`\/clear` starts a new conversation with empty context.\n\n**Why**\n\nYou can now tell when the problem is attached images or other media being too large rather than the conversation itself being too long.\n\n- Area: Compaction\n- Names: `\/clear`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}