{"version":"2.1.234","anchor":"background-agent-failures-are-labelled-with-a-clearable-reas","canonical_anchor":"background-agent-failures-are-labelled-with-a-clearable-reas","heading":"Background agent failures are labelled with a clearable reason","tier":"notice","area":"Background Agents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/background-agent-failures-are-labelled-with-a-clearable-reas","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Background agent failures are labelled with a clearable reason\n\nA stopped background agent now tells you whether it was auth, billing, context limit or model availability.\n\n**What**\n\nWhen 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.\n\n**Details**\n\n- The auth category is deliberately suppressed for remote sessions, where re-authenticating locally would not help.\n\n**Evidence**\n\n`credit balance too low`\n\n- Area: Background Agents\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}