A slash command can now be refused by a policy attached to it, with the reason shown.
What's wrong with this entry?
Before running a slash command, Claude Code now consults a policy value attached to the command entry and can refuse it, showing the reason. Commands with no such policy value attached still run as before.
- The policy value is supplied by the server on each command entry; absent one, the command is allowed.
- Refusals emit telemetry that separates a stale command list from an active denial.
tengu_input_slash_invalid
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