How it works
Real PCs, testing Longshot together.
Beanstalk runs Longshot's pull requests on volunteers' PCs, compares them with main, and
posts the numbers back to the pull request. Many GPUs and drivers, no extra work for anyone.
For everyone
What it is
A change that works on one PC can break on another graphics card, Linux, Windows or a Steam Deck. Beanstalk is Longshot's test farm: a team of PCs that build each approved change, play the same scenes before and after it, and report what changed.
For testers
Lend your PC
- Install the app and sign in with git.magicbean.dev.
- Pick your game files and when it may test: when you're away, always, or on a schedule.
- That's it. It tests in the background and keeps itself up to date.
Windows without installing: portable zip.
Needs a PC that plays Longshot, and about 100 GB free (150 GB on Windows).
For developers
Test on hardware you don't have
Comment on your pull request what to test:
@Beanstalk check the water in Zora's Domain on AMD
A BigBean approves it, an AI writes the plan, and matching PCs run it. You get a check per target and one comment
with the numbers against main on the same PC.
Safe by design
- Approved first. Nothing runs until a BigBean approves that exact commit; build changes need two.
- Sandboxed. Pull request code runs with no network and sees only its own folder and your game files, read-only.
- Your files stay home. Only results leave your PC: timings, crashes, hardware model, and pictures of the game when asked.
- You're in charge. Pause any time; a running test hands itself to another PC.
Graphics drivers are large, and no sandbox can rule out a driver bug. If that matters to you, run Beanstalk under a separate user account.