You gave the assistant the Diamond Snake link and it never opened it. It named the game from the URL, said there was a gameplay recording when there wasn't one, and set up the video with no game. Now the studio opens the link in its own browser (Browser Use), plays the game, and uses the real thing in videos. The assistant looks at it before it writes a word about the game.
Already done on the live studio: Diamond Snake is in Our games, captured from its link (logo, screens, two real rounds), and your Diamond Snake video's game shot now shows that gameplay.
This is a real capture, made by the studio on this branch. The logo is the game's own file. The gameplay is two rounds played by the studio's browser: it ate a gem, reached 1.25×, cashed out "YOU WIN ×1.25", and started again. On the server the whole capture took 82 s.
Every card click reloaded the whole page, and the page pulled about 14 MB of start frames: 2 MB PNGs straight from the image model, with caching off, downloaded again on every click and on every live refresh. Now pictures come as small previews (about 110 KB instead of 2 MB), the browser keeps what it has loaded, and a card opens its shot panel in place, in 0.11 s locally. Previous/next, Esc and Back work the same way, and the full picture is one click away.
A box at the top of every storyboard, and the feedback field on the Videos page. Write what should change, e.g. "make her blonder, a stronger first second". The studio's Claude applies it to this video, and the studio remakes what that changes: the pictures, and once there are clips, the clips of the changed shots (new start frames where those changed, their lines said again). That's up to $3 at a time; anything bigger waits for your Redo button. The box shows the change as it's made, then what Claude says it changed. The note is also kept as feedback on the recipe.
| Before | After | |
|---|---|---|
| Your link | Not opened. The name "Diamond Snake" was guessed from the URL. | Opened in the studio's browser. Its title, words, logo, screens and rounds come back in about a minute. |
| The game's shots | Waited for an upload. The assistant said a recording existed when it didn't. | Filled with the real gameplay as soon as the video is made, or when the capture lands. |
| Your Diamond Snake video | Set up with no game, so it could never get the game's recordings. | Done on live: linked to Diamond Snake, and its game shot shows the real gameplay. |
| Opening a shot | A full page reload that pulled about 14 MB of pictures each time. | Opens in place. Small previews (about 110 KB each), kept by the browser. |
| Feedback on a video | Stored with the video and its recipe; nothing changed. | Claude changes the video, and the pictures and clips it changes are remade, live on the page. |
| browser-use / video-use | Only on my machine. The studio couldn't use either. | Both installed on the studio's server. video-use reads speech with local Whisper, so it needs no ElevenLabs key. |
The recipes are written for coin pushers. Street Booth's lines say "Drop one coin and watch the wall move", but Diamond Snake is a snake crash game. Now that the page's own words reach the assistant ("Every diamond the snake eats raises your multiplier. But any of them can crash the snake"), it can rewrite the lines for the real game. Ask it to, or we can make a recipe for crash games.
Pages that need a login aren't opened. For those, record the game on a phone and drop the clip on the game's page, as before.
The studio plays like a bot. It sweeps the board with the arrows, taps the middle of canvas games and cashes out after a few seconds. That's good enough to show the game moving and a win; for a hero moment, film a real round.