Skip to content

File selection in the WebUI does not work #8486

Closed

Description

@jfayad

Description

When I try to reference a specific file through the @ command I constantly get a no matching result (even before typing)

On the console I see an error on the following request:

http://127.0.0.1:4096/find/file?dirs=true

which returns:

{
  "data": {
    "dirs": "true"
  },
  "error": [
    {
      "expected": "string",
      "code": "invalid_type",
      "path": [
        "query"
      ],
      "message": "Invalid input: expected string, received undefined"
    }
  ],
  "success": false
}

Plugins

none

OpenCode version

1.1.20

Steps to reproduce

  1. Open the webUI
  2. Start typing a prompt and reference a file with the @ command

Screenshot and/or share link

No response

Operating System

macOS Sonoma 14.4.1

Terminal

WebUI started from vscode terminal with opencode --port 4096 -> Ctrl+P -> Open WebUI

Activity

  1. github-actions commented on Jan 14, 2026

    @github-actions
    Contributor

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

    Both issues describe similar problems with the file search API endpoint (/find/file) in the web UI where the query parameter is not being sent properly, causing validation errors.

    Feel free to ignore if your specific case differs from these.

  2. jfayad commented on Jan 14, 2026

    @jfayad
    Author

    I confirm similarity as the request going is missing the query query param in the URL.

    Keeping this issue as this is still broken on v1.1.20

  3. xnosek00 commented on Jan 14, 2026

    @xnosek00

    Hi, I can confirm the same problem. @jfayad did you try downgrade to older version? I tryied
    opencode upgrade v1.1.13

    • v1.1.14
    • v1.1.15
    • v1.1.16

    And I had the same problem. But it works before I upgrade from v1.1.16 to 1.1.20.

    So I tryed clean docker container. I installed opencode (newest version) and I had the same problem.

    It worked before I did upgrade to 1.1.20 and downgrade doesn't work.

  4. xnosek00 commented on Jan 14, 2026

    @xnosek00

    it seems, that this bug is duplicate of this bug: #8325

    And this is related: #8326

  5. jfayad commented on Jan 14, 2026

    @jfayad
    Author

    I didn't try to downgrade, yesterday I was on 1.1.8 and it was working well. I upgraded to 1.1.20 today and this got broken

  6. carloscdante commented on Jan 19, 2026

    @carloscdante

    I'm getting the same results on macOS.

  7. jfayad commented on Jan 19, 2026

    @jfayad
    Author

    I'm wondering if the issue is appearing because of frontend resources being cached by the browser...
    it's highly possible that v1.1.8 scripts were still being used by the browser. After using a different port on one of the webUI I noticed the UI changed and the autocomplete worked

  8. xnosek00 commented on Jan 27, 2026

    @xnosek00

    Based on my latest investigation, the web UI is not loaded from Opencode on the local machine, but instead the libraries are pulled from the web. So if something is not working in the web UI, downgrading Opencode is practically pointless. Any fix to the web UI has to be done on their servers, or it’s possible to use a different web UI outside of Opencode. That’s how I handled it at the time when the web UI was completely broken for everyone.

    In any case, this thread can be closed. This issue is resolved.

  9. github-actions commented on Mar 29, 2026

    @github-actions
    Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingwebRelates to opencode on web / desktop

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions