claude-code - 💡(How to fix) Fix --teleport fails with 'Session expired' on confirmed-active cloud session (OAuth, correct account) [2 comments, 2 participants]

• I tried from a second alias signed into a different work account too — same error. The error message is misleading: nothing visible is actually expired.

1. Observe immediate error: Session expired. Please run /login to sign in again. Either teleport succeeds, or the error explains what is actually wrong (e.g. account mismatch, scope mismatch, session ownership, server-side state).

• #22972 (closed as dup of #20976) — same error string but different root cause (env-var override). This appears to be a separate failure mode of the same generic "Session expired" error. Suggest improving the error message to distinguish: (a) local auth missing/expired, (b) account mismatch with session owner, (c) session not found server-side, (d) scope/subscription mismatch.

TL;DR

The issue is likely due to a mismatch between the local CLI authentication and the cloud session ownership, and improving the error message to distinguish between different failure modes could help diagnose the issue.

Guidance

• Verify that the cloud session is indeed owned by the same account that is signed in via OAuth in the local CLI, and that the session is not archived or expired on the server-side.
• Check the scope and subscription settings for the account to ensure they match the requirements for the cloud session.
• Consider adding more detailed error messages to the claude CLI to distinguish between different failure modes, such as account mismatch, scope mismatch, or session not found server-side.
• Test the claude --teleport command with a different session ID to see if the issue is specific to one session or a more general problem.

Example

No code snippet is provided as the issue seems to be related to authentication and session management, and not a specific code problem.

Notes

The issue is likely related to the authentication and session management mechanisms of the claude CLI, and improving the error messages could help diagnose the issue. However, without more information about the internal workings of the claude CLI and its authentication mechanisms, it is difficult to provide a more specific solution.

Recommendation

Apply a workaround by verifying the account and session settings, and consider improving the error messages to distinguish between different failure modes, as the root cause of the issue is not clearly identified.