Somewhere in the Snow

Newest update: The Online Expedition (2026-09-12)

• Two penguins can now reunite in shared online rooms, each player controlling their own bird across a split screen.
• Online rooms are named and hosted — join a friend's expedition by room name, or create one and wait for them to find you.
• Weather and reunion happen together: storms roll in as you search, and when you meet, you both see the same moment of victory.
• You keep your local pair and custom names safe — switching between solo expeditions and online play never erases your progress.

Earlier update: Clearer Paths (2026-09-12)

• The main menu now gets straight to the point — choose Local or Online play without the extra explanation.

What players say

• @sunraku · 2026-09-12 · played 17 min · 1 heart: “Love this game. Finding each other in the snow. It was also good that there is a choice for Local and Online. The UI also is clean. Love to spend time in this game”

  • @gamer (maker) replied 2026-09-12: “appreciate it!”

• @rookie · 2026-09-12 · played 48 min · 1 heart: “Really nice update to the front menu! Skipping the extra text to jump right into Local or Online play feels great. Navigating through the snowstorms using callout arrows and sliding around mountain peaks with a partner is as charming as ever. Awesome work @0xkep!”

  • @gamer (maker) replied 2026-09-12: “thank you!”

• @alongzera · 2026-09-12 · played 27 min · 1 heart: “I very much like the concept of the game easy but fun! Can't wait to play this game with someone!”

  • @gamer (maker) replied 2026-09-12: “thank you so much! just a little cozy game to play with a partner/friends/family for a couple minutes of fun. i'm glad you enjoy it”

• @chizkeykkk · 2026-09-20 · played 22 min: “This is such a cool idea, bro! The music was so relaxing, and when my friend and I finally managed to locate each other, it was so fun haha 😂 Definitely had a great time playing this together!”

Join and play, by yourself

This world is @gamer/somewhere-in-the-snow. Its play URL is https://www.spawn.co/@gamer/somewhere-in-the-snow.

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/@gamer/somewhere-in-the-snow@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 @gamer/somewhere-in-the-snow; 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/@gamer/somewhere-in-the-snow.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/@gamer/somewhere-in-the-snow/code and pastes it to you — it signs you up, links you to them, and makes you an editor of @gamer/somewhere-in-the-snow 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, 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.