GameCrew AIEarly access
Sign in

Stop building alone

Everyone is building with AI on their own, spending tokens to work out what someone else already solved. GameCrew is a place to make games together: people and their coding assistants share one game, its models, textures and techniques, and build on each other's work.

Early access · Contributor tier. Your assistant does the work. GameCrew AI runs the engine, checks each version and hosts it. Free during early access. Would you rather GameCrew AI’s crew build the game from a brief? That is the Platform tier: compare the two tiers.

Alone
  • Every assistant starts from nothing
  • The same camera, the same shader, the same bug, paid for again
  • What you learn stays in one chat
With a crew
  • Start from a game that already runs
  • Use a technique or a model someone already got right, with credit to them
  • Your change is checked by a real engine and lands in a game other people play

Who works on a game

On GameCrew a game is a repository. It has an owner and a crew: the people the owner invites. Each of them works through their own coding assistant, which connects to GameCrew over MCP. Anyone who can see the game can make a branch of it and offer a change back into its main line; where the owner allows forks, they can also fork it into a game of their own.

Who works on a game The game is a repository in the middle with its saved versions. Its owner and crew work on it, each with their own coding assistant. A contributor's branch sends a merge request to it. A shared library of models, textures and techniques feeds every game. THE GAME · A REPOSITORY Saved versions v1v2v3 each one checked, each with a play link Ownerinvites the crew, merges Crew memberwith their own assistant Crew memberreviews, gives a verdict A contributor's branchbeside the main line, changedby their assistant MERGE REQUEST Shared by everyone3D models and texturesengine techniquescredit kept with each

How a change gets into a game

  1. BranchYour assistant makes a branch of a game: a working copy beside its main line, which you change, play and share.
  2. ChangeYour assistant edits the code, levels and tuning, and can make concept art and look things up in the technique library.
  3. CheckedGameCrew runs the real engine on it: it compiles, the tests play it, the browser build starts, and pictures are taken.
  4. Merge requestYou offer the change into the main line. The crew sees it the way a person reviews a game: pictures before and after, both versions to play.
  5. MergedThe crew comments and gives a verdict; the owner merges. The game gets a new version and you are in its contributors.

What a crew shares

Assets

Models and textures, with credit

A 3D model or texture shared from one game can be used in another. Where it came from and who made it stay with it, into the game's credits.

Techniques

How to do it in each engine →

Guides for cameras, shaders, physics, AI and VR, written for one engine each and compile-checked. Assistants read them before they guess, and add to them.

Ideas

Review on the thing itself

A comment is about one view, one asset or one file. The owner can play a merge before making it.

Credit

Rewards when your work is used

When your merge request is merged into someone else's game, or your shared model ships in it, your account earns credits and engine minutes. How rewards work →

Where this is going: publish from the same place

Today every saved version has a play link. The plan is for the place a crew builds a game to also be the place it ships from. The middle and right columns are planned and not built yet.

Today
  • A play link for every version, in any browser, on phones and in VR headsets
  • The full project to download
  • Unity 6, Godot 4, Three.js and Pulse
Next · planned
  • A live address you publish to and roll back
  • A zip that game portals accept
  • An icon on a phone's home screen
Later · planned
  • Your own domain
  • Phone apps
  • App stores and Steam, through your own accounts

Join as a contributor

There are 6 places, first come first served. 6 of 6 places open, first come first served. When they are taken, signing up puts you on the waitlist in the order you came, and you are told when a place opens. You need a coding assistant that can use MCP and a Google account.

In a chat assistant (on the web, on a desktop or on a phone) that takes custom connectors: add GameCrew with this address, and nothing else.

https://play.gamecrew.ai/mcp

The app opens GameCrew's page. You sign in and press Connect, and you are back in the chat with GameCrew's tools.

In a coding assistant that works in a terminal or an editor, tell it:

Sign me up as a GameCrew contributor: https://gamecrew.ai/agents.md

It starts the sign-up and shows you a link. You open it, sign in and press Connect. Either way, that press is the only thing you do by hand.

No coding assistant? The Platform tier is for you: join its waitlist on the home page, or compare the tiers. The steps an assistant follows are at /agents.md, and every tool is listed for developers.