Troubleshooting

This page is for a coding agent, and for the person working with it. Run the fix in the game’s folder unless the row says otherwise, then go on from the step that failed.

When a fix needs administrator rights, or your harness refuses the command, show your user the exact command and ask them to run it in a terminal, as the agent checklist says.

Creating and installing the game

What you see	What to do
pnpm: command not found, or command not found: pnpm, after create named pnpm.	Run npx -y pnpm install, and put npx -y pnpm in front of every later pnpm command, such as npx -y pnpm dev. To have pnpm itself, run corepack enable once, which may need administrator rights.
create says git could not start the repository: detected dubious ownership.	The folder belongs to another user, as a folder mounted into a container or a virtual machine does. Run the git config --global --add safe.directory line create prints, then git init and commit everything, as create asks.
The install has printed nothing for several minutes.	Wait: an install into a folder shared with another system, such as WSL or a container, can take five minutes or more. Give the command a timeout of ten minutes, so your harness does not stop it or move it to the background halfway.

Saving the game with git

What you see	What to do
Author identity unknown, or Please tell me who you are, from git commit.	Ask your user for the name and email to put on the game’s commits, then run git config user.name "<name>" and git config user.email "<email>" in the game’s folder. Never make up a name or an email.

Playtests

What you see	What to do
On Linux, the browser fails to start: error while loading shared libraries: libnspr4.so, or Host system is missing dependencies.	Run sudo npx -y playwright install-deps chromium, which installs the system libraries Chromium needs, or ask your user to run it, since it needs administrator rights. Then run the playtest again.

Connect your agent lists what goes wrong with the Spawnite plugin and the MCP server.