Pocket Studio Docs

Remix

A remix is a game of your own that starts from a copy of a published game. Your coding agent copies that game to your computer and changes it into yours. A published remix names the game it came from: its page says A remix of Moon Lander by docs-writer, and the page of Moon Lander lists it under Remixes.

#What can be remixed

  • A game built outside Pocket Studio, such as Pocket Tokyo or Pocket Maneuver, while it is published and its author named its public repository. A remix starts from that repository.
  • A game made in Pocket Studio (a PocketJS app made with the pocket-studio command) while it is published. Each build its author pushed carried its source files, and the Studio keeps the newest.

A game that is not published, whose author named no repository, or that was built before the Studio kept sources, cannot be remixed. It has no Remix.

#Start a remix

Remix stands beside Play and Download wherever a game is shown: on the game's page, on its card on the landing page's shelf, and in the dock of its play page, which leads to the game's page. It opens a dialog with one prompt and asks for no sign-in.

  1. Copy the prompt.
  2. Paste it into your coding agent, in the directory where you keep projects. Any agent that runs commands on your computer takes it: Claude Code, Codex, Cursor and others.
  3. Replace <describe your game> with what you want to change, and send it.

For Pocket Maneuver the prompt reads:

Remix the game "Pocket Maneuver" (https://studio.pocket.nexus/games/maneuver) into a game of my own.

1. Clone its source with its submodules: https://github.com/doodlewind/pocket-maneuver
2. Read its README.md and AGENTS.md. Build it and run it on this computer.
3. Change it: <describe your game>

When I ask you to publish it on Pocket Studio, follow https://studio.pocket.nexus/docs/remix/#publish

The agent clones the repository with git, builds the game with the repository's own tools and runs it. Up to here your computer holds nothing of Pocket Studio's: no pocket-studio command, no plugin and no link to an account. The repository's README.md and AGENTS.md say how the game is built, on which computers, and what a remix renames before it is published (its title, its app id, its package names).

Under the prompt the dialog has the game's Source code as the download part shows it. Its second part has Get a link code and a link to this page. For a game built outside Pocket Studio it is headed Publish it on Pocket Studio and also links Pocket3D on GitHub: the source and the documents of the engine those games are built on. For a game made in Pocket Studio it is headed Link code.

#Publish a remix

Publishing is where the pocket-studio command comes in. Ask your agent to publish the remix: the prompt sent it to this part, and each step below is a command it runs in the remix's directory. The one thing it needs from you is a link code.

An agent that reads this page runs steps 1, 3 and 4 itself. It asks the user for the link code of step 2, unless pocket-studio whoami prints an account already.

1. Set the computer up.

curl -fsSL https://studio.pocket.nexus/install | sh

The command needs curl and tar. It finds Bun or installs it, copies the Pocket Studio kit into ~/.pocket-studio and puts pocket-studio on your PATH. A shell that does not find pocket-studio afterwards runs it as ~/.pocket-studio/bin/pocket-studio. A computer that has the command skips this step.

2. Link the computer to your account. Press Remix on the game's page, then Get a link code: the dialog asks you to sign in and shows a code that works once, within 15 minutes. Give it to the agent, which runs link with it:

pocket-studio link K7QD-9M4X
Linked this machine to https://studio.pocket.nexus as docs-writer

A computer stays linked: when pocket-studio whoami prints an account, this step is done.

3. Register the remix.

pocket-studio register --title "Night Maneuver" --remix https://studio.pocket.nexus/games/maneuver
Registered "Night Maneuver" as docs-writer, a remix of "Pocket Maneuver" by evan.

--title is the remix's own name. --remix names the game it came from by its page, its address, its share link or its id. The command writes .pocket-studio.json, which names the server and the remix and holds no token, and adds it to the copy's .gitignore. A guest account cannot register a game.

4. Upload and publish.

StepCommand
Build the game for a device with the repository's own toolswhat its README.md says
Upload the package you built, one a devicepocket-studio package <file> --target <device> --version 0.1.0
Let accounts download the packagespocket-studio downloads on
Set the picture on its pagepocket-studio cover <png>
Add words, clips and pictures to its pagepocket-studio listing <dir>
Name your copy's public repository, so others can remix your versionpocket-studio repository <url>
Publishpocket-studio publish --slug <name>

A remix is published once it has a package. --slug is the name in the remix's address and in its page's, /games/<name>: 3 to 32 lowercase letters, digits and inner hyphens. The clone's git remote origin is the original repository: push to a repository of your own before you name it. Games built elsewhere describes each command, and Packages the file each device takes.

#A game made in Pocket Studio

Pocket Studio holds the source of a game made in it and hands it to accounts, and such a game is built with the PocketJS compiler and runs on a device in your room. Its prompt sends the agent to this part:

Remix the Pocket Studio game "Moon Lander" (https://studio.pocket.nexus/games/moon-lander) into a game of my own.

1. It is a PocketJS app whose source Pocket Studio holds. Follow https://studio.pocket.nexus/docs/remix/#pocket-app to set this computer up and link it to my account. Ask me for the link code.
2. Copy the game: pocket-studio remix a8ja3s2exefnv
3. Change it: <describe your game>

1. Set the computer up, with the command of step 1 above:

curl -fsSL https://studio.pocket.nexus/install | sh

2. Link the computer to your account. The agent asks you for a link code: press Get a link code in the game's Remix dialog and give it the code.

pocket-studio link K7QD-9M4X

3. Copy the game, in the directory where you keep projects, with the id the prompt names:

pocket-studio remix a8ja3s2exefnv
Started "Moon Lander Remix" for PSP as docs-writer, a remix of "Moon Lander" by docs-writer
Created ./moon-lander-remix from the source of "Moon Lander" by docs-writer: 11 files
Build 1 is on the PSP (.pocket/studio/out/psp/moon-lander-remix.js, 514 KiB)

The copy is a project titled " Remix" with a session on the game's first device; --device <id> picks another. Its AGENTS.md describes the game that was copied.

4. Change it and send builds. pocket-studio title "<Title>" gives the remix a name of its own, pocket-studio shot writes pictures of the game for the agent to read, and pocket-studio push sends a build to your room. What the agent does has the loop.

5. Publish, when you ask for it, with pocket-studio publish: Publishing and sharing.

#Copy and register in one command

pocket-studio remix https://studio.pocket.nexus/games/maneuver

On a computer that is set up and linked, pocket-studio remix takes a game's page, its address, its share link or its id.

  • A game built outside Pocket Studio is cloned with git, with its submodules, into ./<game>-remix/ and registered as " Remix": the clone of Start a remix and step 3 of Publish a remix in one command. It ends with the steps that are left.
  • A game made in Pocket Studio is copied as above.

#A remix is a game of its own

  • It has a page of its own, /games/<name>, with its own Download part, and its own address.
  • The original's page lists it under Remixes, with its title, who made it and the devices it has packages for. The page lists the newest 24 and says how many more there are.
  • Its packages are its own. A remix that adds a device is that remix's version for the device, not the original's. Pocket Tokyo with a PSP package and a remix of it with a Nintendo 3DS package are two games: the remix's page offers the 3DS package, and Pocket Tokyo's page offers the PSP one and names the remix. When the original's author later uploads a 3DS package, it is the original's, beside the remix's.
  • Its packages are homebrew from you, unless Pocket Nexus verified the remix. Only a verified game may deploy a web build, so a remix of a Pocket3D game has no browser version at its address until then.
  • Unpublishing or deleting a remix takes it off the original's page.

#What the original's author keeps

The Terms say how a remix works. By publishing a game made with the Pocket Studio command line, its author gives every Pocket Studio user a licence, free of charge, to copy, change and publish its source as a remix. Taking the game down or deleting it ends that licence from then on and stops new remixes; copies downloaded before and remixes made before stay with the people who have them.

A game built elsewhere is remixed under the licence of its own repository.