fix: restore the V2 TUI sidebar and palette command

[Manaf941]

Summary

On current OpenCode 2 previews the V2 TUI integration registers nothing: no goal sidebar, and no Goal entry in the ctrl+p palette. The server side (tools, /goal, persistence) is unaffected, so the plugin looks healthy while its whole TUI surface is dead.

There are three independent breakages, and the first one hides the other two.

1. ui.slot takes a claim object, and the positional form was removed. Bisecting the published @opencode-ai/plugin declarations (dist/tui/context.d.ts) pins the change to 0.0.0-next-17226:

preview	ui.slot
0.0.0-next-17055 … 0.0.0-next-17224	<Name extends SlotName>(name: Name, render: Slot<Name>) => () => void
0.0.0-next-17226 and later	(claim: SlotClaim) => () => void, carrying render plus exactly one of prepend/append/before/after/replace

No overload was retained. In the 0.0.0-next-17403 host:

slot(K) {
  let C = `slot#${F++}`,
      X = ["prepend","append","before","after","replace"].filter(W => K[W] !== void 0)
  if (X.length !== 1) throw Error("Slot claim requires exactly one placement key")
  ...
}

So slot("sidebar.content", render) throws, setupTuiV2 aborts on its first statement, and the app slot — which mounts the keymap layer — is never reached. One throw removes both the sidebar and the palette command.

2. The sidebar read theme keys that do not exist. It used theme.text, theme.textMuted and theme.primary, copied from the V1 sidebar. Both preview generations expose a nested theme (theme.text.default, theme.text.subdued, theme.text.feedback.success.default, theme.text.action.primary): the last two flat keys are undefined and theme.text is a colour group, not a colour. This was already wrong on 0.0.0-next-17055 (theme.primary does not occur in that binary at all), so it never worked — it was simply unreachable behind breakage 1.

3. The keymap layer never opted into the global mode. goal.show sets palette: true but the layer omitted mode, which the plugin contract has documented since 0.0.0-next-17055 ("Limits the layer to one OpenCode input mode. Use global to opt out; defaults to base."). Without it the layer registers but the palette never lists the command; every host built-in exposing a palette command declares mode: "global".

Related issue

None open — filed directly from a live V2 debugging session.

Changes

• src/tui.ts: add registerSlotV2(), which branches on context.ui.slot.length — one parameter means the claim-object host, two means the pre-17226 host. Both shipped generations were checked directly: 0.0.0-next-17403 implements slot(K) (arity 1) and 0.0.0-next-17055 implements slot(Q, X) (arity 2). It also tolerates a host that returns no disposer.
• src/tui.ts: add themeColorV2() + goalColorsV2(), resolving the first candidate theme path that exists and descending into a default leaf when the node is a colour group. Nested paths are tried first, legacy flat keys remain as fallbacks, so one path serves both generations. element() already skips undefined props, so an unresolved colour degrades to the inherited default rather than throwing.
• src/tui.ts: setupTuiV2() registers both slots through the adapter; GoalKeymapLayerV2() declares mode: "global".
• test/tui-v2.test.ts: update the mock to the current host contract (arity-1 slot, nested theme) and add coverage for the claim-object host, the positional fallback, a host returning no disposer, themeColorV2 across nested/grouped/flat themes, and the mode: "global" assertion.

Only V2 code paths are touched: the V1 integration still uses api.theme.current with flat keys and is unchanged.

The old mock encoded the outdated contract (slot(name, render), { text, textMuted, primary }), which is why the suite stayed green against an API that no longer exists. Reverting just the call shape in registerSlotV2 now fails 8 tests in that file, where previously it failed none.

Verification

Gates:

bun run lint        clean
bun run typecheck   clean
bun test            98 pass / 0 fail (370 assertions, 6 files)
bun run build       dist/server.js 95.30 KB
bun run pack:dry-run  ships dist, src/tui.ts, LICENSE, README

End to end against opencode2 0.0.0-next-17403 (claim-object host), plugin loaded from this working copy, isolated OPENCODE_DB and OPENCODE_GOAL_STATE_PATH, driven in tmux:

• sidebar renders Goal / Status: active / Time: … / Tokens: … / Auto-continues: … / Goal set. / objective, and Time: ticks while the goal is active
• palette lists Goal; selecting it opens the dialog with the objective plus Refresh / History / Pause / Clear, and Refresh prompts the agent
• /goal pause → Status: paused + Stop: paused; /goal complete … → Goal achieved (1:13), exercising the text.feedback.success group descent
• state survives a restart with -c; invoking the command with no session open toasts "Open a session before viewing goal state." instead of crashing
• exactly one Goal block throughout, across four setup activations during one boot

Colour resolution confirmed byte-exact by matching the pane's ANSI codes to the host theme: header 38;2;205;214;244 = text.default, detail lines 38;2;147;153;178 = text.subdued, Goal achieved 38;2;166;227;161 = text.feedback.success.default.

Re-run against opencode2 0.0.0-next-17055 (positional host) in a pinned linux/arm64 container, configured the way that era expects — ~/.config/opencode/tui.json with a relative plugin path, since cli.json only appears with the 17403-era migration. The adapter reported slotArity: 2, took the positional branch, setup returned a cleanup function, the palette listed Goal, and /goal … rendered the sidebar. (The preview CLI silently self-updates; OPENCODE_DISABLE_AUTOUPDATE=1 is needed to keep an old preview under test.)

host	slot arity	branch taken	palette	sidebar
0.0.0-next-17403	1	claim object	yes	yes
0.0.0-next-17055	2	positional	yes	yes

Checklist

• bun test passes (new behavior has regression coverage)
• bun run lint passes
• bun run typecheck passes
• bun run build passes and dist/server.js is committed if server code changed — build is clean; src/server.ts and its imports are untouched (src/server.ts does not import src/tui.ts) and the rebuilt bundle is byte-identical, so there is no dist change to commit
• README/docs updated if behavior or options changed — no options or documented behavior changed; the README already lists TUI sidebar/palette integration as V2-supported, which this restores

Notes for review

• The arity check is a heuristic. It is correct on both shipped generations, but a host that wrapped slot variadically would defeat it, and guessing the claim object on a legacy host fails silently whereas the reverse throws loudly. try { slot(claim) } catch { slot(name, render) } would key off the observable throw instead — happy to switch if you prefer.
• goalColorsV2 is evaluated in the component body rather than inside the render closure, so a runtime theme switch will not restyle an open sidebar. That matches the previous const theme = api.theme behaviour, so it is not a regression, but the host's built-ins read theme values inside their render effects and this could follow suit.
• registerSlotV2 and themeColorV2 are exported for tests; both are reachable through setupTuiV2 with two mock variants if you would rather not widen the published surface of ./tui.
• The cast on context.ui.slot is needed because the pinned @opencode-ai/plugin-v2 (npm:@opencode-ai/plugin@0.0.0-next-17055) still declares the positional signature. Bumping that pin past 0.0.0-next-17226 would let the claim-object call type-check directly.

AI attribution

Written with the OpenCode 2 agent harness (opencode2) using Anthropic Claude Opus 5. All verification above — unit gates, both live host runs, and the type-declaration bisection — was executed, and the diff was reviewed by the submitter before opening this PR.

[Manaf941]

Sorry for the slop PR. Reviewed the code before sending and tested manually, and it now brings back the goal interface.