[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-73509":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":17,"stars7d":18,"stars30d":19,"stars90d":16,"forks30d":16,"starsTrendScore":20,"compositeScore":21,"rankGlobal":10,"rankLanguage":10,"license":22,"archived":23,"fork":23,"defaultBranch":24,"hasWiki":23,"hasPages":23,"topics":25,"createdAt":10,"pushedAt":10,"updatedAt":31,"readmeContent":32,"aiSummary":33,"trendingCount":16,"starSnapshotCount":16,"syncStatus":34,"lastSyncTime":35,"discoverSource":36},73509,"steel-browser","steel-dev\u002Fsteel-browser","steel-dev","🔥 Open Source Browser API for AI Agents & Apps. Steel Browser is a batteries-included browser sandbox that lets you automate the web without worrying about infrastructure.","https:\u002F\u002Fsteel.dev",null,"TypeScript",7153,938,21,23,0,26,62,141,78,39.92,"Apache License 2.0",false,"main",[26,27,28,29,30],"ai","ai-agents","ai-tools","browser-automation","llm","2026-06-12 02:03:14","\u003Cbr \u002F>\n\u003Cp align=\"center\">\n\u003Ca href=\"https:\u002F\u002Fsteel.dev\">\n  \u003Cimg src=\"images\u002Fsteel_header_logo.png\" alt=\"Steel Logo\" width=\"100\">\n\u003C\u002Fa>\n\u003C\u002Fp>\n\n\n\n\u003Ch3 align=\"center\">\u003Cb>Steel\u003C\u002Fb>\u003C\u002Fh3>\n\u003Cp align=\"center\">\n    \u003Cb>The open-source browser API for AI agents & apps.\u003C\u002Fb> \u003Cbr \u002F>\n    The best way to build live web agents and browser automation tools.\n\u003C\u002Fp>\n\n\u003Cdiv align=\"center\">\n\n[![Commit Activity](https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Fcommit-activity\u002Fm\u002Fsteel-dev\u002Fsteel-browser?color=yellow)](https:\u002F\u002Fgithub.com\u002Fsteel-dev\u002Fsteel-browser\u002Fcommits\u002Fmain)\n[![License](https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Flicense\u002Fsteel-dev\u002Fsteel-browser?color=yellow)](https:\u002F\u002Fgithub.com\u002Fsteel-dev\u002Fsteel-browser\u002Fblob\u002Fmain\u002FLICENSE)\n[![Discord](https:\u002F\u002Fimg.shields.io\u002Fdiscord\u002F1285696350117167226?label=discord)](https:\u002F\u002Fdiscord.gg\u002Fsteel-dev)\n[![Twitter Follow](https:\u002F\u002Fimg.shields.io\u002Ftwitter\u002Ffollow\u002Fsteeldotdev)](https:\u002F\u002Ftwitter.com\u002Fsteeldotdev)\n[![GitHub stars](https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Fstars\u002Fsteel-dev\u002Fsteel-browser)](https:\u002F\u002Fgithub.com\u002Fsteel-dev\u002Fsteel-browser)\n\n\u003C\u002Fdiv>\n\n\u003Ch4 align=\"center\">\n    \u003Ca href=\"https:\u002F\u002Fapp.steel.dev\u002Fsign-up\" target=\"_blank\">\n      Get Started\n  \u003C\u002Fa>  ·\n    \u003Ca href=\"https:\u002F\u002Fdocs.steel.dev\u002F\" target=\"_blank\">\n      Documentation\n  \u003C\u002Fa>  ·\n  \u003Ca href=\"https:\u002F\u002Fsteel.dev\u002F\" target=\"_blank\">\n      Website\n  \u003C\u002Fa> ·\n  \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fsteel-dev\u002Fsteel-cookbook\" target=\"_blank\">\n      Cookbook\n  \u003C\u002Fa>\n\u003C\u002Fh4>\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\"images\u002Fdemo.gif\" alt=\"Steel Demo\" width=\"600\">\n\u003C\u002Fp>\n\n## ✨ Highlights\n\n[Steel.dev](https:\u002F\u002Fsteel.dev) is an open-source browser API that makes it easy to build AI apps and agents that interact with the web. Instead of building automation infrastructure from scratch, you can focus on your AI application while Steel handles the complexity.\n\nUnder the hood, it manages sessions, pages, and browser processes, allowing you to perform complex browsing tasks programmatically without any of the headaches:\n- **Full Browser Control**: Uses Puppeteer and CDP for complete control over Chrome instances -- allowing you to connect using Puppeteer, Playwright, or Selenium.\n- **Session Management**: Maintains browser state, cookies, and local storage across requests\n- **Proxy Support**: Built-in proxy chain management for IP rotation\n- **Extension Support**: Load custom Chrome extensions for enhanced functionality\n- **Debugging Tools**: Built-in request logging and a UI to view\u002Fdebug sessions with\n- **Anti-Detection**: Includes stealth plugins and fingerprint management\n- **Resource Management**: Automatic cleanup and browser lifecycle management\n- **Browser Tools**: Exposes APIs to quick convert pages to markdown, readability, screenshots, or PDFs.\n\n\nFor detailed API documentation and examples, check out our [API reference](https:\u002F\u002Fdocs.steel.dev\u002Fapi-reference) or explore the Swagger UI directly at `http:\u002F\u002F0.0.0.0:3000\u002Fdocumentation`.\n\n> Steel is in public beta and evolving every day. Your suggestions, ideas, and reported bugs help us immensely. Do not hesitate to join in the conversation on [Discord](https:\u002F\u002Fdiscord.gg\u002Fsteel-dev) or raise a GitHub issue. We read everything, respond to most, and love you.\n\nIf you love open-source, AI, and dev tools, [we're hiring across the stack](https:\u002F\u002Fjobs.ashbyhq.com\u002Fsteel)!\n\n### Make sure to give us a star ⭐\n\n\u003Cimg width=\"200\" alt=\"Start us on Github!\" src=\"images\u002Fstar_img.png\">\n\n## 🛠️ Getting Started\nThe easiest way to get started with Steel is by creating a [Steel Cloud](https:\u002F\u002Fapp.steel.dev) account. Otherwise, you can deploy this Steel browser instance to a cloud provider or run it locally.\n\n## ⚡ Quick Deploy\nIf you're looking to deploy to a cloud provider, we've got you covered.\n\n| Deployment methods | Link |\n| -------------------- | ----- |\n| Pre-built Docker Image (combined API + UI) | [![Deploy with Github Container Registry](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FGHCR-478CFF?style=for-the-badge&labelColor=478CFF&logo=github&logoColor=white)](https:\u002F\u002Fgithub.com\u002Fsteel-dev\u002Fsteel-browser\u002Fpkgs\u002Fcontainer\u002Fsteel-browser) |\n| 1-click deploy to Railway | [![Deploy on Railway](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FRailway-B039CB?style=for-the-badge&labelColor=B039CB&logo=railway&logoColor=white)](https:\u002F\u002Frailway.app\u002Fdeploy\u002Fsteelbrowser) |\n| 1-click deploy to Render | [![Deploy to Render](https:\u002F\u002Frender.com\u002Fimages\u002Fdeploy-to-render-button.svg)](https:\u002F\u002Frender.com\u002Fdeploy) |\n\n\n## 💻 Running Locally\n\n### Docker\n\nThe simplest way to deploy\u002Frun a Steel browser instance locally is to run the pre-built Docker image:\n\n```bash\n# Pull and run the Docker image\ndocker run -p 3000:3000 -p 9223:9223 ghcr.io\u002Fsteel-dev\u002Fsteel-browser\n```\n\nThis will start the Steel browser server on port 3000 (http:\u002F\u002Flocalhost:3000) and the UI at http:\u002F\u002Flocalhost:3000\u002Fui. The 9223 port is used for the console debugger.\n\nYou can now create sessions, scrape pages, take screenshots, and more. Jump to the [Usage](#usage) section for some quick examples on how you can do that.\n\nAlternatively, you can run the API and UI separately with docker compose:\n\n```bash\ndocker compose up\n```\n\nFor Mac Silicon users, you will need to pass this env flag to the Docker compose command to run the images on the correct platform:\n```bash\nDOCKER_DEFAULT_PLATFORM=linux\u002Farm64 docker compose up\n```\n\n## Quickstart for Contributors\nWhen developing locally, you will need to run the [`docker-compose.dev.yml`](.\u002Fdocker-compose.dev.yml) file instead of the default [`docker-compose.yml`](.\u002Fdocker-compose.yml) file so that your local changes are reflected. Doing this will build the Docker images from the [`api`](.\u002Fapi) and [`ui`](.\u002Fui) directories and run the server and UI on port 3000 and 5173 respectively.\n\n```bash\ndocker compose -f docker-compose.dev.yml up\n```\n\nYou will also need to run it with `--build` to ensure the Docker images are re-built every time you make changes:\n\n```bash\ndocker compose -f docker-compose.dev.yml up --build\n```\n\nIf you run on a custom host, create a `.env` file (see `docs\u002FDEVELOPMENT_SETUP.md` for variables) or modify the environment variables used by `docker-compose.dev.yml` to use your host.\n\n### Node.js\nAlternatively, if you have Node.js and Chrome installed, you can run both the server and the UI directly:\n\n```bash\nnpm install\nnpm run dev\n```\n\nThis will also start the Steel server on port 3000 and the UI on port 5173.\n\nMake sure you have the Chrome executable installed and in one of these paths:\n\n- **Linux**:\n  `\u002Fusr\u002Fbin\u002Fgoogle-chrome`\n\n- **MacOS**:\n  `\u002FApplications\u002FGoogle Chrome.app\u002FContents\u002FMacOS\u002FGoogle Chrome`\n\n- **Windows**:\n  - `C:\\Program Files\\Google\\Chrome\\Application\\chrome.exe` OR\n  - `C:\\Program Files (x86)\\Google\\Chrome\\Application\\chrome.exe`\n\n#### Custom Chrome Executable\n\nIf you have a custom Chrome executable or a different path, you can set the `CHROME_EXECUTABLE_PATH` environment variable to the path of your Chrome executable:\n\n```bash\nexport CHROME_EXECUTABLE_PATH=\u002Fpath\u002Fto\u002Fyour\u002Fchrome\nnpm run dev\n```\n\nFor more details on where this is checked look at [`api\u002Fsrc\u002Futils\u002Fbrowser.ts`](.\u002Fapi\u002Fsrc\u002Futils\u002Fbrowser.ts).\n\n## 🏄🏽‍♂️ Usage\n> If you're looking for quick examples on how to use Steel, check out the [Cookbook](https:\u002F\u002Fgithub.com\u002Fsteel-dev\u002Fsteel-cookbook).\n>\n> Alternatively you can play with the [REPL package](.\u002Frepl\u002FREADME.md) too `cd repl` and `npm run start`\n\nThere are two main ways to interact with the Steel browser API:\n1. [Using Sessions](#sessions)\n2. [Using the Quick Actions Endpoints](#quick-actions-api)\n\nIn these examples, we assume your custom Steel API endpoint is `http:\u002F\u002Flocalhost:3000`.\n\nThe full REST OpenAPI documentation can be found [on our site](https:\u002F\u002Fdocs.steel.dev\u002Fapi-reference) and on your local Steel instance at `http:\u002F\u002Flocalhost:3000\u002Fdocumentation`.\n\n#### Using the SDKs\nIf you prefer to use the our Python and Node SDKs, you can install the `steel-sdk` package for Node or Python.\n\nThese SDKs are built on top of the REST API and provide a more convenient way to interact with the Steel browser API. They are fully typed, and are compatible with both Steel Cloud and self-hosted Steel instances (changeable using the `baseURL` option on Node and `base_url` on Python).\n\nFor more details on installing and using the SDKs, please see the [Node SDK Reference](https:\u002F\u002Fgithub.com\u002Fsteel-dev\u002Fsteel-node\u002Fblob\u002Fmain\u002Fapi.md) and the [Python SDK Reference](https:\u002F\u002Fgithub.com\u002Fsteel-dev\u002Fsteel-python\u002Fblob\u002Fmain\u002Fapi.md).\n\n\n### Sessions\nThe `\u002Fsessions` endpoint lets you relaunch the browser with custom options or extensions (e.g. with a custom proxy) and also reset the browser state. Perfect for complex, stateful workflows that need fine-grained control.\n\nOnce you have a session, you can use the session ID or the root URL to interact with the browser. To do this, you will need to use Puppeteer or Playwright. You can find some examples of how to use Puppeteer and Playwright with Steel in the docs below:\n* [Puppeteer Integration](https:\u002F\u002Fdocs.steel.dev\u002Foverview\u002Fguides\u002Fpuppeteer)\n* [Playwright with Node](https:\u002F\u002Fdocs.steel.dev\u002Foverview\u002Fguides\u002Fplaywright-node)\n* [Playwright with Python](https:\u002F\u002Fdocs.steel.dev\u002Foverview\u002Fguides\u002Fplaywright-python)\n\n\u003Cdetails open>\n\u003Csummary>\u003Cb>Creating a Session using the Node SDK\u003C\u002Fb>\u003C\u002Fsummary>\n\u003Cbr>\n\n```typescript\nimport Steel from 'steel-sdk';\n\nconst client = new Steel({\n  baseURL: \"http:\u002F\u002Flocalhost:3000\", \u002F\u002F Custom API Base URL override\n});\n\n(async () => {\n  try {\n    \u002F\u002F Create a new browser session with current API fields\n    const session = await client.sessions.create({\n      blockAds: true,\n      proxyUrl: \"user:pass@host:port\", \u002F\u002F optional\n      dimensions: { width: 1280, height: 800 }, \u002F\u002F optional\n    });\n    console.log(\"Created session with ID:\", session.id);\n  } catch (error) {\n    console.error(\"Error creating session:\", error);\n  }\n})();\n````\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n\u003Csummary>\u003Cb>Creating a Session using the Python SDK\u003C\u002Fb>\u003C\u002Fsummary>\n\u003Cbr>\n\n````python\nimport os\nfrom steel import Steel\n\nclient = Steel(\n    base_url=\"http:\u002F\u002Flocalhost:3000\",  # Custom API Base URL override\n)\n\ntry:\n    # Create a new browser session with custom options\n    session = client.sessions.create(\n        block_ads=True,\n        proxy_url=\"user:pass@host:port\",  # optional\n        dimensions={\"width\": 1280, \"height\": 800},  # optional\n    )\n    print(\"Created session with ID:\", session.id)\nexcept Exception as e:\n    print(\"Error creating session:\", e)\n````\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n\u003Csummary>\u003Cb>Creating a Session using Curl\u003C\u002Fb>\u003C\u002Fsummary>\n\u003Cbr>\n\n```bash\n# Launch a new browser session\ncurl -X POST http:\u002F\u002Flocalhost:3000\u002Fv1\u002Fsessions \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\n    \"proxyUrl\": \"user:pass@host:port\",\n    \"blockAds\": true,\n    \"dimensions\": { \"width\": 1280, \"height\": 800 }\n  }'\n```\n\u003C\u002Fdetails>\n\n\n#### Selenium Sessions\n>**Note:** This integration does not support all the features of the CDP-based browser sessions API.\n\nFor teams with existing Selenium workflows, the Steel browser provides a drop-in replacement that adds enhanced features while maintaining compatibility. You can simply use the `isSelenium` option to create a Selenium session:\n\n```typescript\n\u002F\u002F Using the Node SDK\nconst session = await client.sessions.create({ isSelenium: true });\n```\n```python\n# Using the Python SDK\nsession = client.sessions.create(is_selenium=True)\n```\n\u003Cdetails>\n\u003Csummary>\u003Cb>Using Curl\u003C\u002Fb>\u003C\u002Fsummary>\n\u003Cbr>\n\n```bash\n# Launch a Selenium session\ncurl -X POST http:\u002F\u002Flocalhost:3000\u002Fv1\u002Fsessions \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\n    \"isSelenium\": true\n  }'\n```\n\u003C\u002Fdetails>\n\u003Cbr>\n\nThe Selenium API is fully compatible with Selenium's WebDriver protocol, so you can use any existing Selenium clients to connect to the Steel browser. **For more details on using Selenium with Steel, refer to the [Selenium Docs](https:\u002F\u002Fdocs.steel.dev\u002Foverview\u002Fguides\u002Fselenium).**\n\n### Quick Actions API\nThe `\u002Fscrape`, `\u002Fscreenshot`, and `\u002Fpdf` endpoints let you quickly extract clean, well-formatted data from any webpage using the running Steel server. Ideal for simple, read-only, on-demand jobs:\n\n\u003Cdetails open>\n\u003Csummary>\u003Cb>Scrape a Web Page\u003C\u002Fb>\u003C\u002Fsummary>\n\u003Cbr>\n\nExtract the HTML content of a web page.\n\n```bash\n# Example using the Actions API\ncurl -X POST http:\u002F\u002F0.0.0.0:3000\u002Fv1\u002Fscrape \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\n    \"url\": \"https:\u002F\u002Fexample.com\",\n    \"delay\": 1000\n  }'\n```\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n\u003Csummary>\u003Cb>Take a Screenshot\u003C\u002Fb>\u003C\u002Fsummary>\n\u003Cbr>\n\nTake a screenshot of a web page.\n```bash\n# Example using the Actions API\ncurl -X POST http:\u002F\u002F0.0.0.0:3000\u002Fv1\u002Fscreenshot \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\n    \"url\": \"https:\u002F\u002Fexample.com\",\n    \"fullPage\": true\n  }' --output screenshot.png\n```\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n\u003Csummary>\u003Cb>Download a PDF\u003C\u002Fb>\u003C\u002Fsummary>\n\u003Cbr>\n\nDownload a PDF of a web page.\n```bash\n# Example using the Actions API\ncurl -X POST http:\u002F\u002F0.0.0.0:3000\u002Fv1\u002Fpdf \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\n    \"url\": \"https:\u002F\u002Fexample.com\"\n  }' --output output.pdf\n```\n\u003C\u002Fdetails>\n\n## Get involved\nSteel browser is an open-source project, and we welcome contributions!\n- Questions\u002Fideas\u002Ffeedback? Come hangout on [Discord](https:\u002F\u002Fdiscord.gg\u002Fsteel-dev)\n- Found a bug? Open an issue on [GitHub](https:\u002F\u002Fgithub.com\u002Fsteel-dev\u002Fsteel-browser\u002Fissues)\n\n## License\n[Apache 2.0](.\u002FLICENSE)\n\n---\n\nMade with ❤️ by the Steel team.\n","Steel Browser 是一个开源的浏览器API，专为AI代理和应用程序设计，旨在简化网页自动化过程而无需担心基础设施问题。它支持完整的浏览器控制、会话管理和代理支持等功能，允许开发者通过Puppeteer、Playwright或Selenium连接并操作Chrome实例。此外，Steel还提供了扩展支持、调试工具、反检测机制以及资源管理等特性，使得复杂的浏览任务变得简单易行。该项目非常适合需要构建与Web交互的AI应用或进行大规模网页自动化的场景使用。",2,"2026-06-11 03:45:53","high_star"]