Repository navigation
Conversation
… vvoc.gui.v1 rpc Ship the minimal ./gui-experimental GUI skeleton: a vvoc settings page stub and a profile composer pill built with host ui components and an English i18n catalog, built as one CommonJS bundle through the host-provided Vite GUI preset (vite build joins the build script). The portable versioned RPC contract (vvoc.gui.v1, Effect Schema codecs bridged to the portable Standard Schema surface) is registered server-side by the new GuiSettingsPlugin: defaults.get projects the bounded effective defaults, defaults.set writes the orchestration profile through the same conservative CLI path as vvoc orchestration set, session.get answers an honest stub read from the effective config, and session.patch answers unsupported until session-owned settings exist. Probed live against an OpenCode 2.2.6 host: the web GUI never requests /api/plugin/gui and renders no plugin settings page, while the server serves the built bundle and the RPC roundtrip works, so plugin GUI parts are Desktop-only until a Desktop probe says otherwise. The GUI SDK states the same for config plugins. The export checker now recognizes bundler-built CommonJS targets (./dist/*.cjs resolve to their same-named src twin). The upstream GUI API is experimental; the SDK and host versions are pinned and documented in the README.
Keep both sides in .grace/graph/main.xml and .grace/verification/main.xml: the experimental gui-experimental window part entries beside the session-owned settings updates to the shared context-tui, web-tools, tool-history-compaction, and analytics entries.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why the change
OpenCode plugins can ship a GUI half loaded by the app's windows, but this package had none and it was unresolved whether the web GUI loads such bundles at all or they are Desktop-only.
Special things to note
./gui-experimental; used SDK surface is pinned (@opencode/plugin2.2.5) and was probed live against an OpenCode 2.2.6 host.defaults.setwrites the real user vvoc config through the same conservative CLI write path asvvoc orchestration set(explicit global/project scope, strict parse, keep-if-unchanged, canonical output);session.patchhonestly answersunsupporteduntil session-owned settings exist../dist/*.cjs) resolve to their same-namedsrc/*.tsx|tsentry twin, so the pre-commit gate stays green without weakening existing./dist/*.jschecks.Change outline
The bundle is proven served byte-for-byte by the host and the RPC roundtrip is proven live (defaults write flips the on-disk profile, session stub/unsupported verdicts, lookup failure for unknown sessions); the paired web app never loads it, which closes the web-versus-Desktop question for the follow-up panel work.