You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[FEATURE]: Access web interface from different device #11934
I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
Where I work, we have a VPN that allows us to access any server on each other's machine via their IP.
That means I can leave my laptop running some sessions, and check it from another device, like my phone, while I do something else.
However, all the state of the web UI (incuding the model configurations) is stored in localStorage, which makes it really hard to monitor sessions from other devices.
It would be nice if there was an easier way to see all sessions running in that server without relying on localStorage.
This issue not only exists when accessing from another browser. It also exists when opencode has to run on a different port.
So opencode web --port 4096 and opencode web --port 4097 result in localhost:4096 and localhost:4097 being opened in the browser. For the browser these are two separate web pages, and thus they get separate localstorages, requiring to configure the web app again each time this happens.
I stumbled across this issue as opencode acp by default uses the same port as opencode web. So when acp is started first and web later, I have to start fresh in the web app.
It would be nice if the web app could persist its configuration via opencode, writing it somewhere under ~/.config/opencode.
A workaround that I've found, that works relatively well:
Run opencode in the terminal (with web enabled), keep it there, don't touch it.
On the web page, open a project and enable workspaces.
That way I can at least monitor the sessions remotely and send eventual instructions.
I just have to remember to not use the free models (we aren't allowed at work). But once they're disabled on the new device, at least they stay disabled.
The TUI doesn't seem to be able to integrate well with those sessions, though (as I think it doesn't support workspaces/git worktrees)
Activity
github-actions commentedon Feb 3, 2026
This issue might be a duplicate of existing issues. Please check:
servedeployments #5784: MCP auth configuration for multi-tenant serve deployments - addresses running OpenCode in serve mode with auth for multiple users/devicesFeel free to ignore if none of these address your specific case.
ianldgs commentedon Feb 3, 2026
Maybe related to #10519 too
rschaeuble commentedon Feb 12, 2026
This issue not only exists when accessing from another browser. It also exists when opencode has to run on a different port.
So
opencode web --port 4096andopencode web --port 4097result in localhost:4096 and localhost:4097 being opened in the browser. For the browser these are two separate web pages, and thus they get separate localstorages, requiring to configure the web app again each time this happens.I stumbled across this issue as
opencode acpby default uses the same port asopencode web. So when acp is started first and web later, I have to start fresh in the web app.It would be nice if the web app could persist its configuration via opencode, writing it somewhere under
~/.config/opencode.ianldgs commentedon Feb 13, 2026
A workaround that I've found, that works relatively well:
Run
opencodein the terminal (with web enabled), keep it there, don't touch it.On the web page, open a project and enable workspaces.
That way I can at least monitor the sessions remotely and send eventual instructions.
I just have to remember to not use the free models (we aren't allowed at work). But once they're disabled on the new device, at least they stay disabled.
The TUI doesn't seem to be able to integrate well with those sessions, though (as I think it doesn't support workspaces/
git worktrees)github-actions commentedon Apr 15, 2026
To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.