1 Beanstalk test farm
mooki edited this page 2026-11-14 16:18:47 +00:00

Beanstalk test farm

Announced and partly built. No agent release to download and no registered agents in the published implementation snapshot. There is nothing to install yet.

The public repository is named Beanstalk. Its README still says “Beanstock” in places. Use the repository name and the Spec, especially Implementation (Nov 14, 2026), for current status.

The farm is intended to let volunteers test Longshot pull requests against main on hardware the author does not own. It is separate from ordinary CI and from the contributor-owned LS workbench.

What is built, and what is not

The implementation section describes a coordinator and a desktop agent named beanstalk-agent. Approvals through /farm commands are pinned to a commit; an old approval does not approve a new push. Sensitive changes need a second maintainer.

The Linux sandbox, queue, leases, statuses, comparison reporting, dashboard and caching are described as implemented. The Windows sandbox is not built, so Windows agents are not offered farm jobs. Central builder artifacts and maintainer-signed approvals are also not implemented. Do not read the earlier design sections as a list of shipped features.

The snapshot says the first full local hardware run is in progress. It does not establish a working volunteer fleet or completed end-to-end coverage.

For now

  1. Read the implementation section before the older design and rollout sections.
  2. Follow the repository and specification for a release and reviewed onboarding instructions. This page intentionally gives no agent installation or execution commands.
  3. If you want to help test now, use the merged human test-request workflow.

Every tester supplies their own game copy. Game files, keys, saves and generated game output must not pass through the farm. A sandbox does not remove GPU-driver risk; future volunteering remains an owner decision.