{"version":"2.1.288","anchor":"precomputed-compact-telemetry-and-the-control-message-admit","canonical_anchor":"precomputed-compact-telemetry-and-the-control-message-admit","heading":"Reworded messages when a shell command cannot be checked, plus smaller internal changes","tier":"notice","area":"Bash Tool","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/precomputed-compact-telemetry-and-the-control-message-admit","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Reworded messages when a shell command cannot be checked, plus smaller internal changes\n\nMessages about shell commands that cannot be checked before running were reworded, alongside several small internal changes\n\n**Unclear.** It is not clear what the device channel setting or the other internal changes control.\n\n**What**\n\nA mix of small changes:\n\n- Messages saying a shell command cannot be checked before it runs were reworded, for example \"The program xargs gives ... can't be checked before it runs\".\n\n- The reason recorded for one such case is now an unsupported shell rather than an unsupported interpreter.\n\n- The device channel, a connection Claude Code uses to exchange messages, gained a setting for admitting messages from people on a project.\n\n- Two usage events were added, and some existing usage data is now gathered differently.\n\n**Why**\n\nThese are mostly internal. The part you might notice is the wording of messages about shell commands Claude Code cannot check before running.\n\n- Area: Bash Tool\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}