Ravi

Many agents, one browser

Many agents, one human, one browser. Cookies, signed-in sessions, and CLI credentials sit in one pool. A second agent can reuse a session the first one opened, or reuse the human’s. That is the login wall. Grok Bot’s own computer-and-apps doc says every Bot shares one computer, and screens are not a security boundary. Reusing a human session, or handing the human the browser at “enter email,” is the wall. Each agent needs its own Ravi identity (inbox, phone, vault) so it can sign up, wait on the code, and store the password as itself.

Nobody gives an agent inbox + phone + vault as one identity.

https://docs.x.ai/grok-bot/computer-and-apps

Your agent hit a login wall (https://docs.ravi.app/getting-started/login-wall.txt). When to Use (https://docs.ravi.app/getting-started/when-to-use.txt). Sign Up (https://docs.ravi.app/getting-started/sign-up.txt). Authentication (https://docs.ravi.app/getting-started/authentication.txt).

What is shared

Cookies, signed-in sessions, and CLI credentials sit in one pool. Many agents share one browser and one session pool. A second agent can reuse a session the first one opened, or reuse the human’s. Every Bot shares one computer, and screens are not a security boundary.

What each agent needs

Each agent needs its own Ravi identity (inbox, phone, vault) so it can sign up, wait on the code, and store the password as itself.

Next Steps