explaingit

steel-dev/steel-browser

7,020TypeScriptAudience · developerComplexity · 3/5Setup · easy

TLDR

Steel is an open-source browser automation server that gives AI agents a simple API to control a real Chrome browser, create sessions, navigate pages, capture screenshots, and extract content without building browser infrastructure yourself.

Mindmap

mindmap
  root((steel-browser))
    What it does
      Browser sessions
      Page navigation
      Screenshot capture
      Content extraction
    Compatible tools
      Puppeteer
      Playwright
      Selenium
    SDKs
      Python SDK
      Node.js SDK
      REST API
    Audience
      AI developers
      Automation builders
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Let an AI agent browse websites and fill out forms on your behalf by pointing it at a Steel session API.

USE CASE 2

Scrape JavaScript-rendered pages without setting up your own headless browser, using Steel's session management.

USE CASE 3

Build an AI research tool that navigates multiple URLs and returns clean readable text from each page.

USE CASE 4

Capture screenshots of web pages programmatically through Steel's REST API for visual testing or monitoring.

Tech stack

TypeScriptNode.jsChromeDockerPythonCDP

Getting it running

Difficulty · easy Time to first run · 30min

Requires Docker and a Chrome installation for local self-hosting, the hosted cloud version at steel.dev skips setup entirely.

In plain English

Steel is an open-source tool that gives AI applications a way to control a real web browser. The idea is that AI agents often need to browse websites, fill out forms, take screenshots, or extract content, but wiring up a browser to an AI system from scratch involves a lot of low-level infrastructure work. Steel handles that infrastructure layer so the AI application can focus on what it actually needs to do. Under the hood, Steel runs a Chrome browser process and exposes an API your code can call to create browser sessions, navigate pages, capture screenshots, convert pages to readable text or PDF, and manage cookies and local storage. It uses an existing browser automation protocol called CDP (Chrome DevTools Protocol), which means it is compatible with popular automation libraries like Puppeteer, Playwright, and Selenium. It also includes some detection-avoidance features and support for routing traffic through proxies. You can run Steel yourself using a pre-built Docker image or by installing it locally with Node.js and a Chrome installation. One Docker command starts the server on port 3000 and a debugging UI at the same address. There is also a hosted cloud version at steel.dev if you do not want to manage the server yourself. The project provides two SDKs, one for Python and one for Node.js, as well as a REST API with full documentation. A separate Cookbook repository contains ready-to-use examples for common tasks like scraping, web research, and interacting with sites that require login. Steel is aimed at developers building AI agents and automation tools that need reliable, programmable browser access. It is in public beta, open source, and actively developed. The license is available in the repository.

Copy-paste prompts

Prompt 1
Show me how to start a Steel browser session with the Python SDK, navigate to a URL, and extract its readable text content.
Prompt 2
I am building an AI agent that needs to fill out web forms, show me how to use Steel to automate form interaction step by step.
Prompt 3
Help me set up the Steel server locally with Docker and connect to it from a Node.js Playwright script for browser automation.
Prompt 4
Show me how to manage browser cookies and local storage through the Steel REST API for a site that requires login.
Prompt 5
How do I route Steel browser sessions through a proxy to avoid rate limiting during large-scale web scraping?
Open on GitHub → Explain another repo

← steel-dev on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.