DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to branch a run from a checkpoint to try another path with Infinite Pokemon

Create a checkpoint, then branch from an earlier point into a separate world.

Who it is forA player who wants to test a different choice without losing the current adventure.

The problemA player who made a risky choice wants to compare outcomes without overwriting progress in the original run.

The outcomeThe player has a separate branch with its own world database and generation context, while the original run stays unchanged.

What you need first

  • Node.js 22.13 or newer
  • A terminal in the repository folder
  • Codex sign-in and generation allowance for full single-player or hosted play (the browser demo and the finite tutorial preview do not need it)

Steps

  1. Open the save options in the game and create a checkpoint at the current point.
  2. Keep playing the original run for a while.
  3. Return to the earlier checkpoint and choose to branch from it.
  4. Explore the new branch and confirm that later events from the original run are not present.

Prompt for your agent

In Infinite Pokémon, create a checkpoint in a run, branch from it, and report whether the branch has its own world database and whether later events from the original run appear in it. Note any generation status shown for unfinished destinations.

Caveat. Each branch generates its own content, so exploring a branch uses Codex allowance again even though its history starts from the checkpoint.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page