anomalyco / anomalyco/opencode

tui: @ file picker excludes tracked files under dot-directories on Windows V2

Open
#46,144 1 comment 0 reactions 1 assignee View on GitHub

@Hona is already working on this.

Since Aug 29, 2026.

2.0
Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

Description

Description

On OpenCode V2 beta for Windows, @ autocomplete omits tracked, non-ignored files when any path segment starts with .. For example, Windows/.config/opencode/opencode.json is visible through /api/fs/list, but /api/fs/find?query=opencode returns no match.

Windows defaults to the ripgrep search backend. Its catch-all index calls ripgrep.find() without hidden: true, effectively running rg --no-config --files without --hidden. This makes file-picker behavior backend-dependent and provides no config or API option to include hidden paths.

This still reproduces after #33976 was automatically closed with an invitation to open a new issue if relevant. The related fix in #34000 was closed without being merged.

Plugins

@ephemushroom/opencode-claude-mem, @ephemushroom/opencode-hermes, oh-my-openagent@beta, opencode-antigravity-auth

OpenCode version

0.0.0-beta-18684

Steps to reproduce
  1. On Windows, create a Git repository containing a tracked file such as src/.config/example.json.
  2. Confirm the file is not excluded by .gitignore.
  3. Start OpenCode V2 in the repository.
  4. Type @example.json or its full relative path.
  5. Observe that the file is absent from autocomplete.
Screenshot and/or share link

Not available. The issue is consistently reproducible through both the TUI and /api/fs/find.

Operating System

Windows 11 10.0.26200.9168

Terminal

WezTerm

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.