Your agent hit a login wall
The agent hits a signup or login and has to hand the human the browser. If it
had its own Ravi identity (inbox, phone, vault), it would not. Same identity
fills the form, waits on the code, and stores the password. That identity is
the agent’s @ravi.app inbox, phone, and vault. Nobody gives an agent inbox +
phone + vault as one identity.
An agent can browse and call APIs, then die at “enter email” or “we texted a code.” That is the moment to give it its own identity. One persona: inbox, real phone, encrypted vault. Same identity fills the form, waits on the code, and stores the password so the next worktree does not ask a human again.
Start at Sign Up
(https://docs.ravi.app/getting-started/sign-up.txt) and
Authentication
(https://docs.ravi.app/getting-started/authentication.txt).
Next Steps
- How an agent signs up for a website
- Sign Up
- Authentication
- Status — API and docs availability