How to install globally for opencode (not per project)

[mandarvaze]

The docs refer to cloning the repo and starting opencode from the cloned directory

It is not clear whether this will work for all the projects that use opencode, or do I need to clone ECC repo everywhere (does not make sense)

I want a "global" install so that once installed, ECC can be used across multiple projects with opencode

[eminfedar]

Yes and I want to use it without npm.

[affaan-m]

The supported "global" path is the npm package plus the installer/CLI, not cloning ECC into every target project.

Concretely:

• install the package once
• use the package/plugin wiring for the OpenCode runtime pieces
• use ecc-install (or the root install docs) to materialize the instructions/commands/agents you want in the projects that should use them

What is not recommended is cloning the full ECC repo into every project directory just to make OpenCode work.

Also, a packaging gap that existed around .opencode/dist has been fixed on main, and we added a regression test to keep the npm tarball from silently shipping without the built OpenCode payload again. So the current direction is explicitly toward a cleaner reusable install surface, not per-project repo clones.

[tech-and-avinash]

But still not listing skills when using npm install -g ecc-universal and inlcude "plugin": ["ecc-universal"], then ecc install --profile full --target opencode

[chenhz01]

The install guidance above is right, but @tech-and-avinash's August report is still open, and the cause is almost always location rather than profile: ecc install --target opencode materializes into a project-local .opencode/, while a globally launched opencode resolves skills from its own global dir — so the files exist and are still not listed.

Confirm which tree got written and which one opencode reads:

find . -path '*opencode*' -name 'SKILL.md' | head
ls ~/.config/opencode/

First list non-empty and second empty means a path mismatch, not a broken package.