Problem
The error message:
ERR your authentication token has expired, please run chainloop auth login again
is shown for any authentication-related failure, not just token expiry. This masks the real cause — for example, invalid credentials or misconfigured endpoints return the same generic message, making it hard to diagnose the actual problem.
Expected behavior
Each failure mode should surface its own descriptive error. The "token expired" message should only appear when the token is actually expired. Other failures (invalid credentials, unreachable server, revoked token, etc.) should propagate their own error messages.
Impact
Users troubleshooting authentication issues are misled into re-running chainloop auth login when the real cause is something else entirely, increasing time-to-resolution.