Repository navigation
feat(ui): refine installer and agent capability settings - #3037
Merged
Merged
Conversation
GCWing
force-pushed
the
gcwing/refine-installer-agent-settings
branch
from
September 15, 2026 02:55
3c24ee7 to
c2cfc60
Compare
GCWing
force-pushed
the
gcwing/refine-installer-agent-settings
branch
from
September 15, 2026 03:09
c2cfc60 to
3d33460
Compare
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.
Summary
--previewmode that rejects installer mutations, process launches, and model requests; remove simulated installation progress.Type and Areas
Type: UI/UX, refactor, bug fix, regression tests.
Areas: Installer React/Tauri, Web UI Agent and model settings, shared design system, mobile web, i18n, installer docs.
Motivation / Impact
The installer now uses the same public control contracts as the app. Agent capability editing exposes explicit selected states and a save hint, while summaries distinguish enabled Skills from those available at runtime. Model API key fields retain one visibility control. Mobile workspace and device tools satisfy the repository's typography and shared-control checks, and account regression fixtures use a stable language across host systems.
Verification
Passed locally:
pnpm run fmt:rspnpm run design-system:checkpnpm run check:web(Appearance, typography, all 23 theme-color surfaces, visual governance contracts, and TypeScript)pnpm run i18n:auditpnpm --dir src/web-ui run icons:checkpnpm --dir OpenBitFun-Installer exec tsc --noEmitcargo check --manifest-path OpenBitFun-Installer/src-tauri/Cargo.tomlcargo test --manifest-path OpenBitFun-Installer/src-tauri/Cargo.toml --lib preview::tests(2 passed)pnpm --dir src/mobile-web exec tsc --noEmitpnpm --dir src/mobile-web run test:ui-components(10 passed)pnpm --dir src/mobile-web run test:account-browser(16 passed)git diff --checknode scripts/check-git-object-sizes.mjs --base origin/main --head HEADpnpm run motion:auditcompleted; its existing PortForwardDialog inventory item is outside this change. GitHub CI must pass on the final PR head before merge.Reviewer Notes
AI-assisted; testing level: focused local checks, with full CI required before merge. The browser account suite was run to reproduce and fix the CI failure using disposable Chrome profiles and the existing synthetic Relay fixture. It validates account behavior, including cross-tab sign-out and legacy records.
Visual acceptance, real installation/uninstallation, and local packaging were not performed. No mock or browser-controlled visual verification was used. Live remote workspace, remote control, Peer Device Mode, and Detached Dispatch were not exercised; fixture account tests do not establish live-host compatibility. Existing product command and configuration paths are retained. The optional frontend
previewOnlyfield defaults to normal behavior when absent.Checklist