Stagehand
Open-source browser automation framework for combining code, Playwright-style control, and AI-assisted web actions.
Open the source and read safety notes before installing.
Citation facts
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
- Canonical URL
- https://heyclau.de/entry/tools/stagehand
- Source URLs
- https://docs.stagehand.dev, https://github.com/browserbase/stagehand, https://www.stagehand.dev
- Brand
- Stagehand
- Brand domain
- stagehand.dev
- Brand asset source
- brandfetch
- Author
- Browserbase
- Claim status
- unclaimed
- Last verified
- 2026-04-27
Schema details
- Install type
- copy
- Troubleshooting
- No
- Scope
- Source repo
- Website
- https://www.stagehand.dev
- Pricing
- open-source
- Disclosure
- heyclaude_pick
- Application category
- DeveloperApplication
- Operating system
- macOS, Windows, Linux
Full copyable content
## Editorial notes
Stagehand is a strong fit for agent workflows that need deterministic browser automation with optional AI assistance.
## Disclosure
Editorial listing. No paid placement or affiliate link is used.About this resource
Editorial notes
Stagehand is a strong fit for agent workflows that need deterministic browser automation with optional AI assistance.
Disclosure
Editorial listing. No paid placement or affiliate link is used.
Source citations
Add this badge to your README
Show that Stagehand is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/tools/stagehand)How it compares
Stagehand side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | Open-source browser automation framework for combining code, Playwright-style control, and AI-assisted web actions. Open dossier | Open-source browser automation library for building AI agents that can navigate, click, type, and inspect websites. Open dossier | Cloud browser infrastructure for browser automation, AI agents, scraping workflows, and web interaction at scale. Open dossier | MIT-licensed CDP browser-control harness from Browser Use that lets Claude Code, Codex, and other coding agents connect to a real or cloud Chrome browser, use screenshots and coordinate clicks, edit task-specific helpers, and optionally learn reusable domain skills for web automation workflows. Open dossier |
|---|---|---|---|---|
| Trust | ||||
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety · Privacy · | Safety ✓ Privacy ✓ | Safety · Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | ||||
| Category | tools | tools | tools | tools |
| Source | first-party | source-backed | source-backed | source-backed |
| Author | Browserbase | Browser Use | Browserbase | Browser Use |
| Added | 2026-04-27 | 2026-04-27 | 2026-04-27 | 2026-06-18 |
| Platforms | CLI | CLI | CLI | CodexCLI |
| Source repo | — | — | — | — |
| Safety notes | — missing | ✓Browser Use drives a real browser and can navigate, click, type, and submit forms autonomously; run it against trusted sites and review actions before granting access to logged-in sessions or sensitive accounts. | — missing | ✓Browser Harness can connect agents to a real logged-in Chrome profile. Remote debugging may expose active sessions, extensions, bookmarks, history, page content, downloads, uploads, and account actions to the agent. The documented Way 1 setup uses the user's everyday Chrome profile through `chrome://inspect/#remote-debugging`; require explicit user consent before attaching to sensitive accounts. The documented Way 2 setup launches Chrome with a non-default `--user-data-dir` and remote debugging port; keep that isolated profile separate from everyday browser data. Remote Browser Use Cloud sessions require `BROWSER_USE_API_KEY`, may use proxies, can persist profile state, and can continue billing until timeout or shutdown. Agents using Browser Harness can edit `agent-workspace/agent_helpers.py` and optional domain-skill files; review generated helper code and public skill contributions before reuse. Browser automation can submit forms, send messages, purchase items, scrape websites, change account settings, and upload files. Keep destructive or account-writing tasks behind confirmation. |
| Privacy notes | — missing | ✓Page content, screenshots, and DOM data are sent to the configured LLM provider to plan actions, and agents can read and submit data on authenticated sites; control credentials and which pages agents can access. | ✓Browserbase runs browsers in its cloud, so the pages you visit, screenshots, and session data are processed on Browserbase infrastructure; avoid driving authenticated or sensitive sessions without reviewing data handling and retention. | ✓Browser Harness workflows can expose page screenshots, DOM text, URLs, cookies-backed login state, account data, downloads, uploads, form inputs, and extracted website data to the agent and configured model providers. Profile sync for Browser Use Cloud is documented as cookies-only, but it still moves browser authentication material into a remote browser environment. Cloud browser live URLs, proxy settings, profile identifiers, daemon logs, `/tmp` socket or pid files, and copied support artifacts may reveal browsing activity or account context. Public domain-skill PRs should not include secrets, private selectors tied to confidential apps, customer data, screenshots, credentials, tokens, or personal browsing history. |
| Prerequisites | — none listed | — none listed | — none listed |
|
| Install | — | — | — | |
| Config | — | — | — | — |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Related resources
Browser Use
Open-source browser automation for AI agents.
Browserbase
Cloud browser infrastructure for AI agents.
Related guides
Source-backed guides for putting this to work.
Featured in
Signals
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.