> ## Documentation Index
> Fetch the complete documentation index at: https://ocx.kdco.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# OCX for OpenCode V2

> Your OpenCode config, anywhere — portable profiles and editable components

OCX gives you named OpenCode setups you can use across projects, and a way to share the files that make them useful.

* **Switch profiles.** Keep separate configurations for work, personal projects, and review.
* **Own your files.** Install agents, skills, commands, and profile recipes from a registry, then edit them directly.
* **Review updates.** Preview file changes, protect local edits, and verify installations against recorded hashes.

> [!NOTE]
>
> **OCX 3 is the OpenCode V2 preview.** It requires OpenCode 2.0.3 or newer within major version 2. The frozen OCX 2.0.15 line supports OpenCode V1. The legacy documentation remains available in the navigation.

## Get started

After [setting up the preview](https://ocx.kdco.dev/docs/v2/installation.md), create a profile and launch:

```sh theme={null}
ocx profile add work
ocx profile use work
ocx oc
```

The profile is an ordinary directory under `~/.config/ocx/profiles/`, or `$XDG_CONFIG_HOME/ocx/profiles/`. Add your native OpenCode configuration, instructions, agents, and skills there. OCX selects the directory; OpenCode loads its contents.

> **[Installation](https://ocx.kdco.dev/docs/v2/installation.md)**
>
> Set up the development preview and select your OpenCode V2 executable.

> **[Quick start](https://ocx.kdco.dev/docs/v2/quick-start.md)**
>
> Create, customize, and switch between your first profiles.

> **[File registries](https://ocx.kdco.dev/docs/v2/registries.md)**
>
> Install editable components and manage their updates.

> **[Moving from V1](https://ocx.kdco.dev/docs/v2/migration.md)**
>
> Preview an import while keeping your existing setup intact.

## What OCX manages

| OCX | OpenCode |
| - | - |
| Profile creation, cloning, naming, and selection | Native configuration and terminal preferences |
| Registry sources, file installation, and ownership receipts | Agents, tools, plugins, MCP, and permissions |
| Update previews, edit protection, and removal | Sessions, credentials, background work, and compaction |
| Static registry authoring and legacy import | Native runtime and service behavior |

There is no OCX runtime plugin or launch-time configuration overlay. Profiles share OpenCode's native credential and session storage; they are configuration choices, not separate accounts. See [profile behavior](https://ocx.kdco.dev/docs/v2/profiles.md) for project discovery and instruction loading.

## Explore the reference

* [Configuration](https://ocx.kdco.dev/docs/v2/configuration.md) explains each OCX file, source scope, and selection rule.
* [CLI reference](https://ocx.kdco.dev/docs/v2/cli.md) covers commands, options, examples, and exit codes.
* [Create a registry](https://ocx.kdco.dev/docs/v2/registry-authoring.md) walks through publishing your own components.
* [Troubleshooting](https://ocx.kdco.dev/docs/v2/troubleshooting.md) covers version checks, file conflicts, and recovery.

OCX is an independent project and is not affiliated with the OpenCode team.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.