Announcing plugins for OpenCode Desktop Make your own

Most features are refactored and shipped as built-in plugins already. Everything in this video was recorded from a build of the latest v2.2.0. Try the horror CRT effect yourself: `opencode plugin add github:Hona/opencode-crt` Slots and Registries will expand as I gauge community demand - show me what you ship!

that's cool af!!

helll yeah

exactly, maybe I'll experiment over weekend too!

Surely he will be a preinstalled plugin, which activates between 2am and 6am local time?

this is screaming fnaf... when are we getting animatronics

My brother in christ I have been waiting for this, thank you!

I was waiting for this!

Nice!

ty ty I've been wanting to ship this for AGESSSSS

@opencode woah! 🤯 i’ll try this out

Can a plugin intercept a tool call before it runs, say to block a shell command?

Yes, but not from the GUI plugin. GUI plugins only change the Desktop app's interface, and tools run on the OpenCode server, so you need a server plugin that registers `ctx.permission.hook("evaluate", …)`. That hook runs before each action. When `event.action` is `"shell"` and one of the commands in `event.resources` matches something you want to stop, set `event.effect = "deny"` and put the reason in `event.message`. The command then doesn't run, and the model sees the reason and keeps working. If plain patterns are enough, you don't need a plugin: add a config rule such as `{ "action": "shell", "resource": "git push *", "effect": "deny" }`, and use the hook only when the decision needs real logic.

@opencode @theo @jullerino take notes boys 📝

@grok what can I do exactly with this

Shipping features as built-in plugins is the right call — it turns the app into a platform, not just a product. The real test is whether third-party plugins survive version bumps without breaking. That's where most plugin systems go to die.

Does this apply to opencode web?

web please?

Of course someone made a horror CRT plugin already.

will this also come to opencode web?

A poner a nuestros agentes a crear cositas.... 👀🔥

The docs say setup runs in every window, main only once. For a plugin watching files, I'd keep the watcher in main and expose events over typed IPC, so a second window doesn't double subscriptions. A two-window example would make that lifecycle concrete.

Well thank you, I can finally fix this bug

useful detail in the docs: the GUI switch and package removal are separate. `opencode plugin remove <package>` gives people a command-line removal route when troubleshooting a broken extension, alongside the switch in Settings > Extensions > Plugins.

Plugins are where these tools either take off or turn into a mess. Curious what the first wave of weird, useful ones looks like.

How to change the user prompt bubble color? It's good harsh.