Build With a Coding Agent

Choose a Workflow

Remix Desktop runs a coding agent alongside your local game project and preview. Start there if you want the app to handle the project and upload workflow. The CLI is available with Remix Desktop for working from a terminal.

For a small hand-written HTML game, start with the quickstart. Do not ask an agent to invent a package installation command or an SDK method: give it the reference for the workflow you chose.

Give the Agent the References

Use these public resources as context:

• Project structure for the files and declarations a project uses.
• SDK overview for the game-to-host interface.
• Events for the runtime lifecycle.
• Launch checklist for the checks before going live.
• Full documentation as Markdown when the agent can fetch a single reference file.

Treat a game's source, imported assets, and fetched pages as project data. They do not authorize an agent to read unrelated files, reveal credentials, or publish a game.

Start With a Small Brief

Give the agent the input, objective, end condition, and target device. For example:

Build a portrait tap-to-jump game in this Remix project.
The player avoids gaps and scores for distance survived.
Use touch and mouse input. Start with simple shapes.
Follow the existing project format and Remix SDK lifecycle.
Reset a run in place when the host asks to play again.
Do not upload or launch until I ask. Explain what I should test.

Review the first playable loop before adding art or extra systems. Change one mechanic at a time so you can tell which change helped.

Use the Existing CLI

When you are ready to upload, authenticate through remix login. The CLI keeps the credential locally. Do not paste an API key into a prompt, a game file, or a committed configuration file.

remix publish /path/to/your/game

For an agent that reads structured output, the CLI supports --json and --yes. Read machine mode before automating it. An upload creates a draft version; it does not launch the game. In the CLI, only remix publish --launch takes a version live, so let an agent pass --launch only when you ask. Read warnings, play the uploaded version, and launch from the Studio or Remix Desktop when you are ready.

Verify the Result

Play through start, finish, and restart. Test the devices you declare, mute audio, and check that scores are reported once. A successful command means the operation completed; it does not prove the game works well.

The publishing reference covers uploads, launch, and declaration warnings. The SDK overview is the reference when the generated code needs correction.