Remote monitor

Turning it on

Settings > Remote. It is off by default. Turning it on generates a pairing token and a QR code — scan it with a phone and the monitor opens in that browser.

The port defaults to 8765 and is changeable if something else on your network already has it. The token is generated once and kept, so paired devices survive a restart.

How the connection works

The local server binds to loopback only. It is never exposed to your network directly. Instead Bentomux runs a bundled cloudflared quick tunnel, which gives it a public https://trycloudflare.com URL. That URL, with the token embedded, is what the QR encodes — there is nothing else to type.

The tunnel is end-to-end encrypted and the server refuses plain HTTP. Screen text is rendered headlessly, so what you see on the phone is the pane's actual contents with escape sequences already consumed.

What you can do

• Watch the panes you select, updating live while output is moving.
• See the full list of workspaces and panes, and which pane is focused.
• Switch between panes.
• Type into the pane you are watching.
• Answer approval prompts, through the same path the local overlay uses.

Treat the link like a password

The pairing token grants full control: everything listed above, on every pane. Anyone holding that URL can type into your shells. Do not post it, do not put it in a shared channel, and turn remote monitoring off when you do not need it.

The token is exchanged once for an HttpOnly cookie that expires after twelve hours, rather than being kept in the URL — so it does not linger in browser history or leak through Referer headers. Authentication attempts are rate-limited, and message size and write rate per socket are capped.