kdcokenny/ocx

What it solves

OCX allows users to manage and apply custom configurations (profiles) and components to OpenCode across different repositories without needing to modify the repositories themselves. It addresses the need for consistent, auditable, and portable AI agent configurations that can be shared via registries.

How it works

OCX acts as a configuration manager that uses a "ShadCN-style" approach, where components are copied directly into a project's .opencode/ directory rather than being hidden in dependencies. It uses profiles to control what the AI agent sees via include and exclude patterns, and it employs SHA-256 verification to ensure the integrity of components installed from registries.

Who it’s for

Developers using OpenCode who want to maintain their own set of AI agent instructions and configurations across multiple projects, or teams wanting to distribute curated AI components via registries.

Highlights

• Portable Profiles: Apply your own configuration to any repository without modifying the source code.
• Registry System: Install profiles and components from curated, remote registries.
• Auditable Code: Components are SHA-verified and owned by the user, ensuring the AI agent only runs reviewed code.
• Granular Control: Manage what OpenCode sees through specific include and exclude patterns.