AI GitHub
Steel Browser for remote browser sessions
Provide browser infrastructure that automation clients can connect to.
Key Takeaways
- Steel exposes managed browser sessions and connection details for automation clients.
- The browser service provides a session endpoint.
- Connect a small script to a new session, inspect a fixture page and close it.
- A remote browser can carry authenticated state.
How it works
Steel exposes managed browser sessions and connection details for automation clients. It is the browser layer under a script or agent that decides what to do.
What you need
The browser service provides a session endpoint. Bring a client that can speak the exposed browser protocol and be deliberate about whether session state is preserved.
What to try first
Connect a small script to a new session, inspect a fixture page and close it. Repeat with concurrent sessions and confirm their cookies remain isolated.
Simulate an expired session and confirm the client can detect it. A clean lifecycle makes it easier to distinguish browser service failures from agent errors.
Where to look for failures
A remote browser can carry authenticated state. Control session lifetime and access to debugging endpoints, and decide what artifacts to retain after execution.
Related Franklin pages
Separate browser provisioning from the logic that chooses the next action. Run against a fixture with a login and test what happens when the session expires mid-workflow.
- Build repeatable browser workflows around forms, navigation and extracted data. Skyvern for running browser workflows
- Combine explicit browser steps with natural-language actions, extraction and observation. Stagehand for code and model-assisted browser automation
For an agent interface that reaches mobile apps, see Franklin’s guide to Phone-Use. Phone-Use
Project documentation
Try it for your workflow
Explore the project’s documentation for setup and usage, or save this page to a collection for later.
Read the project documentation ↗