Changelog #018
Chrome extension support, enhanced scraping capabilities, and improved reliability across the platform with 25+ bug fixes.
⭐ New
Chrome Extension Support
Steel now supports the ability to customize your browser sessions with Chrome Extensions. You can upload and use extensions from files or directly from the Chrome Web Store. Extensions are stored globally per organization and can be injected into any session using extension IDs or the all_ext parameter.
1# Upload extension from Chrome Web Store2response = client.extensions.upload_from_store(3url="https://chromewebstore.google.com/detail/..."4)56# Inject extensions into session7session = client.sessions.create(8extension_ids=['all_ext'] # or specific extension IDs9)
Extensions integrate with Steel's browser sessions through the Chrome DevTools Protocol and are initialized when sessions start.
Available on: Steel Cloud ☁️ | Steel-browser (OSS) 🔧
Enhanced HTML to Markdown Conversion
Improved scraping algorithms on the /scrape endpoint now include HTML sanitization before markdown conversion and other reliability improvements, ensuring cleaner output and preventing rendering issues across all session types.
Available on: Steel Cloud ☁️ | Steel-browser (OSS) 🔧
🔧 Improvements
-
Added .env keys management to playground for easier usage
-
Updated logging mechanisms for better test execution visibility and debugging
-
Improved extension loading with corrected path resolution and naming conventions
🐛 Bug Fixes
-
Fixed Puppeteer context evaluation errors with __name polyfill
-
Resolved device inconsistencies and enabled web security by default
-
Fixed deployment configuration for improved connectivity
-
25+ additional bug fixes across Steel Cloud and steel-browser
As always, thanks for testing out the Steel beta. We really look forward to more of your feedback and continuing to build with this awesome, curious, and supportive community.