Steel

Publishes Steel Browser infrastructure and official cloud-browser Skills for live browsing, reusable code, and session diagnosis.

About Steel

Steel maintains the open-source steel-browser project and related browser-service tooling. The infrastructure supplies browser sessions; agent reasoning and application logic remain with the connected client or code.

Steel supplies browser infrastructure for agents and automation code. A workflow creates a browser session, connects its chosen client, performs page work, and releases the session. The open-source browser server and hosted service are distinct operating choices; cloud-oriented Skills do not automatically describe a self-hosted deployment.

Official Skills are maintained in steel-dev/skills and target specific cloud-browser jobs. The hosted MCP service and the open-source browser runtime have different setup paths, which should be checked before equating the repository with a cloud account.

Software from Steel

Begin with the browser backend: a server you operate or a hosted session. Then follow the matching client and session-cleanup instructions.

Alternatives to Steel Workflows

Compare Browserbase for SDK automation and hosted sessions, Skyvern for reusable business workflows, Lightpanda for a lightweight browser engine, Bright Data for managed web data services. Choose by the browser environment and task result you need.

Frequently Asked Questions

What does Steel publish as source?
The linked steel-browser repository provides browser infrastructure, while companion repositories contain interfaces and official agent instructions.
Is Steel the task-planning agent?
The infrastructure provides sessions and connectivity. A coding agent or application supplies task reasoning, inputs, and output verification.
Where are the official Skills?
steel-dev/skills maintains operating, developer, and session-diagnosis guidance. Read each Skill’s service assumptions instead of treating all of them as local-server instructions.
Does open-source setup create a hosted account?
No. Hosted MCP authentication and session access are service-level setup. They do not appear automatically when the open-source runtime starts.
What does Apache-2.0 apply to?
It applies to the steel-browser source. Cloud time, account limits, model usage, and companion-package licensing must be assessed separately.
How should a failed session be reported?
Keep the session ID, relevant step, and redacted runtime evidence. Official steel-session-debugging guidance can help distinguish infrastructure failure from target-site behavior.

Inspect a Hosted Browser Session

A short extraction checks the full session lifecycle, including cleanup. A useful result records whether the session was released as well as what the page contained.