reins

Drive your real, logged-in browser from the shell — the CLI for Reins, the MCP browser bridge.

Same idea as adding Reins to a coding agent over MCP, but you drive it yourself. reins login once, then every tool your agent could call is a shell command against your real browser — real cookies, real sessions, no re-login, no fresh cloud Chromium.

npm i -g reins

reins login            # OAuth into your Reins account
reins browsers         # list your connected browsers
reins select <id>      # pick one to drive
reins open https://app.example.com/dashboard
reins snapshot         # interactive elements, with refs
reins click e7
reins type "hello" --ref e3
reins screenshot

Why this and not a local-only tool

Reins is a product, not just a local app. The CLI is the free on-ramp; behind your login sit hosted sessions, capture-to-your-own-R2 with free egress, multi-profile, and account tooling. The same reins command works from your shell and from any MCP client (Claude Code, Cursor, Zed).

Any tool, directly

The friendly verbs cover the common loop. Everything your account exposes is reachable generically:

reins tools                          # list every available tool
reins call nav '{"action":"goto","url":"https://x.com"}'
reins call dumps '{}'

Config

• Endpoint — defaults to https://reins.vulcanos.pro; override with REINS_ENDPOINT (self-host / dev).
• Token — stored at ~/.reins/config.json (owner-only).

License

MIT · © Nathanael Aninweze · the original Reins (reins.vulcanos.pro), first shipped 2026-04-30.