OpenCode v1.14.33 fixes custom-agent loading and shifts plugins to on-demand installs

• OpenCode shipped two same-day patch releases, and LLMpsycho's v1.14.32 post plus LLMpsycho's v1.14.33 post show the focus was bug cleanup, not new surface area.
• The first patch, according to LLMpsycho's v1.14.32 post and the v1.14.32 release notes, fixed broken shell editing, HTTP workspace context loss, OpenAPI schema mismatches, and image attachment fallback behavior.
• The second patch, per LLMpsycho's v1.14.33 post and the v1.14.33 release notes, fixed custom agents in plugins not loading and restored an InstanceBootstrap init parameter for non-Efficient environments.
• steipete and vincent_koc both said the heavier npm install and slowness complaints were addressed by moving most extras into extensions and ripping out roughly 20,000 lines.
• Separate from the patches, opencode's Kimi 2.6 status post said OpenCode Go was still seeing intermittent provider issues with Kimi 2.6.

You can read the v1.14.32 release, the v1.14.33 release, and the plugin docs back to back. The docs say npm plugins are auto-installed with Bun at startup and cached in ~/.cache/opencode/node_modules/, which makes the extension split more concrete than the tweets alone. The weirdly useful detail is that the second patch landed only hours after the first, which reads like a cleanup pass on a cleanup pass.

The first patch was a grab bag of sharp-edged fixes that hit core editing and workspace flows.

The official changelog lists five notable items:

• Shell mode became editable again, including backspace and cursor movement.
• HTTP API workspace adapters stopped losing instance context during create, sync, and routing.
• Experimental workspace creation stopped dropping extra data.
• OpenAPI parameter schemas were corrected so generated clients match the public API.
• Unsupported image formats now fall back to text reads instead of being sent as image attachments.

The same release also removed prompts for agents using the global temp directory, a small change that matters more in agent loops than it does in release notes.

The follow-up patch was narrower. The release notes say it fixed custom agents inside plugins not loading, restored InstanceBootstrap for non-Efficient setups, removed a stale Nix packages filter, and refreshed CLI docs.

That custom-agent fix is the one with the most blast radius. OpenCode's plugin docs say plugins can come from local directories or npm packages, and that npm plugins are installed automatically with Bun at startup. When agent-loading breaks there, it hits the extensibility story, not just one command path.

The more interesting part of the story came from maintainers explaining why the patch train was so messy.

steipete said the release fixed dependency issues and slowness for some npm installs, and that "almost everything" moved into extensions so the package is leaner. vincent_koc put a number on it, saying the team ripped out about 20,000 lines of code and shifted many plugins to download only when needed during install.

That lines up with the current plugin documentation, which describes npm packages as a startup-installed layer rather than something that has to live in the base package. The result is a smaller core and more moving parts in the extension path, which also helps explain why plugin bugs were front and center in v1.14.33.

Not everything was fixed by the release pair. In a separate status post, opencode said OpenCode Go was still seeing intermittent issues with Kimi 2.6 and that the team was working with providers on the problem.

That matters because it places at least some recent breakage outside the local package itself. The release notes were about client and plugin mechanics, while the Kimi post points at upstream model-serving instability still leaking into the product after the patches landed.