OCX CLI
OCX keeps OpenCode setups in portable profiles and installs agents, skills and commands from registries as ordinary files.
- 981 ★ on the repository
- Last commit
- MIT
Minimal access
Why this level
- Registry components enter agent configuration, so check the registry source.
Install
- Works in
Manual install
bun install --frozen-lockfile
bun run --cwd packages/cli build
alias ocx="bun \"$PWD/packages/cli/dist/index.js\""The Set up the development preview block from the README: Bun and OpenCode V2 are required, run it in a checkout of the branch.
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- Registry components enter agent configuration, so check the registry source.
This is third-party code. Review the repository files before installing.
What it does
OCX is an extension manager for OpenCode. A profile is an ordinary folder under `~/.config/ocx/profiles/` holding OpenCode config, instructions, agents and skills. The `ocx oc` command launches OpenCode with a chosen profile. Registry components are copied into a profile or the project `.opencode/` directory and stay editable, with an ownership record for updates and removal. Before updating, OCX previews changes and verifies file hashes. Profiles are isolated from each other, so a work set does not affect a personal one.
Who it is for. OpenCode users who keep different agent sets for work, personal projects and review and need a shared way to distribute them in a team.
Good fit when
- Work and personal OpenCode profiles must not mix.
- A team distributes identical agents and skills through its own registry.
- You need to see the difference before updating a component.
- A setup moves to another machine as a folder.
Not a fit when
- You work only in Claude Code or Cursor.
- You need a ready build without installing Bun or compiling from source.
- The project stays on OpenCode V1 and `ocx@2.0.15`.
Example request
Create a work profile, make it the default and launch OpenCode through it.Limitations
This branch targets OCX 3 for OpenCode 2.0.3 or newer as a preview. Building needs Bun and OpenCode V2. For OpenCode V1 the README advises keeping `ocx@2.0.15`. The project is independent and unaffiliated with the OpenCode team. The latest commit in the repository is from September 2026. Users define registries themselves, so component content and safety depend on the chosen source. The `ocx update` and `ocx verify` commands show differences before applying, but accepting edits remains your decision.
How to disable. Remove profiles with the `ocx profile` commands or by deleting folders in `~/.config/ocx/profiles/`, and drop the `ocx` alias from your shell. Copied components remain ordinary files.
FAQ
How do I base a second profile on the first?
Run `ocx profile add personal --clone work`, then launch `ocx oc -p personal`.
How do I install a registry component?
After `ocx init --project` run `ocx add team/review --project`, where `team` is the registry name.
How do I check local edits?
`ocx update --all --project --dry-run` previews updates and `ocx verify --project` compares file hashes.
Can I migrate from V1?
Yes. `ocx migrate --from <folder> --profile work` previews the import before applying, and originals stay untouched.
What is needed to run it?
Bun and OpenCode V2. The CLI is built from a checkout of the branch and no prebuilt package is given in Quick start.
Discussion
No questions or reviews yet.
Related
CLI toolsA Windows plugin for OpenCode Desktop that sets edit boundaries, screens commands and ties test results to the current code.
A CLI that saves Codex accounts under labels and switches between them with one command, skipping repeated codex login.
An OpenCode plugin where hooks on tool and subagent calls are declared in config and command output flows into context.
A local semantic code index: the agent searches by meaning, then follows hits into definitions, callers and dependency paths
OpenCode skill set for 1C
OpenCode global settings archive (1С skills)
Around thirty OpenCode skills for 1C configurations: editing, extensions, databases, reports, forms, metadata, SKD, XDTO, roles, subsystems
OpenDomain keeps a project's business concepts and rules in repository Markdown so agents rely on them instead of guessing.
README in short
Profiles are separate folders and components are copied as files with an ownership record. V1 has a separate guide.