Skip to content
ScriptSmithPublic

About

Open a browser that uses the networking of another host, container, sandbox, kubernetes pod, or VM

Topics

Resources

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

A browser giving a thumbs-up from inside a server

rembro: remote browser

rembro opens a web browser that uses the networking of another host, container, sandbox, or VM.

Run with the --debug flag, and let your agent drive the browser via playwright.

rembro runs on Linux, macOS and Windows. Its targets run Linux.

rembro ssh:devbox                                # a tab for each dev server on devbox
rembro docker:shop-web-1 http://api:8000         # a Compose service, by its name
rembro k8s:shop/api-7d9f http://orders.shop.svc  # a cluster service, no kubectl port-forward
rembro ssh:bastion http://10.0.4.12:3000         # an address only the bastion can reach
rembro --remote ssh:devbox                       # run the browser on devbox, show its window here
rembro --debug sbx:myapp                         # let an AI agent in the sandbox drive the browser
rembro run ssh:devbox gimp                       # any GUI program, window shown here
rembro install docker:shop-web-1 firefox         # put a browser in the container for --remote

Use cases

  • Preview a web app running on a remote dev box, in a dev container or in a Docker sandbox, without ssh -L or docker run -p.
  • Open a Kubernetes service, an admin UI or a metrics dashboard without kubectl port-forward, using cluster DNS names.
  • Reach internal sites and private IPs that only a bastion host or VPN gateway can see, without setting up an ssh -D SOCKS proxy by hand.
  • Let an AI coding agent in a sandbox drive a real browser with Playwright or Puppeteer over CDP or WebDriver BiDi, while you watch.
  • Run graphical Linux programs on a server, in a container or in a VM, and see their windows on your desktop, with sound.

Install

curl -fsSL https://raw.githubusercontent.com/ScriptSmith/rembro/main/install.sh | sh

Or download it from the latest release.

Too big or complicated for your liking? Get most of the functionality with a 100 line bash script.

Where the browser runs

  • On this machine, by default. rembro points the browser at a SOCKS5 proxy on this machine's loopback, and the target makes every connection for it, DNS lookups included. You keep your own browser, fonts, GPU and window manager, with a separate profile for each target.
  • In the target, with --remote. Its window comes to this desktop through waypipe on Wayland or through a forwarded X11 connection, and its sound plays here.

Targets

Target What it is
local this machine, on Linux
ssh:[USER@]HOST[:PORT] a host or VM reached with ssh, using your ssh config
docker:NAME, podman:NAME, nerdctl:NAME a running container
apple-container:NAME a container run by Apple's container tool
sbx:SANDBOX a Docker sbx sandbox
k8s:[NAMESPACE/]POD[/CONTAINER] a pod in kubectl's current context
incus:INSTANCE, lxc:INSTANCE an Incus or LXD instance
wsl:DISTRO a WSL distribution
exec:COMMAND any command that runs its arguments in the target, such as exec:'docker compose exec -T web'

Getting started

Start a dev server in the target and run rembro TARGET. With no URL, rembro opens a tab for each HTTP server listening on the target's loopback, and more tabs as new servers start. Give URLs to open particular pages instead.

rembro picks the first browser it finds, starting with Chromium and its forks and then Firefox. Use -b firefox (or set REMBRO_BROWSER) to choose. It never uses your regular browser profile unless you ask: each target gets its own profile.

For --remote, the target needs a browser of its own. rembro install TARGET installs Chromium there, and rembro install TARGET firefox installs Firefox.

Programs in the target can open pages in rembro's browser through BROWSER and an xdg-open wrapper, so OAuth flows use the target's network (details).

rembro --help lists every option, target type and example. rembro run --help and rembro install --help cover the subcommands.

Security

  • With --debug and the browser on this machine, a program in the target can read your local files and the profile's cookies, so use --remote --debug for a target you don't trust (details).
  • --x11-trusted gives the target the same access to your X11 display that ssh -Y does, and so does an X server that can't make untrusted connections (details).
  • --remote and rembro run forward this machine's sound server, which programs in the target can record from; --no-audio turns it off (details).
  • --trust-target-ca lets the target read that profile's HTTPS traffic (details).
  • On macOS and Windows, rembro can't tell which user connects to its SOCKS server, so other users of this machine can reach the target through it while rembro runs (details).

Documentation

  • docs/install.md: the install script, release archives for Linux, macOS and Windows, and Cargo.
  • docs/usage.md: targets, containers and VMs, browsers, profiles, opening pages, --debug, rembro run, rembro install, displays on macOS and Windows, and every option.
  • docs/how-it-works.md: the agent, its transport, other architectures, networking, display and sound forwarding, reconnects, and building rembro.
  • docs/security.md: what the target can see and do, debugging, X11, sound, CA trust and the local SOCKS server.
  • docs/bash.md: rembro.sh, the core of rembro in a bash script, how it works, and what it leaves out.

License

rembro is MIT or Apache-2.0, at your option. The waypipe builds in its releases are GPL-3.0-or-later; licenses/waypipe-NOTICE.md in each release archive describes them, and waypipe-source.tar.gz in each release is their source.

About

Open a browser that uses the networking of another host, container, sandbox, kubernetes pod, or VM

Topics

Resources

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages