Request a Sign-In Code
Start the OTP flow and send a sign-in code to the correct email address.
Trigger the OTP request from the CLI and continue into verification without switching tools.
- Start the OTP flow correctly.
- Use the correct purpose value for sign-in or sign-up.
- Handle cooldowns and lockouts without guessing.
Where this happens
- `curl` and `jq` must be available on the local machine.
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 request-otp you@example.com signin` when you already know you need the OTP flow.
- 2. Use `signup` instead of `signin` when you are intentionally creating a new human identity.
- 3. Read the JSON result in the terminal and wait for the email to arrive.
- 4. Continue directly to code verification rather than rerunning the request command unnecessarily.
Keep Going in Sign In and Sessions
Stay in the same interface and move to the next closest task in this topic when needed.
Verify the Sign-In Code
Complete the OTP flow, establish the human session, and move into the workspace or terminal workflow.
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.