Edit a game made in Rosebud
Bring a game made in the Rosebud editor into a folder, change it locally and publish it back.
Use this to change a game someone built in the Rosebud editor, with your own tools or a coding agent. Pulling needs Rosebud Pro or higher on the owner's account, for code download; see Pricing. Without it, pull fails with plan_required, while update still works: tell your agent what you changed in Rosebud before it updates.
Connect to the game
Find the project ID in the editor's address, https://rosebud.ai/edit/<project_id>, then run:
rosebud connect --project <project_id>Open the approval_url it prints, sign in as the game's owner and approve. rosebud status reports active once you have.
Pull its files
rosebud pull --directory ./gameThis writes the game's current files, text and media, including edits made in Rosebud, into ./game. Use a folder that holds only the game: update refuses hidden files such as .git. On Windows, a name Windows can't keep (one ending in a dot or space, or a device name such as con.js) is skipped.
Games made with Rosie include AGENTS.md and other notes. Read them before you change anything.
Edit and publish
rosebud update --directory ./gameThe game keeps its link. Files Rosebud already has aren't uploaded again. Keep new media in assets/ with lowercase names.
Media the editor accepts but an update can't upload, such as MP4, GIF, WebM, M4A, FBX or OBJ, is kept only if you leave the file unchanged at the same path. Changing or renaming one is refused with unsupported_file: do that in the Rosebud editor, then pull again.
If someone keeps editing in Rosebud while you work, run rosebud pull --directory ./game again before each update. It brings in their changes and keeps yours. See rosebud pull for conflicts.