Built-in wording exists for a lower-priority working mode, all replaceable by server config and off by default.
Lower-priority mode ships with default copy and a confirmation, but stays off unless server config sets enabled.
What's wrong with this entry?
The lower-priority usage-limit mode carries its own built-in wording: label "Continue now at lower priority", status "Working at lower priority until {reset}", wait banner "Working at lower priority ยท waiting for capacity", and "You've used this week's lower-priority allowance". A confirmation is assembled at runtime around "Continuing now at lower priority" and ". Your weekly limit still applies, and responses may pause while waiting for spare capacity. Run /low-priority to stop." Every string can be replaced by the server config, and the whole thing stays off unless that config sets enabled to true.
- The config object is named
tengu_toasty_breezeand falls back to empty, so with no server value the feature is off. - The mode is registered as an action-kind command under the name
low-priority.
tengu_toasty_breeze
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.236
Extra-usage panel now shows for team and enterprise accounts
Both mention usage limit
-
v2.1.236
Wrap-up hint near the usage limit is now per-plan and once per window
Both mention usage limit
-
v2.1.236
Visible notice when approaching the 5-hour usage limit
Both mention usage limit