anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 18:25:32 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

[FEATURE]: Access web interface from different device #8412

New Issue
Open
opened 2026-02-16 18:09:54 -05:00 by yindo · 4 comments
yindo commented 2026-02-16 18:09:54 -05:00
Owner
Copy Link
Copy Source

Originally created by @ianldgs on GitHub (Feb 3, 2026).

Originally assigned to: @adamdotdevin on GitHub.

Feature hasn't been suggested before.

  • 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.

Originally created by @ianldgs on GitHub (Feb 3, 2026). Originally assigned to: @adamdotdevin on GitHub. ### Feature hasn't been suggested before. - [x] 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`.
yindo added the discussionweb labels 2026-02-16 18:09:54 -05:00
yindo commented 2026-02-16 18:09:55 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Feb 3, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #10288: Mobile version of OpenCode (Android/iOS/Web UI) - related to accessing OpenCode from different devices
  • #6461: Named Remote Connections with Session Origin Tracking - addresses accessing OpenCode on remote servers with better session management
  • #5784: MCP auth configuration for multi-tenant serve deployments - addresses running OpenCode in serve mode with auth for multiple users/devices

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Feb 3, 2026): This issue might be a duplicate of existing issues. Please check: - #10288: Mobile version of OpenCode (Android/iOS/Web UI) - related to accessing OpenCode from different devices - #6461: Named Remote Connections with Session Origin Tracking - addresses accessing OpenCode on remote servers with better session management - #5784: MCP auth configuration for multi-tenant serve deployments - addresses running OpenCode in serve mode with auth for multiple users/devices Feel free to ignore if none of these address your specific case.
yindo commented 2026-02-16 18:09:55 -05:00
Author
Owner
Copy Link
Copy Source

@ianldgs commented on GitHub (Feb 3, 2026):

Maybe related to #10519 too

@ianldgs commented on GitHub (Feb 3, 2026): Maybe related to #10519 too
yindo commented 2026-02-16 18:09:55 -05:00
Author
Owner
Copy Link
Copy Source

@rschaeuble commented on GitHub (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 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.

@rschaeuble commented on GitHub (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 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`.
yindo commented 2026-02-16 18:09:55 -05:00
Author
Owner
Copy Link
Copy Source

@ianldgs commented on GitHub (Feb 13, 2026):

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)

@ianldgs commented on GitHub (Feb 13, 2026): 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`)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label discussion web
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#8412
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?