{"version":"2.1.242","anchor":"clearer-wording-for-feedback-failures-permission-denials-and","canonical_anchor":"clearer-wording-for-feedback-failures-permission-denials-and","heading":"Clearer wording for feedback failures, permission denials and upgrades","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/clearer-wording-for-feedback-failures-permission-denials-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Clearer wording for feedback failures, permission denials and upgrades\n\nFeedback and permission messages were rewritten, including a denial explaining don't-ask mode blocked a tool.\n\n**What**\n\nSeveral messages were rewritten into plain sentences, including \"Draft too large. Shorten the details and try once more.\" and \"Couldn't send feedback. The draft is still queued. Try again later.\" A new denial message explains that a tool was blocked because don't-ask mode is on, a line was added about plugins sharing usage, and the Max upgrade link now carries campaign attribution.\n\n**Evidence**\n\n`Draft too large. Shorten the details and try once more.`\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}