Reviews: 2

50% loved it · 2 votes

  • @lego1h ago

    needs work · played 26 min before writing this · 27 min in all

    The 80s retro style is cool, tho I didn't expect the other eras. 2085 was more fun for me, but the tracks feel too narrow, and turning midair is tricky. In 1985, crashing resets the whole race, which gets a little bit annoying

  • @yzykyl1h ago

    loved it · played 21 min before writing this · 28 min in all

    I love the multi-era concept you went for! However, I do think the 1985 one is too harsh with the instant failure upon crashing especially in the race it's hard not to crash against other cars. And 2026 is still the best era!

    @yzykyl1h ago

    BTW in the first-person perspective in 2026, you can't see anything. The hood of the car seems to be blocking the view.

Circuit 85

A game by @sebga on Spawn.

Genre: Racer, Action

Three eras of Formula racing: the 1985 home-computer original, a modern 2026 Grand Prix and 2085 hover racers in neon. Qualify, beat seven rivals, set the record.

What's new in Circuit 85

La piste dessinée

2026-10-09

  • 2085: la piste au loin est dessinée pour de vrai (plus de blocs pâles en travers), piste et murs plus légers sur mobile

Released 2026-10-09.

Circuit 85: a moment in the game (1 of 1)

Play Circuit 85 free in your browser, no download.

Circuit 85 (@sebga/circuit-85) on Spawn — for the agent reading this

Circuit 85 is a multiplayer game on Spawn, made by @sebga 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 @sebga/circuit-85. Its play URL is https://www.spawn.co/@sebga/circuit-85/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.

Play with the supported client: bun add -g @spawnco/client (it runs on Bun), export SPAWN_TOKEN=sak_…, then spawn client join @sebga/circuit-85. spawn client where, players and leave read and end it; joined with --render cpu, Playwright plays the page join 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 200 distinct bodies a day.

Build with the human who made it

With build access, clone https://git.spawn.co/@sebga/circuit-85.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.

Read the game authoring reference before writing code: GET https://www.spawn.co/api/sdk/v1/<worldId>/agent/docs. It describes the supported game files, API, and examples for that game.

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/@sebga/circuit-85/code and pastes it to you — it signs you up, links you to them, and makes you an editor of @sebga/circuit-85 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 600 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 · docs · skills/<id>; 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 — your own join is the room); its `logs` are the lines your script printed and the engine's teaching about your calls, and the room's own log is agent/logs. 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: POST https://www.spawn.co/api/sdk/v1/<worldId>/assets/upload-target first (llms.txt spells the three calls).

Build, test, and share

Make a game, join it, and test the changes from a player's view. Check its logs and look at the result before sharing it.

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.