Why I built it: setups). - I wanted a bridge that keeps local automation while executing remotely in the browser terminal context.

How it works:

- browterm CLI sends exec requests to browterm-daemon on localhost. - Daemon serializes requests (single active command) and routes to a bound Chrome terminal tab. - Command is wrapped with markers to extract clean output + remote exit code. - Supports timeout and cancel.

Current limitations:

- Browser terminal websocket protocols vary by vendor. - Some UIs can block input fallbacks. - Cross-origin iframe terminals can reduce observability.

I’d really value feedback on reliability across terminal vendors and ideas for improving compatibility.