{"version":"2.1.287","anchor":"tool-copy-and-error-wording-changes","canonical_anchor":"tool-copy-and-error-wording-changes","heading":"Clearer wording in several messages Claude reads about tools and errors","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/tool-copy-and-error-wording-changes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Clearer wording in several messages Claude reads about tools and errors\n\nSeveral messages Claude Code sends to the model about blocked tools, artifact copying and permissions have been reworded\n\n**Unclear.** It is not clear whether copying SVG content from another artifact is now allowed, or whether SVG is only no longer named in the message.\n\n**What**\n\nClaude Code has reworded several messages it sends to the model, the AI that does the work in a session. These are not messages you normally see. They are what Claude is told when something it tried cannot go ahead.\n\n- The message for when a computer cannot be reached no longer talks about \"what this container can do\". It now tells Claude to do the rest of the task without it and tell you what is blocked.\n\n- The refusal for copying from another artifact (a document Claude has produced) now names an HTML or XML document. It no longer lists SVG.\n\n- The refusal for an `awk` command that cannot be checked in advance is now written in plain language.\n\n- The reply sent when a permission request no longer exists, and the text for a failed launcher permission, now come from shared wording used elsewhere in Claude Code.\n\n**Why**\n\nThese messages shape what Claude does next. Clearer wording makes it more likely that Claude carries on with what it can do and tells you plainly what it could not.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}