A stopped background agent now tells you whether it was auth, billing, context limit or model availability.
What's wrong with this entry?
When a background agent run stops, its stop reason is now mapped to one of auth, billing, context limit or model unavailable, each with a user-facing label and error code, so a failed run says why it failed. A "credit balance too low" stop is reported as a billing problem.
- The auth category is deliberately suppressed for remote sessions, where re-authenticating locally would not help.
credit balance too low
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.232
Background dialog gains a Completed section and lets you stop finished agents
Both mention background agent
-
v2.1.232
Task list keeps your place, and Enter opens a running agent
Both mention background agent
-
v2.1.239
Workers can register as parked instead of idle
Both mention background agent