TUI referencing local directory when using attach --dir to connect to a remote server. #5380

Activity

1. jeremytondo

   added

   bugSomething isn't workingSomething isn't working

   on Dec 11, 2025
2. github-actions

   added

   opentuiThis relates to changes in v1.0, now that opencode uses opentuiThis relates to changes in v1.0, now that opencode uses opentui

   on Dec 11, 2025
3. github-actions commented on Dec 11, 2025

   

   github-actionsBot

   on Dec 11, 2025 – with GitHub Actions

   Contributor

   More actions

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

   • TUI sends absolute local paths causing ENOENT on server side #4686: TUI sends absolute local paths causing ENOENT on server side (Windows client to Linux server path resolution)
   • opencode attach: File path duplicates client's relative directory, causing ENOENT #4967: opencode attach: File path duplicates client's relative directory, causing ENOENT (similar attach path duplication issue)

   Both issues describe problems with path resolution when using remote servers with attach, where paths are resolved on the client instead of the server. Feel free to ignore if this addresses a specific case not covered by those issues.
4. jeremytondo commented on Dec 11, 2025

   

   jeremytondo

   on Dec 11, 2025

   Author

   More actions

   The related issues identified by the bot are likely related, but neither deals with using the attach --dir flag, so it may be worthwhile to keep this open? That is, if this is truly not the expected behavior.
5. rekram1-node

   self-assigned this

   on Dec 11, 2025
6. rekram1-node

   removed

   opentuiThis relates to changes in v1.0, now that opencode uses opentuiThis relates to changes in v1.0, now that opencode uses opentui

   on Dec 11, 2025
7. terwey commented on Dec 15, 2025

   

   terwey

   on Dec 15, 2025

   More actions

   I have noticed the same behavior. You can reference files in the remote server but it then throws errors as it prefixes it with the local dir.

   Also the attach needs serious work because the slightest error on the server and it just perma-hangs on a blank screen with zero indication to the user what it got stuck on.
8. oussamadouhou

   added a commit that references this issue on Dec 30, 2025

   fix: pass --dir parameter from attach command to SDK client

   ...

   This issue will close once commit b4c560b is merged into the 'dev' branch.

   b4c560b
9. cgarrot commented on Jan 10, 2026

   

   cgarrot

   on Jan 10, 2026

   More actions

   I'm experiencing this issue and wanted to provide some context about when this happens:

   General Use Case: Remote Server + Local Client
   When OpenCode server runs on a remote machine (VPS, remote workstation, container) and you attach from a local machine:

   Current behavior:

   # On local machine
   opencode attach http://remote-server:4096 --dir /path/to/project
   # Bug: The --dir path is interpreted as LOCAL machine path
   # Server receives: /local/user/path/to/project (doesn't exist on remote)
   # Result: Wrong directory, or connection fails

   Expected behavior:

   # On local machine
   opencode attach http://remote-server:4096 --dir /path/to/project
   # Should work as: Send directory path to server
   # Server receives: /remote/server/path/to/project (exists on remote)
   # Server does: chdir /remote/server/path/to/project
   # Result: Opens in correct remote directory

   Why this matters:

   1. Multi-project development: Developers work on multiple projects on a remote machine
   2. Fixed server directory: Server starts in a default directory (e.g., /home/user or /workspace)
   3. Remote-first setup: The server is the source of truth, not the local machine

   Common scenarios affected:

   • SSH tunnels to remote OpenCode servers
   • Containerized OpenCode instances
   • Development on remote workstations

   👍React with 👍5Reacted by Alexandre Reyes Martins, Haoyu Tang, Nelson Pires, Carsten Kragelund Jørgensen and Stephen Belanger
10. nyxkrage

    marked opencode attach --dir fails because it tries to change directory on the client instead of the server #8933 as a duplicate of this issue on Jan 16, 2026
11. github-actions commented on Mar 25, 2026

    

    github-actionsBot

    on Mar 25, 2026 – with GitHub Actions

    Contributor

    More actions

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

    removed

    bugSomething isn't workingSomething isn't working

    on May 3, 2026
13. rekram1-node

    closed this as not plannedon May 22, 2026