Revoke a Human Session
Invalidate a human API session explicitly instead of waiting for the access token to expire.
CLI In this interface
4 steps Steps
2 interfaces Available in
Use this path when
Use the built-in revoke command for the currently stored human session.
What you'll finish here
- Invalidate a session deliberately.
- Clear local credentials after revocation.
- Avoid mixing session revocation with PAT rotation.
Where this happens
Same Task, Other Interfaces
Use the version that matches where you are working now. The subject matter stays the same; the delivery changes by surface.
Keep this boundary clear
- Use PAT revocation for personal API keys and secret rotation for workspace automations. Do not use session revoke for those credential types.
Do the work
- 1. Confirm that the current auth mode is a human session rather than a PAT or automation token.
- 2. Run `./backlog.sh auth revoke`.
- 3. Let the CLI clear the access token, refresh token, and in-memory app access token state after success.
- 4. Run `./backlog.sh status` if you want to confirm the profile is now unauthenticated.
Keep Going in Sign In and Sessions
Stay in the same interface and move to the next closest task in this topic when needed.
CLI Sign In and Sessions
Request a Sign-In Code
Start the OTP flow and send a sign-in code to the correct email address.
4 steps
CLI Sign In and Sessions
Verify the Sign-In Code
Complete the OTP flow, establish the human session, and move into the workspace or terminal workflow.
4 steps
CLI Sign In and Sessions
Refresh a Human Session
Keep a human API session alive by exchanging the refresh token for a fresh token pair.
4 steps
Nearby Guides
These guides stay close to the current workflow so you can keep moving without restarting discovery.