browser-tools
PulseGate's liveness check found it on 14 Sep 2026; it is registered on GitHub and PyPI and has been in the index since 1 Jul 2026. How this is checked
browser-tools is an open-source CLI tool for browser automation, debugging, and anti-detect browsing. It supports integration with Playwright and Chrome DevTools, and is designed for developers who need robust browser control and web scraping capabilities from the command line.
Inferred · not functionally tested
Overview
6 featuresPurpose: Automating and debugging browsers with anti-detect capabilities from the command line.
Inferred · not functionally tested
Audience: developers needing browser automation and scraping tools
Inferred · not functionally tested
Functions: browser_automation
Inferred · not functionally tested
Interfaces: API: unknown · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: unknown
Recorded constraints: pricing: open_source · license: MIT · platforms: CLI · deployment: cli
Constraint provenance is unknown; confirm requirements with the publisher.
Record sources: pypi.org · github.com. These links do not verify the individual claims.
browser-tools sits in PulseGate's CLI tools & terminal category. Inferred · not functionally tested: It focuses on automating and debugging browsers with anti-detect capabilities from the command line. Inferred · not functionally tested: browser-tools is an open-source project aimed at developers needing browser automation and scraping tools. Basis unknown · not verified: browser-tools is open source under the MIT license. Basis unknown · not verified: browser-tools is available on the command line.
Behind browser-tools is dungle-scrubs, and it first shipped in 2026. Inferred · not functionally tested: Key capabilities include browser automation, debugging tools, and anti-detect browsing. Basis unknown · not verified: Catalogued interfaces include an MCP server.
Summary written by a language model from the project’s public pages.
Tasks: Inferred · not functionally tested
- Browser automation
- Debugging tools
- Anti-detect browsing
- Web scraping
- Playwright integration
- Chrome DevTools support
Topics: Inferred · not functionally tested
Built with & integrations
Trust & compliance
Indexing history
7What PulseGate has recorded for this listing
Frequently asked questions about browser-tools
- What is browser-tools?
- Inferred · not functionally tested: Browser-tools focuses on automating and debugging browsers with anti-detect capabilities from the command line. It is catalogued under CLI tools & terminal on PulseGate.
- Who should use browser-tools?
- Inferred · not functionally tested: browser-tools is an open-source project built for developers needing browser automation and scraping tools.
- Is browser-tools free?
- Basis unknown · not verified: Yes — browser-tools is open source under the MIT license and free to use.
- What platforms does browser-tools run on?
- Basis unknown · not verified: browser-tools runs on the command line.
- Is browser-tools still active?
- PulseGate's liveness check found it on 14 Sep 2026.
- What projects are similar to browser-tools?
- Similar projects tracked by PulseGate include browser-act-cli, browser-automation-cli, and browserget.browser-act-clibrowser-automation-clibrowserget
- Who makes browser-tools?
- browser-tools is developed by dungle-scrubs.
- When did browser-tools launch?
- browser-tools first shipped in 2026.
Similar projects
Closest matches by what these projects do