browser-session-ctl lets shell commands drive your existing logged-in Chrome session — click, type, read tabs — for use with Claude.
Yes, browser-session-ctl is open source under the GPL-3.0-or-later license.
browser-session-ctl is free to use.
Yes, browser-session-ctl can be self-hosted (the source is available under the GPL-3.0-or-later license).
browser-session-ctl is a Chrome extension plus local sidecar that lets shell commands click, type in, and read your existing logged-in browser session, for use with Claude. Open source: yes (GPL-3.0-or-later); self-hostable; pricing free. It is JavaScript, localhost-only, with 27 commits.
Most browser-automation tooling for agents launches a fresh headless browser, which then has to authenticate into every site from zero. browser-session-ctl inverts that: a Chrome extension pairs with a local sidecar listening on 127.0.0.1:8765, so shell commands — and the agent driving them — operate inside the browser session you are already signed into, clicking, typing, and reading tabs on the sites as your logged-in self. It only accepts commands from localhost, and the repo carries the extension, sidecar, scripts, and tests with an npm-based setup. Open source: yes (GPL-3.0-or-later); self-hostable; pricing free.
A lot of GTM work lives behind logins — the CRM, the ad manager, the outreach inbox, the analytics dashboard — where a from-scratch headless browser stalls on auth, MFA, and session state. browser-session-ctl lets an agent act inside the session you have already established, which is exactly what makes routine in-browser GTM chores scriptable. Open source: yes (GPL-3.0-or-later); self-hostable; pricing free. The honest read: this is the powerful-and-dangerous end of agent tooling — you are handing scripted control of your authenticated identity to an agent — so the localhost-only confinement matters, and you would want it pointed at low-stakes tasks first. The GPL-3.0-or-later copyleft is also worth noting if you plan to bundle it into anything you ship closed.