Browser and computer automation

Browser actions remain governed by the current approval and credential boundary. A connected account does not grant every possible provider action.

Provided capabilities

Capability	Status	Surfaces	Who it helps
Persistent browser sessions Keep a governed cloud browser session alive across multiple browser steps.	Live	iOS, web	Individual, Business, Team
In-chat browser Use a browser dock inside cloud text chat for explicit browsing and login handoffs.	Live	iOS	Individual
Credential vault and agent-owned accounts Complete account sign-in flows without exposing the secret itself to the language model.	Live	iOS	Individual, Business

Example outcomes

Continue a browser task. Ask Praxa to revisit a page in the same conversation and verify the session context is preserved.

Complete a login handoff. Take control for credential entry and confirm the model never receives the secret value.

Approve a browser action. Inspect the exact target and action before allowing a state-changing browser step.

Prefer extraction for reading. Ask for page content and confirm Praxa uses a read path rather than an unnecessary interactive session.

Verify the surface

Confirm the capability status and listed surface in the Capability Atlas.

Exercise the example with the smallest safe scope and inspect the visible result or approval card.

Test one unavailable, denied, or disconnected state so the surface fails honestly.

Use a developer tutorial only when this guide links to a supported public developer contract.

Provided capabilities