Ravi

Credentials Across Worktrees

Ravi gives AI agents their own identity (email inbox, real phone, encrypted vault) so they can sign up for services, receive verification codes, and keep the passwords they create. For teams whose agents have to act on the web, not just talk.

Store the password across worktrees

Same identity stores the password it created in the encrypted vault, so the next worktree can retrieve it instead of signing up again. The vault lives on the identity in the Ravi API, not in the git worktree. A new checkout that authenticates as that identity reads the same password.

After signup, mint an identity-scoped key (ravi_id_...) and pass it into each runtime. A management key (ravi_mgmt_...) can also target the identity with ?identity=<uuid>. Device-code login (ravi auth login) against https://api.ravi.app stores keys in ~/.ravi/config.json for local CLI use. The CLI is one identity per machine — shared ~/.ravi/config.json is not a multi-agent runtime. Multiple agents on one host use the HTTP API with per-identity ravi_id_... keys.

export RAVI_API_KEY="ravi_id_..."
export IDENTITY_UUID="<identity-uuid>"

# Save the password the agent just created.
curl -X POST "https://api.ravi.app/api/passwords/?identity=$IDENTITY_UUID" \
  -H "Authorization: Bearer $RAVI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"domain": "acme.com", "username": "agent", "password": "..."}'

# In another worktree, with the same identity key, read it back.
curl "https://api.ravi.app/api/passwords/?identity=$IDENTITY_UUID" \
  -H "Authorization: Bearer $RAVI_API_KEY"

Do not leave the password in the worktree. Store it on the identity, then authenticate the next runtime with the same ravi_id_... key.

Signup and first identity: Sign Up (https://docs.ravi.app/getting-started/sign-up.txt). Key types and device-code login: Authentication (https://docs.ravi.app/getting-started/authentication.txt).

Next Steps