anomalyco / anomalyco/opencode

[BUG][OPENCODE|DESKTOP] Can't used any `/commands` on DESKTOP, suspect `~/.opencode/` and `./.config/opencode` might conflicting on each other

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

@Hona is already working on this.

Since Aug 6, 2026.

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

Description

Description

As the Title says "Can't used any /commands on DESKTOP, suspect ~/.opencode/ and ./.config/opencode might conflicting on each other".

For the past 2 months, I've been struggling to use the Opencode Desktop app anymore. The only major change I made was installing ECC and Caveman to improve my daily workflow.
Ever since then, I haven't been able to use Opencode's built-in slash commands (e.g. /init). They consistently fail with a "server error".
I already opened an issue in the Opencode repository, but with around 3.8K open issues, it seems like my report (and many others) has gone unnoticed.
What's strange is that Opencode CLI works perfectly. Every command runs without any issues. The problem only exists in the Desktop application.
After digging into it, I noticed something interesting:
The default Opencode harness is stored in ~/.config/opencode, and both the CLI and Desktop versions seem to use it without problems.
However, when installing certain tools, plugins, or harnesses (such as ECC/Caveman), they appear to be installed under ~/.opencode instead of ~/.config/opencode.
I'm starting to suspect that this mismatch between the two directories might be causing the Desktop app to fail while the CLI continues to work normally.
Has anyone experienced the same issue or figured out what's causing it? If you've found a workaround or fix, I'd really appreciate hearing about it.

Plugins

ECC, Caveman

OpenCode version

OpenCode Desktop v1.18.14

Steps to reproduce

Installed this and it will stored on ~/.opencode

opencode-debug-20260806T075437.zip

Screenshot and/or share link
Image
Operating System

Windows 10 PRO

Terminal

No response

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.