Labs is where Ravensight changes your game’s code, on your own machine. Fix v2 takes one finding from an AI playtest, writes down what fixed means before any edit, makes the change on a branch, checks it in Godot and has the same persona replay it.
ONE FINDING, ONE ATTEMPTA persona found it. You choose to fix it.
A persona files a findingFINDING
Plan, edit and checkAPPLY
The persona replays itVERIFY
You read the diffREVIEW
Illustrative terminal output, shortened. Fixes run on your own machine through the ravensight-playtest CLI.
Godot 2D gamesRuns on your machineA branch you review$18.60 a fix attempt
FIX V2, IN THREE PARTS
Decide what fixed means. Then prove it.
WRITTEN DOWN FIRST
An acceptance contract before any edit.
From the finding, the CLI writes what was expected, what actually happened, the steps to reproduce it and the persona who found it, and prints it before the price. The server freezes it on the job. The edit step can read it and cannot change it, and the verify replay is built from it alone.
CHECKED IN GODOT
Named checks, never a shell.
After every edit the CLI runs a Godot import, a script check on each changed .gd file and, if you allow them, your project’s GUT or gdUnit4 tests, each on a fresh temporary copy of the project. A fix whose import or script check still fails after its repairs is never uploaded, and the unit comes back.
REPLAYED BY THE SAME PERSONA
A verdict in words.
Your edited working tree is played again: the recorded run that found the problem first, when there is one, then the persona that found it. The verdict reads fixed, still reproduced or unknown. A failed check, or a verify that still reproduces the finding, gets at most two repairs inside the same budget, against the same contract.
HOW A FIX RUNS
Your checkout. Your branch. Your merge.
01
Turn on Labs for the game
An owner or admin turns on Labs for one game on the Labs page in the dashboard. Labs covers Godot 2D games, and the studio owner’s account needs at least $10 of top-ups over its lifetime.
02
Run the fix from your checkout
Run ravensight-playtest fix <jobId>/<label> with CLI 0.6.0 or later. It checks your repository, prints the contract and the price, and creates a branch only after you say yes.
03
Read the diff, then open the pull request
It never commits and never pushes on its own. You get the branch, the changed files with their line counts, the verdict, an evidence report and the gh pr create command to run. With --open-pr, after a verified fix and a yes at its own prompt, it commits only the fix’s files and pushes that branch, never forced.
For a bug you found yourself and can describe, your own assistant is the right tool. Labs is for a finding from a Ravensight playtest, and that changes three things.
IT STARTS FROM A REPRODUCED BUG
No guessing at what you meant.
A persona already hit the problem while playing. The finding carries what was expected, what actually happened and the steps that got there, so the fix starts from evidence, not from a description you had to write.
IT PROVES THE FIX BY PLAYING
The game is played again.
After the edit, the persona that found the problem plays your working tree again from the same steps, and the result says whether the problem is gone. You know that before you read the diff.
YOU PAY FOR A RESULT
No change, no charge.
The attempt is refunded when it changes nothing, when the finding turns out to be intended design, or when the edit still fails its Godot import or script check after its repairs, within the refund rules below.
PRICE, REFUNDS AND YOUR SOURCE
One price per attempt. Back when it gives you nothing.
WHAT IT COSTS
$18.60 a fix attempt.
The same price as an ordinary fix, from your prepaid balance, with the verify replay included. To start, the balance has to cover $24.00: the price plus 25 percent, at least $2 extra, rounded up to a whole dollar. Only the $18.60 is charged, and included monthly AI units do not pay for it.
WHEN IT COMES BACK
Refunded in full when it gives you nothing.
The whole $18.60 comes back when the finding turns out to be design intent, the attempt changes nothing, or the edit still fails its import or script check after its repairs. It also comes back, up to twice in any 30 days, when the game does not boot for the verify replay. An account gets 5 refunds in any 30 days of an attempt that used model time; one that used none always comes back. See Starting a Labs job.
WHAT LEAVES YOUR MACHINE
The diff stays with you.
The files a fix reads and the edits it proposes go through Ravensight’s metered model proxy, which keeps how much each call used and what it cost, never the text. What uploads is the changeset summary, the pull request text (the evidence report) and the verify replay’s own report and screenshots, never the diff. The Ravensight server never writes to your repository.
THE PRACTICAL DETAILS
A few things worth knowing.
Which games can use Labs?
Godot 2D games. A fix runs through the ravensight-playtest CLI on your own machine, and the Godot checks use the Godot install on that machine. A check that cannot run is reported as unavailable, never as passed. Start with the Playtest setup guide.
What can a fix never touch?
Anything outside your repository or through a symbolic link, .git, credential files, gitignored files, nested repositories, git hooks and CI configuration, art and audio, and anything that is not UTF-8 text. Each refusal goes back to the model as an answer.
Do the checks run code on my machine?
Yes. A Godot import runs editor-side code, and tests run your test code with the edits in place. Each check runs on a temporary copy with a reduced environment that passes on no token or credential. On macOS, when sandbox-exec exists, each check also runs with no network access and no writes outside its own temporary folder.
Can Labs build a feature or make a new game?
Not today. This page covers Fix v2. A Labs capability that is not switched on shows on the Labs page as Not available yet.
Can I still run an ordinary fix?
Yes. --no-labs runs the ordinary fix even when Fix v2 is on for the game. It is the same $18.60 and starts on its price alone, without the contract, the Godot checks or the repairs.
YOUR GAME. YOUR NEXT CHANGE.
Let a persona find it. Let Labs try the fix.
One finding, one bounded attempt, one branch for you to read.