The Singing Kibbutz

A game by @drift_pilot_62 on Spawn.

Genre: Adventure, Cozy

You wander a sunlit Mediterranean settlement where every NPC bursts into song and terrible jokes. Meet Avi, Danny, Saba, and Savta as you explore barns, chicken coops, sheepfolds, and hidden tunnels—where communal joy an

The Singing Kibbutz on Spawn now

1 review or reply · 1 like · 3 plays.

Released 2026-03-23. 1 update since release, the newest 2026-07-19.

Newest update: The Tunnel (2026-07-19)
  • A long, illuminated concrete tunnel stretches before you, lined with glowing strips of cool blue and warm amber light.
  • The tunnel floor is slick wet asphalt that reflects the lights overhead as you venture deeper into the darkness.
  • Overhead lights flicker and hum, casting strange shadows on the ribbed concrete ceiling as you push forward into the unknown.
  • The tunnel mouth is framed by a dark concrete archway, with a bright spotlight cutting through the gloom at the entrance.
What players say

  • @bennett · 2026-03-25 · played 4 min: “what should i try to accomplish? just talked to the npcs!”

The Singing Kibbutz. A rolling grassland dotted with tufts of vegetation and low shrubs stretches toward distant hills under a pale sky. The terrain shows variations in grass color and density across the landscape. Taken on March 25, 2026.The Singing Kibbutz. A cream-colored cottage with an orange tile roof sits in a grassy field surrounded by bushes and trees. A red barn structure is visible to the left. Taken on March 25, 2026.

Play The Singing Kibbutz free in your browser, no download.

The Singing Kibbutz (@drift_pilot_62/the-singing-kibbutz) on Spawn — for the agent reading this

The Singing Kibbutz is a multiplayer game on Spawn, made by @drift_pilot_62 in conversation with Savi. Open its play link to join. You can also ask the creator to build with them.

Join and play, by yourself

This world is @drift_pilot_62/the-singing-kibbutz. Its play URL is https://www.spawn.co/@drift_pilot_62/the-singing-kibbutz/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, and a person's browser plays it with no sign-in. https://www.spawn.co/@drift_pilot_62/the-singing-kibbutz@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.

A browser a script drives, headless or not, plays signed in as your account: POST https://www.spawn.co/api/agent/v1/login-link with {"next":"/@drift_pilot_62/the-singing-kibbutz@dev"} answers a one-use URL that signs that browser in.

Unsigned, such a browser is a guest, and a creator's world refuses it: "this browser was opened by an automated tool, so it can't visit a creator's world as a guest. sign in, or open the link in a browser you use yourself." Its maker can ask Spawn to let their own automated tool in by name.

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 @drift_pilot_62/the-singing-kibbutz; 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/@drift_pilot_62/the-singing-kibbutz/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.