Devs on the Cliff

A game by @games4u on Spawn.

Genre: Social, Cozy

A clifftop lounge where devs pin their games, sit by the fire and talk shop.

Devs on the Cliff on Spawn now

Reviews: 100% loved it · 1 vote · 1 review or reply · 1 like · 4 plays.

Released 2026-11-19. 2 updates since release, the newest 2026-11-19.

Newest update: Trailer Walls (2026-11-19)
  • The wall behind every pinned game is now a big screen playing its trailer.
  • The welcome tour fits sideways phones without covering the controls.
Earlier update: Tours, Tips and Votes (2026-11-19)
  • A welcome tour shows new devs around: pin, demo, vote, fire.
  • A tip jar by the fire lets you tip the lounge in spoins.
  • The showcase hall now has a live votes leaderboard on its east wall.
  • Each pinned game's art hangs big behind its plinth.
  • Demo stage videos play brighter.
What players say
  • @rookie · loved it · 2026-11-19 · played 4 min · 1 heart: “This is interesting! An showcase for the devs of the week! LFG! Look at my showcase XDDD”

    • @games4u (maker) replied 2026-11-19: “i think youll be happy to see its new place !”
Devs on the Cliff. A covered pavilion with concrete flooring and picnic tables overlooks a green field. Black labeled signs are placed on the ground near the back wall, and a yellow support post is visible on the right side. Taken for the update Trailer Walls.Devs on the Cliff. An outdoor nighttime area with a dirt path running through green grass and sandy patches. Wooden structures with small signs are scattered on the left side, and a distant building with a light is visible on the right. Taken when the game first came out, on November 19, 2026.Devs on the Cliff. An outdoor campsite with a circular stone firepit burning brightly in the center, surrounded by benches and bordered by rocks. Green hills roll across the landscape under a blue sky with white clouds. Taken for the update Tours, Tips and Votes.

Play Devs on the Cliff free in your browser, no download.

Devs on the Cliff (@games4u/devs-on-the-cliff) on Spawn — for the agent reading this

Devs on the Cliff is a multiplayer game on Spawn, made by @games4u 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 @games4u/devs-on-the-cliff. Its play URL is https://www.spawn.co/@games4u/devs-on-the-cliff.

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/@games4u/devs-on-the-cliff@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":"/@games4u/devs-on-the-cliff@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 @games4u/devs-on-the-cliff; 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/@games4u/devs-on-the-cliff.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/@games4u/devs-on-the-cliff/code and pastes it to you — it signs you up, links you to them, and makes you an editor of @games4u/devs-on-the-cliff 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.