The Grey Area

Newest update: Clean slate on the new engine (2026-07-01)

• Rebuilt on the new engine — saves now restore your week cleanly when you come back, disconnects clean up after themselves, and phones are welcome at the booth. Trimmed the full-time leaderboard.

Earlier update: The Threshold (2026-07-01)

• Boundaries between zones now visibly separate the map, creating distinct territories you must navigate between.
• Crossing into new areas triggers a palpable shift — the atmosphere, lighting, and ambient presence change as you move between regions.
• Some zones now feel fundamentally different from one another, each with their own character and rules.
• The world feels less like one continuous space and more like a series of distinct places you're moving through.

Earlier update: The Harder Truth (2026-06-30)

• Your first impression notes vanish in hard mode after night three — you're too tired to trust your gut anymore.
• Management promotions strip away your safety net. You read visitors cold, no handwritten hints, just the phone and your instincts.
• The mothership variant shows you a sterile scanner readout instead of a sticky note, keeping everything clinical and distant.
• Late-game visitors in hard mode force you to commit without the comfort of your own scribbled observations.

Earlier update: The Mothership Ascends (2026-05-22)

• The mothership is no longer locked behind progression—you can access it from the start of your journey.
• Explore the depths of the mothership's interior and uncover what lies at the heart of the grey expanse.

Earlier update: The Doppelganger Protocol (2026-05-22)

• A mysterious doppelgänger now appears when conditions align, forcing you to confront an unsettling reflection of yourself.
• The Employee of the Month display has been redesigned with a darker, more introspective aesthetic that reflects the grey nature of your world.
• Debug systems have been refined to better track scripted encounters, ensuring no strange coincidence goes unnoticed.

Join and play, by yourself

This world is @goblinjo/the-grey-area. Its play URL is https://www.spawn.co/@goblinjo/the-grey-area/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/the-grey-area@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/the-grey-area; 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/the-grey-area/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.