Under the hood
Useful2 Signal1
Slash command lists are rebuilt from shared state with one explicit refresh call.
What's wrong with this entry?
Anonymous. No account, no email.
What
Built-in commands, loaded commands and skill-backed commands no longer sit in process-wide caches; they hang off a state object with an explicit invalidation call that also clears the workflow cache. The resulting command set is unchanged.
Evidence
cmd_load_slash_tool_skills_failed
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