[BUG][LATEST] ECC installation for OPENCODE | Global or Specific

[WUIX69]

Greetings affaan-m,

Can you please fix the installation process for Opencode either global or folder specific. it doesn't work the way it should be

PROOF:

Here y'll notice it detects the / commands of ECC but when i try to use it:

And it gives me this

ATTEMP FIX for global:

Also for global installation, it should be placed on C:\Users\{user_name}\.config\opencode in order for opencode to use it globally. I tried to ask A.I for the quick remedy and gives me this guidelines

*OPENCODE | GLOBAL FULL INSTALL | WINDOWS*
- ECC git clone method
- [05-22-2026]

### REFERENCE #1
### 1. Update the configuration directory path
Modified [opencode-home.js](file:///c:/projects/ECC/scripts/lib/install-targets/opencode-home.js#L7) to point to Windows' standard configuration directory:

  rootSegments: ['.config', 'opencode'],

### 2. Compile the TypeScript plugin (Mandatory)
Before running the installer, we ran this command to compile the TypeScript files inside `.opencode/` into their JavaScript distribution files:
node scripts/build-opencode.js
*(This is a crucial step because without it, the `.opencode/dist/` folder does not exist, and OpenCode won't find the universal plugin hooks when loading.)*

### 3. Run the installer
Finally, we ran the installer to pull everything together, apply the `full` profile, and write the configurations/assets into the destination:

node scripts/install-apply.js --target opencode --profile full

### REFERENCE #2
**Yes, absolutely!** 

Once you have updated the path in `opencode-home.js`, you can use the wrapper scripts perfectly. Any arguments you pass to the wrappers are forwarded directly to the installer. 

For example, running:

./install.ps1 --target opencode --profile full
*(or `./install.sh` on macOS/Linux)*


Is **exactly equivalent** to running `node scripts/install-apply.js --target opencode --profile full`. The wrappers will read the updated `opencode-home.js` target file and successfully copy all assets directly into `.config/opencode`.

The / command successfully can be used on global however the same issues in the picture above shows the same. can you please fix, and adjust the installation for opencode support ?

[Rudra-CSER]

Bug: / slash commands detected but non-functional after ECC global install

Environment

• OS: Windows
• Install method: ECC git clone → global profile
• Config path: C:\Users\{username}\.config\opencode

---

What's happening

After running the ECC installer with the full profile, OpenCode correctly detects the / commands (they show up in the autocomplete/menu), but executing any of them does nothing — no skill loads, no response, no error shown.

---

Root cause (suspected)

The plugin is being registered but the compiled output in dist/ is either missing or not being resolved correctly. OpenCode finds the plugin entry point but has no actual logic to execute.

---

Suggested fix

Please check/address the following in the install pipeline:

1. Make build-opencode.js a mandatory pre-install step — the dist/ folder must exist before install-apply.js runs. Consider chaining them or adding a pre-install check:

   node scripts/build-opencode.js && node scripts/install-apply.js --target opencode --profile full

2. Validate the config path resolves correctly on Windows — opencode-home.js should use os.homedir() explicitly:

   path.join(os.homedir(), '.config', 'opencode')

   Not relative to the project root.

3. Add a post-install verification step — after install, confirm that .config/opencode/dist/ is populated and the plugin entry point exists.

---

To reproduce

1. Clone ECC repo
2. Run node scripts/install-apply.js --target opencode --profile full (without building first)
3. Open OpenCode → type / → commands appear but don't execute

---

Happy to test any fix on Windows. Let me know if you need logs or the contents of .config/opencode/ after install.

[WUIX69]

Bug: / slash commands detected but non-functional after ECC global install

Environment

• OS: Windows
• Install method: ECC git clone → global profile
• Config path: C:\Users\{username}\.config\opencode

What's happening

After running the ECC installer with the full profile, OpenCode correctly detects the / commands (they show up in the autocomplete/menu), but executing any of them does nothing — no skill loads, no response, no error shown.

Root cause (suspected)

The plugin is being registered but the compiled output in dist/ is either missing or not being resolved correctly. OpenCode finds the plugin entry point but has no actual logic to execute.

Suggested fix

Please check/address the following in the install pipeline:

1. Make build-opencode.js a mandatory pre-install step — the dist/ folder must exist before install-apply.js runs. Consider chaining them or adding a pre-install check:
   node scripts/build-opencode.js && node scripts/install-apply.js --target opencode --profile full

2. Validate the config path resolves correctly on Windows — opencode-home.js should use os.homedir() explicitly:
   path.join(os.homedir(), '.config', 'opencode')

   Not relative to the project root.

3. Add a post-install verification step — after install, confirm that .config/opencode/dist/ is populated and the plugin entry point exists.

To reproduce

1. Clone ECC repo
2. Run node scripts/install-apply.js --target opencode --profile full (without building first)
3. Open OpenCode → type / → commands appear but don't execute

Happy to test any fix on Windows. Let me know if you need logs or the contents of .config/opencode/ after install.

so after running Step 1 should i update the opencode-home.js to use path.join(os.homedir(), '.config', 'opencode') or it automatically set it to this ?

IF NOT:
the opencode-home.js expects this code arguments, not customized tho

const { createInstallTargetAdapter } = require('./helpers');

module.exports = createInstallTargetAdapter({
  id: 'opencode-home',
  target: 'opencode',
  kind: 'home',
  rootSegments: ['.opencode'],
  installStatePathSegments: ['ecc-install-state.json'],
  nativeRootRelativePath: '.opencode',
});