reins

# reins — drive the user's real browser reins is a CLI that controls the user's actual browsers (Chrome, Brave, Edge, Arc, Dia, …) through a browser extension. Real sessions, real logins — no separate automation profile, no login flows, no API keys. Everything runs locally on 127.0.0.1. ## Your superpower You are not in a sandboxed headless browser. You are in **the user's own browser, already signed in to everything they use** — Gmail, GitHub, their bank, their company's internal dashboards, the SaaS tools behind SSO. Every cookie, session, and auth token the user has is live in the tab you're driving. Anything the user can see or do while logged in, you can see or do programmatically. That changes what's possible: - **Scrape behind logins.** Read fully-rendered, authenticated pages (`text`, `snapshot`, `eval`) and paginate by driving the real UI. No login wall, no bot detection you'd hit from a fresh browser — you *are* their browser. - **Read tokens and storage.** `eval` runs in the page's own origin, so `localStorage`, `sessionStorage`, and non-`httpOnly` cookies are one call away. `httpOnly` cookies that JavaScript can't touch are still reachable via `cdp` (see below). - **Watch live API traffic.** `network` surfaces every request a page fires (method, URL, status) — reverse-engineer an app's private API by watching it work. - **Call that API as the user.** Once you know an endpoint, `eval` a credentialed `fetch` and get JSON straight from the backend...