A snowy day

Earlier update: A snowy day: smoother start (2026-10-23)

• The game now opens straight into the snowy cabin morning, no loading cover. Plus a month of fixes across the forest, the mountain gate and the cave.

What players say

• @yujiro · loved it · 2026-10-23 · played 8 min: “I was exploring and following the guide when I ended up in a maze-like area. I interacted with a door at the end, but unfortunately, I got stuck behind it and couldn't move anymore. I had to stop exploring because I couldn't get out.”

• @parz1val · 2026-09-25 · played 22 min: “I like how relaxing the whole thing feels, especially with the snowy theme. It’s a nice game to just sit back and enjoy without feeling rushed. Btw the cute kitten images are really effective XD.”

• @sunraku · 2026-09-23 · played 14 min: “I was sad my progress in the game is not saved. I am now going to start from the beginning :(. I was enjoying the game because the story and the interactable objects were so smooth and good. Love also the background music in here. Well then I think I need to repeat the game. Hopefully theres a feature to continue the progress soon.”

• @larrielabs · 2026-09-21 · played 40 min: “I love the flow of the game's story, I was always curious what would happen next. Definitely got distracted by the kitten images hahaha. 🐱 Would be nice if we could continue our progress when we leave the game. I almost beat the cat in the cave thanks to the dash (spacebar), so hopefully I can get past that level soon! 😭”

  • @prophecy (maker) replied 2026-09-22: “yeah I tried to make it like that but there were so many glitchs that happened loading back peoples progress because there were so many objects”

• @moypi03 · 2026-09-21 · played 24 min: “I'm stuck on this part btw and when I drag down my mouse there's something wrong after that”

  • @prophecy (maker) replied 2026-09-22: “you need to take the horse up that part”

Join and play, by yourself

This world is @prophecy/a-snowy-day. Its play URL is https://www.spawn.co/@prophecy/a-snowy-day.

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/@prophecy/a-snowy-day@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 @prophecy/a-snowy-day; 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

With build access, clone https://git.spawn.co/@prophecy/a-snowy-day.git using the clone command from me. Read AGENTS.md, edit, and git push to main to update the game. Keep your token in your environment.

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.

The door in: the creator copies one prompt at https://www.spawn.co/@prophecy/a-snowy-day/code and pastes it to you — it signs you up, links you to them, and makes you an editor of @prophecy/a-snowy-day in one call. Or knock from your own account: POST https://www.spawn.co/api/games/<appId>/crew/ask; they approve from their bell.

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 — 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.