Install
Load it into Chrome in a few clicks.
No Node, no build tools. Download the release zip, unpack it, and load the folder as an unpacked extension.
-
Download
Get pagehand.zip from the latest GitHub Release.
-
Unzip
Extract the zip to a folder you will keep — Chrome reads that folder every time it starts. Don’t delete it after installing.
-
Open Extensions
In Chrome’s address bar, go to chrome://extensions and press Enter.
-
Turn on Developer mode
Toggle Developer mode in the top-right corner of that page.
-
Load unpacked
Click Load unpacked, then choose the folder you unzipped (the one that contains
manifest.json). -
Open Pagehand
Click the puzzle icon in the toolbar, pin Pagehand, open the side panel, and add your API key in Settings.
To update later: download the new zip, replace the folder contents, then click the reload icon on chrome://extensions. Prefer building yourself? See the GitHub setup.
How it works
The side panel owns the debugger.
No Node sidecar. No MCP bridge. Pagehand talks Chrome DevTools Protocol from inside the extension and drives the page you are looking at.
-
Open the panel
⌘/Ctrl+Shift+K, or click the toolbar icon.
-
Drop in a key
DeepSeek by default — OpenAI, Anthropic, or any OpenAI-compatible endpoint also work.
-
Ask it to act
Summarize, click, fill forms, chase console errors, or walk a multi-step flow on the live page.
Capabilities
Same protocol Puppeteer speaks.
Accessibility snapshots, input, navigation, screenshots, console and network — implemented against CDP domains, not a brittle DOM scraper.
-
take_snapshotRead the page as a structured accessibility tree with stable uids.
-
click / fill / typeDrive forms and UI the way a user would — including select-all before replace.
-
navigate / pagesMove between pages and manage them while the agent keeps context.
-
console / networkInspect errors and requests without opening DevTools yourself.
-
evaluate_scriptRun focused page scripts when reading the tree is not enough.
-
take_screenshotCapture what the page looks like and keep it in the chat thread.
Privacy
Your key never leaves your machine for us.
Pagehand has no backend. API keys stay in chrome.storage.local
and are sent only to the model provider you choose. While attached,
Chrome shows a “Pagehand is debugging this browser” banner —
that is intentional and cannot be hidden.
Read the full privacy policy →