Skip to content

Offer online play before local setup and acknowledge experimental models - #319

Draft
MoonlightByte wants to merge 1 commit into
mainfrom
feat/local-launch-consent-20260907
Draft

MoonlightByte wants to merge 1 commit into
mainfrom
feat/local-launch-consent-20260907

Conversation

@MoonlightByte

Copy link
Copy Markdown
Owner

Windows users previously began dependency setup without an online-play option, and local/custom models could be activated without acknowledging their experimental behavior.

This adds a tracked launch_game.bat and an online/local choice before the installer checks dependencies. Explicit launch arguments and NEQ_LOCAL_ONLY=1 preserve automated local startup. Installers running inside a checkout use that checkout and retain its launcher.

React and legacy settings request explicit, versioned local-model acknowledgment. Backend activation, endpoint saves/probes and client creation enforce it. Existing local selections remain selected without silently switching to a paid cloud provider. Headless users have a separate acknowledgment command; only version/time are recorded locally.

Validation: 32 Python provider/consent tests, 6 Windows launcher checks, 13 React settings tests, TypeScript checking, a Vite build and 3 Chromium provider-flow tests pass. Browser and API checks use synthetic/local providers; no paid AI calls. Frontend validation reused installed Node 24 dependencies; manifests and lockfile are unchanged.

This draft does not enable hosted BYOK or change game request parallelism. Online copy describes limited alpha access and links to the product page for availability.

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