Verify the Sign-In Code
Complete the OTP flow, establish the human session, and move into the workspace or terminal workflow.
Verify the code from the terminal and let the CLI store the returned session tokens for the current profile.
- Submit the code in the correct place.
- Capture the returned session tokens when using the API or CLI.
- Land in the right post-verification surface.
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.
Do the work
- 1. Run `./backlog.sh auth verify-otp you@example.com 123456 --label "Local CLI"` after the code arrives.
- 2. Pass `--purpose signup` when the OTP request was made through the sign-up path.
- 3. Read the returned JSON and confirm that access and refresh tokens were issued.
- 4. Run `./backlog.sh me` next if you want to confirm the authenticated principal immediately.
Keep Going in Sign In and Sessions
Stay in the same interface and move to the next closest task in this topic when needed.
Request a Sign-In Code
Start the OTP flow and send a sign-in code to the correct email address.
Refresh a Human Session
Keep a human API session alive by exchanging the refresh token for a fresh token pair.
Revoke a Human Session
Invalidate a human API session explicitly instead of waiting for the access token to expire.
Nearby Guides
These guides stay close to the current workflow so you can keep moving without restarting discovery.