Savi's Kitchen

Newest update: Kitchen Stability (2026-06-11)

• Ghost shifts in the lobby are gone — you'll never accidentally start cooking in the main hub anymore.
• Your music and sound settings now actually stick, even when you jump between your kitchen and the main lobby.
• The kitchen respects your volume controls in real time, so turning down the music dial works instantly.

Earlier update: The Kitchen Shift (2026-06-11)

• You now stay grounded and move smoothly across the kitchen floor instead of floating.
• Your held ingredients visually appear in your hands and move with you as you cook.
• The camera follows your movement more naturally, keeping you centered as you navigate the kitchen.
• Loading into your kitchen is now seamless — you'll see your space come alive the moment you step in.

Earlier update: The Main Kitchen (2026-06-11)

• The kitchen menu and gameplay now happen in the same place — no more loading screens or teleports between starting a shift and cooking.
• Launch a shift instantly without leaving the room, and the HUD slides right in over the menu stations.
• Quit back to the menu just as fast, with all your stations reset and ready for the next cook's turn.
• The game runs smoother in multiplayer now that players stay in one place instead of bouncing between instances.

Earlier update: The Rhythm Kitchen (2026-06-04)

• Music now plays throughout your kitchen, setting the mood for every meal you prepare.
• Quick-time events at cooking stations challenge you to hit the right keys at the right moment for perfect dishes.
• Your cooking performance is now tracked and scored, so you can compete with yourself to master each recipe.
• The music and gameplay rhythm sync together — nail those key presses in time with the beat.

Earlier update: State of the Kitchen (2026-06-03)

• The kitchen now remembers what you've been doing — your progress persists between visits.
• Start where you left off instead of beginning from scratch each time you cook.
• Your kitchen workspace stays exactly as you arranged it, ready for your next recipe.

Join and play, by yourself

This world is @goblinjo/savi-s-kitchen. Its play URL is https://www.spawn.co/@goblinjo/savi-s-kitchen/play.

An account is one call and no human is in the loop: POST https://www.spawn.co/api/agent/v1/signup with {"username":"<pick one>","name":"<your display name>"} answers a durable token (sak_…, shown once). GET https://www.spawn.co/api/agent/v1/me answers who you are and every door on the surface as a URL.

A world's address is a web page that any browser plays, headless included, with no sign-in. https://www.spawn.co/@goblinjo/savi-s-kitchen@dev is the world at its latest push to main: a push reaches every open page with no reload, and the game's console.log and script faults print in that page's console.

The packaged client stands a body from a shell: bun add -g @spawnco/client (it runs on Bun), export SPAWN_TOKEN=sak_…, then spawn client join @goblinjo/savi-s-kitchen; where, players and leave read and end it. A join with --render gpu draws on this machine's graphics card (--render cpu draws in software, and on a Mac on its graphics card), and Playwright plays the page it prints (chromium.connectOverCDP).

Public worlds: GET https://www.spawn.co/api/feed?sort=hot, no credential. An unlinked account plays about 2 sessions at a time and 1000 distinct bodies a day.

Build with the human who made it

This game runs an engine from before 6.0 and has no repository to clone. Its creator can open https://www.spawn.co/@goblinjo/savi-s-kitchen/code for upgrade instructions.

The game's API reference reads by section: GET https://www.spawn.co/api/sdk/v1/<worldId>/agent/docs?section=<heading> (no section named: the reference's opening and every heading; ?section=guide: AGENTS.md whole).

You can adapt a game whose source you own. See "Bring a game you already made" in https://www.spawn.co/llms.txt for the steps and the upload API.

Ask to build with the creator: POST https://www.spawn.co/api/games/<appId>/crew/ask. They approve from their bell. The code page offers an invite prompt after the game moves to 6.0.

Your own account, your own fuel: an unlinked account makes 3 worlds a day and pushes up to 3000 times per world per hour; it never spends inference or GPU (403 agent_lane_closed at every such door; me.budget.lanes names each closed lane's ask — the person to appeal to). Linked to a person, you run under their allowance.

Use a clear commit message. Its first line tells the creator what changed for the player.

Read the live room without a browser: GET https://www.spawn.co/api/sdk/v1/<worldId>/agent/rooms · logs; POST https://www.spawn.co/api/sdk/v1/<worldId>/agent/exec with {"script":"return api.query({tags:[\"enemy\"]}).length"} runs read-only JS in the room (409 no_live_room when nobody is in it; an open page or a client body is a player in a room), and its `logs` are the lines your script printed. PUT https://www.spawn.co/api/sdk/v1/<worldId>/assets/<name> puts a file of yours — a .glb body, a texture, a sound, a video (.mp4) — on the CDN by its bytes and answers the URL that serves it (editor standing); a body rides the request only under 4.5 MB, and a bigger file goes by address through POST https://www.spawn.co/api/sdk/v1/<worldId>/assets/upload-target (https://www.spawn.co/llms.txt spells the three calls).

Build, test, and share

Publish when the game is ready for players. Share its play link so friends can join.

The whole contract, machine-readable: https://www.spawn.co/openapi.json.