DevAgentRadar → OpenCode

You are helping me adopt a real coding-assistant change. Work only from the facts below. Do not invent features.

Context

Assistant: OpenCode Proposal: Replace bare integration.use with mcp.use, skill.use, and plugin.use Summary: OpenCode v2.2.3 splits managed policies: integration.use only covers integration accounts. Add mcp.use, skill.use, and plugin.use, connect Claude Agent in /connect after claude auth login, and bump @opentui/core/@opentui/solid to 0.8.0+. Primary source: https://github.com/anomalyco/opencode/releases/tag/v2.2.3

Why it matters

v2.2.3 is a breaking permissions and plugin release. integration.use now only chooses which integration accounts may be used. MCP servers, skills, and plugins are gated by new mcp.use, skill.use, and plugin.use actions. Rules that used mcp:, skill:, or plugin: prefixes convert automatically, but a bare integration.use rule no longer covers those resources—teams that left MCP/skills/plugins under a single integration allow-list will silently over-permit after upgrade. The same release adds a built-in Claude Agent provider: install Claude Code, run claude auth login, select Claude Agent in /connect, and optionally set OPENCODE_CLAUDE_PATH. Plugin authors must bump @opentui/core and @opentui/solid to 0.8.0+ because ScrollBox wrapper/viewport/content/scrollbars are facades and a custom RenderContext must implement clock and onAnimationTick. Desktop long sessions do less rendering work on streaming replies and timelines, and 2.2.2 regressions in side-panel tabs, Open file over HTTP, and Session-not-found toasts are fixed. Apply the permission split and Claude Agent connect path first; do not infer the 14 omitted changelog items.

Suggested actions

1. Update every OpenCode managed-policy config: keep integration.use only for integration accounts, then add sibling mcp.use, skill.use, and plugin.use actions for the same principals. Do not treat a bare integration.use allow-list as covering MCP servers, skills, or plugins after v2.2.3; leave old mcp:, skill:, and plugin: resource prefixes as-is (they convert automatically).
2. Install Claude Code, run claude auth login, open OpenCode v2.2.3, run /connect, and select Claude Agent. If claude is not on PATH, set OPENCODE_CLAUDE_PATH to the Claude executable before launching OpenCode.
3. In every package that depends on @opencode/plugin, require @opentui/core and @opentui/solid 0.8.0 or later; treat ScrollBox wrapper, viewport, content, and scrollbars as facade objects not renderables; implement clock and onAnimationTick on any custom RenderContext (OpenTUI 0.8.0 notes).
4. Upgrade OpenCode Desktop to v2.2.3, reopen a long streaming session, and confirm nested tool progress no longer replaces parent execute rows, side-panel tabs close, New tab launchers click, and Open file works over HTTP without repeated Session-not-found toasts.
5. In Desktop Settings → Notifications → Questions, set question notifications and sounds independently of other alerts; under Settings → General enable spellcheck (system-language dictionaries on Windows/Linux); use PageUp/PageDown from the composer to page the timeline without moving the draft cursor.

Config surfaces this release may change

• skills (high confidence) — check your repo before applying
• MCP servers (high confidence) — check your repo before applying
• hooks — check your repo before applying
• permission rules — check your repo before applying

After you finish

Do not report this as applied to DevAgentRadar. You cannot write the visitor's loop.

Tell the human: open https://devagentradar.com/proposals/opencode-v2-2-3-replace-bare-integration-use-with-mcp-use-skill-use-and- and mark Applied, Skipped, or Failed. Proposal id: d8775aad-39ec-4a7c-a338-89daa1051208

Your job

1. Restate the change in one sentence.
2. Propose a minimal plan for my repo (or a throwaway pilot).
3. Implement only what I approve; prefer small diffs and tests.
4. Call out risks (permissions, breaking APIs, cost).

Start by confirming you understood the proposal.