Skip to content

fix(tui): align spinner colors with OpenCode 2.0.15 theme types - #2

Merged
P-Theo merged 2 commits into
mainfrom
fix/opencode-2-0-15-theme-typing
Sep 23, 2026
Merged

P-Theo merged 2 commits into
mainfrom
fix/opencode-2-0-15-theme-typing

Conversation

@P-Theo

@P-Theo P-Theo commented Sep 23, 2026

Copy link
Copy Markdown
Owner

OpenCode 2.0.15 publicly exposes only three theme hues. This pins the theme types alongside the plugin SDK so TypeScript cannot silently treat the optional theme peer as any, and changes the spinner to use hex or public semantic colors before falling back to the categorical palette. Custom named agent colors, particularly on older supported hosts, may no longer exactly match the agent. The runtime floor stays at 2.0.11.

Validation: npm ci --ignore-scripts, production npm audit, the compatibility check (including a mismatched theme pin), lint, typecheck, 604 tests, build, and packed-artifact import with OpenTUI 0.5.10 and Solid 1.9.15 passed locally. The official OpenCode v2.0.15 release tag exists.

@opencode/theme is an optional peer, so its missing types masked the invalid dynamic hue lookup under skipLibCheck. Pin it alongside @opencode/plugin, use only public semantic hues, and retain the categorical fallback without raising the runtime compatibility floor.
@P-Theo
P-Theo merged commit 3506cae into main Sep 23, 2026
4 checks passed
@P-Theo
P-Theo deleted the fix/opencode-2-0-15-theme-typing branch September 23, 2026 11:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant