[FEATURE]: The WorkSpace settings in OpenCode Web #14656

Activity

1. ZYZMZM98

   added

   discussionUsed for feature requests, proposals, ideas, etc. Open discussionUsed for feature requests, proposals, ideas, etc. Open discussion

   on Feb 22, 2026
2. github-actions

   assigned

   nexxeln

   on Feb 22, 2026
3. github-actions

   added

   coreAnything pertaining to core functionality of the application (opencode server stuff)Anything pertaining to core functionality of the application (opencode server stuff)

   webRelates to opencode on web / desktopRelates to opencode on web / desktop

   on Feb 22, 2026
4. gitrequests commented on Mar 22, 2026

   

   gitrequests

   on Mar 22, 2026

   More actions

   Web mode: project selection screen shows / and hides actual workspace path (Docker)

   Description

   According to the documentation, OpenCode uses the current working directory as the project root when launching in web mode.

   However, when running OpenCode in web mode inside Docker, the UI shows a project selection screen that does not reflect the actual workspace directory.

   Instead, it shows / as a recent project, which is misleading.

   ---

   Screenshot

   

   Observed behavior in the UI:

   • "Recent projects" shows /
   • No indication of the actual working directory (/home/opencode/workspace)
   • No visible link between the UI and the configured workspace

   ---

   Expected behavior

   One of the following:

   • Automatically open the working directory (/home/opencode/workspace) as the active project
   • OR clearly display something like:

   Current workspace: /home/opencode/workspace
   

   • OR list the mounted workspace directory instead of /

   ---

   Actual behavior

   • A project selection screen is shown
   • Only / appears under "Recent projects"
   • The actual workspace path is not visible anywhere
   • User must manually guess or re-select the correct directory

   ---

   Why this matters

   This creates confusion, especially in containerized environments:

   • The working directory is explicitly set (working_dir)
   • The workspace is mounted and known
   • But the UI behaves as if no project is selected

   This is particularly problematic for:

   • Docker setups
   • Remote environments
   • New users expecting automatic project detection

   ---

   Docker setup

   services:
     opencode:
       image: ghcr.io/anomalyco/opencode:latest
       working_dir: /home/opencode/workspace
       volumes:
         - ./opencode:/home/opencode
         - ./workspace:/home/opencode/workspace
       command: ["web", "--hostname", "0.0.0.0", "--port", "4096"]
       environment:
         - HOME=/home/opencode
       ports:
         - "4096:4096"

   ---

   Suggested improvements

   • Detect and auto-open the current working directory as the active project
   • Display the current workspace path in the UI
   • Avoid showing / as the default project when a working directory is explicitly set
   • Provide a clear "Open current workspace" option

   Thanks!

   👍React with 👍1Reacted by Neuralyze
5. gitrequests commented on Mar 22, 2026

   

   gitrequests

   on Mar 22, 2026

   More actions

   Related issues:

   • Why do I have a project with path / in OpenCode Web UI? #18593
   • Recent projects shows "/" when started in non-git directory #15719
   • opencode serve uses / as base directory when started from non-root path allowing access to arbitrary locations + permission path mismatches #14445

   👍React with 👍2Reacted by Alexey Volkov and Neuralyze
6. thdxr

   removed

   discussionUsed for feature requests, proposals, ideas, etc. Open discussionUsed for feature requests, proposals, ideas, etc. Open discussion

   webRelates to opencode on web / desktopRelates to opencode on web / desktop

   coreAnything pertaining to core functionality of the application (opencode server stuff)Anything pertaining to core functionality of the application (opencode server stuff)

   on May 3, 2026
7. github-actions commented on Jul 4, 2026

   

   github-actionsBot

   on Jul 4, 2026 – with GitHub Actions

   Contributor

   More actions

   To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

   👎React with 👎1Reacted by Dzmitry Senchankau
8. github-actions

   closed this as not plannedon Jul 4, 2026