Sessions

A session is the real-time connection between a developer’s worker and the user’s device.

What is a session?

Sessions are stateful actors that relay browser commands between two WebSocket connections: the worker (your backend or a hosted automation) and the client (the mobile SDK’s webview).

Session lifecycle

Sessions follow a state machine:

• created — Session initialized, tokens generated
• pending — First connection established (either client or worker)
• active — Both client and worker connected
• complete — Session finished successfully
• failed — Session terminated with an error
• expired — Session timed out

Tokens

Each session generates separate tokens for the client and worker roles. Tokens are validated on WebSocket upgrade.

Persistence

All session state is persisted in a database. There is no in-memory state to lose — the session actor can be evicted and resumed transparently.

Next steps

• Commands — How to drive the browser
• State Machine — Full state transition diagram