Release notes and distribution updates for OpenRemote.
Dev Servers with OpenRemote Gateway
OpenRemote can now show dev servers started from OpenCode and open them from the app.
This works through OpenRemote Gateway. The gateway detects local servers associated with your OpenCode workspace, creates a short-lived forwarding link, and proxies the dev server through the same authenticated OpenRemote connection.
The goal is simple: if OpenCode starts a local web app, you should be able to preview it from your phone without copying ports, opening extra tunnels, or exposing the server directly.
This also gives OpenRemote a clearer direction for gateway features. Sessions are still the center of the app, but the useful work around a session often includes a running preview, a docs site, or another local service.
I started OpenRemote because I wanted a simple way to check in on OpenCode from my phone while away from my desk.
It turns out a lot of other people want that too, and the more I use it, the more obvious one limitation becomes: remote access should not depend quite so much on the one OpenCode TUI window I happened to leave open.
OpenRemote Gateway is the first step toward fixing that. It runs as a small local process on your machine, keeps remote access available, and gives the app a steadier place to reconnect when you come back later.
For now it is still work in progress and source-build only, but it is already shaping the direction of the project. Gateway makes OpenRemote less about a single live terminal and more about getting back to your work when you need to.
I am excited about the new interaction models this can enable for OpenCode. Imagine opening OpenRemote and seeing the work that needs attention, reconnecting to a recent workspace without caring whether the old terminal is still open, starting OpenCode where you left off, pairing another device when someone needs to jump in, or reaching the local web app OpenCode started so you can preview the local build on the go.
This is so cool: for the first time, OpenCode users can step away from their desktop without worrying what their agents are doing while they are not watching.
Remote Tunnels let you securely connect to your desktop OpenCode session from the OpenRemote app on iOS or Android, even when your phone is not on the same local network.
The first provider is Cloudflare, which means private beta testers can use remote access for free while OpenRemote continues to evolve.
Thank you to the 14 testers helping shape OpenRemote through the private beta, and thank you to Riley Maersch for the project's first community contribution.
Want access? DM Blair Hudson or comment "this is so cool" on the LinkedIn post, and I will reach out for your App Store or Google Play invite email.
OpenRemote now has a signed Android APK available from GitHub Releases. Android users can install directly while Google Play distribution remains in progress.
Update: OpenRemote is now available in private beta through Google Play Internal Testing, and the signed Android APK remains available for direct install.
OpenRemote has moved through the first public distribution milestones: the app is open source under FSL-1.1-MIT, installation docs are live, the optional OpenCode plugin is documented, and the first Android sideload release is available.
iOS TestFlight and Google Play Internal Testing are now available to private beta users.
For the current submission timeline and planned features, see the OpenRemote roadmap.