How shellroute works

Proxy access as simple as opening a terminal. Three steps from install to routed traffic.

1

Install the CLI

Install via npm or Homebrew. One command, no extra dependencies.

  • npm install -g shellroute
  • Log in once with shellroute login
  • Credentials stored locally on your machine
2

Start a proxy session

shellroute opens an isolated shell where HTTP_PROXY and HTTPS_PROXY are set. All HTTP-aware tools route through the selected country automatically.

  • Session-scoped — parent shell and other apps are unaffected
  • Custom prompt shows connection state, country, and exit IP
  • Slash commands: /connect, /disconnect, /rotate, /status, /countries
3

Run your workload

curl, wget, Python, Node, Playwright, Puppeteer, browser agents — anything that respects proxy env vars is routed. Metered per session, billed per GB.

  • Kill switch: traffic fails (not leaks) if the tunnel drops
  • Auto-reconnect on tunnel failure — new exit, same session
  • Usage reported every 30s; final report on disconnect

Start a session. Work normally.

Connect once. Run whatever you need. Disconnect when done.

1

Start shellroute

shellroute

Opens a proxied shell with your aliases, PATH, and functions.

2

Connect a proxy

/connect US

Pick a country. Traffic in this shell now uses the proxy.

3

Run commands normally

curl https://httpbin.org/ip
python3 check_api.py
npm run test

Every command inherits the proxy session automatically.

Start proxying your shell.

Open a session, connect a proxy, and run commands normally

Prepaid usage · Open-source CLI · No contracts