Typing a slash after a rate-limit checkpoint clears the prefilled "continue" so your command runs cleanly.
What's wrong with this entry?
When the usage-limit checkpoint flow prefills your input with continue, typing a slash now removes that prefill so the slash command runs as typed instead of being appended to it.
- The cancellation is reported as
tengu_rl_checkpoint_auto_continue_cancelled_by_slash, a new event in this build.
tengu_rl_checkpoint_auto_continue_cancelled_by_slash
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