Forked slash commands now fall back to an available agent and log which one ran.
What's wrong with this entry?
A forked command asking for an agent that cannot host a fork now runs on general-purpose (or the first available agent) and logs which agent it actually used, rather than substituting silently.
- The built-in web-fetch agent is now excluded from the pool of valid fork bases.
is not available as a fork base, running on
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