Infinite PokémonBrowser demo vs local AI game: what changes after download?
The browser demo and local game share the same core rules, but they serve different purposes. The demo proves the play loop immediately; the local build owns the continuing generated world.
The browser demo
The website runs five prepared Willow Valley maps in a Web Worker. Progress autosaves to IndexedDB and can be exported as portable JSON. No account, provider credential, game server, or model call is required.
Because it is finite, the demo has a clear boundary. Battles, catching, healing, shops, interiors, and the tutorial work, but new regions are not generated beyond the prepared valley.
The local game
The downloaded source runs a Node server with SQLite and connects the host’s Codex runtime after explicit consent. It can prepare new regions, retain a larger world history, create checkpoints and branches, and host friends over a LAN or configured HTTPS address.
Only the host connects Codex and supplies generation allowance. Guests share the host’s authoritative world without receiving access to host credentials or administration.
Moving progress between them
The demo exports trainer, team, inventory, tutorial progress, accepted world changes, and continuity history. The local importer validates the file and creates a new isolated preview run; it never overwrites an existing adventure.
Credentials, browser tokens, filesystem paths, and other players are excluded. After import, the host can connect Codex through the normal consent flow and continue beyond the demo boundary.
Continue reading
Editorial basis: written from the project’s implementation, tests, and versioned documentation with assistance from OpenAI Codex. Claims are limited to the current prototype.