anomalyco / anomalyco/opencode

TUI fails to start due to infinite recursion when scanning skills directories with cyclic symlinks

Open
#40,349 1 comment 0 reactions 1 assignee View on GitHub

@jlongster is already working on this.

Since Aug 4, 2026.

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

Description

Description

When running opencode on Windows, the TUI screen remains completely blank. Commands like -h and -v work normally, but entering the TUI shows nothing.

Troubleshooting process:

  1. opencode --mini worked fine initially, indicating core functionality was intact.
  2. Running opencode (without --mini) resulted in a blank screen.
  3. Ran opencode --pure --print-logs --log-level DEBUG to collect detailed logs.
  4. Logs revealed thousands of duplicate skill name warnings with endlessly nested paths (e.g., vue\vue\vue\...\SKILL.md), indicating the program entered an infinite recursion loop while scanning skills directories.
  5. Deleting ~/.claude/skills and ~/.agents/skills immediately resolved the issue.
Plugins

None

OpenCode version

1.18.11

Steps to reproduce
  1. Have two skill directories in the user folder:
    • C:\Users\<username>\.claude\skills\
    • C:\Users\<username>\.agents\skills\
  2. Create cyclic symbolic links (junction points) between them (e.g., skills/vue pointing to each other).
  3. Run opencode and observe a blank TUI screen.
  4. Check logs with --log-level DEBUG and observe infinite duplicate skill name warnings with recursive paths.
Screenshot and/or share link

Log snippet:

level=WARN message="duplicate skill name" name=vue existing="C:\\Users\\cai\\.claude\\skills\\vue\\vue\\vue\\...\\SKILL.md" duplicate="C:\\Users\\cai\\.agents\\skills\\vue\\vue\\vue\\...\\SKILL.md"

The vue segment repeats hundreds of times, indicating the scanner entered an infinite loop. Full log file grew to several MB with thousands of similar warnings.

Image
Operating System

Windows 11 (10.0.26200.8655)

Terminal

Windows Terminal / PowerShell

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.