You'll notice
Useful4 Signal2
Slash-command arguments are now redacted for tokens and keys before appearing in the transcript.
What's wrong with this entry?
Anonymous. No account, no email.
What
Arguments echoed back as /command args now go through the same secret redaction used elsewhere, covering Bearer tokens, Basic auth, sk-ant- keys and Slack webhook URLs, including the "Args from unknown skill" warning. An unknown command whose arguments change under redaction is now treated as sensitive.
Details
- Plugin names, granted-scope display names, added workspace directory paths and the IDE name in "Opened changes in …" now pass through a display sanitizer
- That sanitizer blanks any string with zero visible width, so invisible characters cannot be used to fake a name
Evidence
Bearer <token>
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
A crashing slash command now tells you it crashed
Both mention slash command
-
v2.1.234
A command can decide from its arguments whether it counts as sensitive
Both mention slash command
-
v2.1.234
A slash-command grouping for a command that does not exist
Both mention slash command