Analysis updated 2026-05-18
Add a custom button or panel to the OpenCode Desktop interface without patching the app.
Package and distribute a mod as a single .ocdx file other users can drag and drop to install.
Build a trusted main-process extension that needs deeper access than the sandboxed renderer allows.
Try out example mods like Keep Awake or Vertical Tabs to see what OCDX extensions can do.
| hona/opencode-desktop-extensions | alamops/agetor | aza-ali/blendpixel.com | |
|---|---|---|---|
| Stars | 12 | 12 | 12 |
| Language | TypeScript | TypeScript | TypeScript |
| Setup difficulty | moderate | hard | easy |
| Complexity | 3/5 | 4/5 | 2/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires Bun, a Rust toolchain, and Git LFS to build from source, needs the production app already installed.
OCDX is a tool that lets developers add extensions, sometimes called mods, to a desktop application called OpenCode Desktop, without modifying the original installed program. It works by starting the real, already-installed OpenCode Desktop app through a temporary bootstrap process instead of changing its files directly, then loading independent extension packages on top of it from a dedicated mods folder. Each extension is packaged as a single archive file with the .ocdx extension, similar to a zip file, containing a manifest describing the extension's name and version, some code that runs in the app's interface, and any images or other assets it needs. Developers write extensions using a typed toolkit that gives access to different parts of the OpenCode Desktop interface, such as adding a button to the title bar, along with tools for managing an extension's lifecycle, storing small pieces of settings data that automatically save, and fetching bundled asset files. Installing an extension is as simple as placing its .ocdx file into a mods folder, either inside the installed release or in a per-user application data folder depending on the operating system. There is also a built-in settings page inside the app for installing extensions by dragging and dropping a file, downloading one from a link, and turning extensions on or off without restarting. The readme is direct about trust: extension code runs with real access to OpenCode's internal interface, and an extension can optionally include a separate, more privileged piece of code that runs with the same level of access as the main application itself. Because of this, the documentation advises only installing extensions from sources a person actually trusts. Building this project from source requires a JavaScript runtime called Bun, the Rust programming language toolchain, and Git LFS for downloading example assets, since it needs to compile some native launcher code, not just JavaScript. The readme provides separate build and installation instructions for Windows and macOS, and lists several example extensions included in the repository, such as one that keeps a computer from going to sleep and a playful one referencing an old mobile game.
A typed SDK and mod loader that lets developers add custom extensions to the OpenCode Desktop app without modifying the installed program.
Mainly TypeScript. The stack also includes TypeScript, Rust, Electron.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.