-
Notifications
You must be signed in to change notification settings - Fork 169
Insights: steel-dev/steel-browser
Overview
Could not load contribution data
Please try again later
5 Pull requests merged by 4 people
-
fix: ensure requests made back to the API are not proxied
#42 merged
Jan 20, 2025 -
Measure traffic usage if proxy server is specified
#38 merged
Jan 20, 2025 -
feat: add CHROME_EXECUTABLE_PATH environment variable for custom chromium binaries
#41 merged
Jan 19, 2025 -
fix: update manifest version to v3 and push improvements to session recorder
#40 merged
Jan 19, 2025 -
Feat/configurable setup
#39 merged
Jan 19, 2025
5 Pull requests opened by 3 people
-
DRAFT: Feat/enable simple token auth
#43 opened
Jan 21, 2025 -
Allow to disable fingerprinting for a session
#44 opened
Jan 22, 2025 -
Allow to upload custom extensions or import from Chrome Web Store
#46 opened
Jan 23, 2025 -
Reuse browser instance between sessions if args are the same
#48 opened
Jan 24, 2025 -
fix: stray chrome processes causing buildup
#49 opened
Jan 24, 2025
2 Issues closed by 2 people
-
This response body is massive! Syntax highlighting won’t work here.
#28 closed
Jan 24, 2025 -
[Feature Request] Allow JS execution and console logs access
#45 closed
Jan 23, 2025
1 Issue opened by 1 person
-
[BUG] Browser processes left running after closing npm run dev with CTRL+C on my m4 mac
#47 opened
Jan 23, 2025
1 Unresolved conversation
Sometimes conversations happen on old items that aren’t yet closed. Here is a list of all the Issues and Pull Requests with unresolved conversations.
-
use steel icon for automated chrome instance
#1 commented on
Jan 23, 2025 • 0 new comments