{"version":"2.1.280","anchor":"login-remedy-hints-surfaced-on-reloginauth-failures-for-inb","canonical_anchor":"login-remedy-hints-surfaced-on-reloginauth-failures-for-inb","heading":"Login-remedy hints surfaced on relogin\/auth failures for inbox reads and cloud subagent launches","tier":"notice","area":"Auth","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/login-remedy-hints-surfaced-on-reloginauth-failures-for-inb","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Login-remedy hints surfaced on relogin\/auth failures for inbox reads and cloud subagent launches\n\nLogin errors now come with a suggested fix instead of just an error message\n\n**What**\n\nWhen reading a peer's inbox message fails because the session needs to log in again, or when launching a remote\/cloud subagent (a delegated Claude Code task running elsewhere) fails because of a missing access token or an authentication rejection, the response now includes a `remedy` describing what's wrong (for example, `auth_expired` or `auth_overridden`), built from the current login and credentials state, instead of just a plain error string.\n\n**Why**\n\nThis gives a more specific reason when a login-related failure happens, making it easier to understand what needs to be fixed, such as logging in again.\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}