Browser tools that agents use start from an empty profile. The page you wanted to update shows a login screen, while the Chrome window where you are already signed in sits right there, unused. Chrome locks that profile folder, and it will not open a debugging port on its default data directory.
browser-automate is a skill for Claude Code and Cursor that gets around both limits. It copies one Chrome profile's cookies and preferences into a temporary folder, launches a second Chrome on that copy with a DevTools port, and connects Playwright over CDP. Your everyday window stays open.
On the same Mac and the same macOS user, Chrome decrypts those cookies with the Keychain key it already has. The clone opens already signed in.
Install
git clone https://github.com/gokulnathan66/browser-automate-skill.git
cd browser-automate-skill
./install.sh
The installer links the skill into ~/.claude/skills and ~/.cursor/skills. You need macOS, Google Chrome, Node 18 or newer, Python 3, and the Playwright npm package.
What to ask for
Fill my Wellfound skills from my resume, and use my existing Chrome profile.
The first recipe fills the Wellfound profile. It types each skill, waits for Wellfound's own suggestions, and accepts only an exact tag. It skips entries labeled "New …". A looser match is the wrong behavior here: Wellfound hides skills you already have, so the next suggestion can be a different tag.
Why a copy, not the live profile
A second Chrome process cannot open the profile folder while your normal Chrome holds it. Quitting Chrome to free the lock closes every tab. The copy leaves that window alone. The skill deletes the copy at the end of the run, because the folder holds live session cookies.
The clone only works on the same Mac and the same user. The skill does not upload those cookies.
Source: https://github.com/gokulnathan66/browser-automate-skill
Top comments (0)