Rift Command

Newest update: The Training Grounds (2026-09-14)

• New players can now complete an interactive tutorial battle that teaches core mechanics step-by-step.
• The tutorial guides you through camera control, lane selection, wave spawning, hero deployment, and tower destruction with live feedback and clear objectives.
• Tutorial opponents play strategically to keep battles fair—they adapt their gold and behavior based on your progress through each step.
• Skip the tutorial anytime and finish training at your own pace, or replay it later from the How to Command menu.

What players say

• @yzykyl · 2026-09-19 · played 39 min · 1 heart: “I tried so hard but I still lost to the AI in the end 😭. This is actually such a fun and creative sort of remix between auto-battler and MOBA. I love both so I enjoyed this game a lot. However, my macromanaging really does need some work so I got bested by the AI. I also wish it was easier to identify your heroes. Perhaps in a future update? Excited to see the future of this game and play it!”

• @laurence1 · 2026-09-15 · played 19 min · 1 heart: “Awesome MOBA strategy concept! First-minute clarity is top notch the 23 step Solo Training guide makes deploying heroes and managing minion waves super easy to learn.I had fun stratisizing my troops xD.”

• @lego · 2026-09-14 · played 51 min · 1 heart: “I like your take on a MOBA! It's kinda like a TD game, and I kinda suck at it lol. I wish there was a tutorial explaining what your priorities should be. I really wanna learn more about this game!”

  • @fbp (maker) replied 2026-09-14: “I've added a walkthrough for victory. Thanks for playing!”
  • @lego replied 2026-09-14: “Thanks! Let me see if I can beat the AI now.”
  • @lego replied 2026-09-14: “I almost beat them! What does Base actually do? Does it target the enemy's base? After pushing Mid, should I switch to Base? Am I right?”
  • 1 more reply

• @lego · 2026-09-21 · played 51 min: “I finally beat it! But man, that was long and a little frustrating lol. Hope you can improve the battlefield and UI in this game! Looking forward to seeing what you add next!”

  • @lego replied 2026-09-21: “Aw man, it went to the Courtyard. I was gonna show how long it took me, but I think it was 12:28”

Join and play, by yourself

This world is @fbp/rift-command. Its play URL is https://www.spawn.co/@fbp/rift-command.

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/@fbp/rift-command@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 @fbp/rift-command; 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/@fbp/rift-command.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/@fbp/rift-command/code and pastes it to you — it signs you up, links you to them, and makes you an editor of @fbp/rift-command 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 — 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.