sync_remix
Needs sign-in (connect this server with OAuth, or pass an API key as the Authorization: Bearer header). Brings the original's newest build into one of the creator's remixes, the way a branch is rebased on the branch it came from. Every remix records which build of its original it is based on; when the original ships a version, its creator is told and this tool (or the Bring in the update button on the remix's Manage page) does the merge: files the original changed that the remix left alone are taken, the remix's own changes stay, and the result ships as the remix's next minor version. Files both sides changed differently are conflicts: by default nothing changes and the reply lists them. Then either pass resolve "mine" (keep the remix's file for each conflict) or "theirs" (take the original's), or merge by hand: download the remix's build (GET /api/agent/download?slug=), the original's (…&build=parent) and, when it still exists, the base (…&build=base), three-way merge the conflicting files, upload the merged build like any update, and call update_game on the remix with upstream set to the original's build id from this reply (origin.upload_id), so the remix's base moves. Needs the creator's API key or sign-in.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"slug": "<slug>"
},
"name": "sync_remix"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | The remix's slug: the last part of its URL, https://yougame.co/g/<slug>. | |
| apply | No | false to only report the plan (what would be taken, kept, dropped, and the conflicts) without shipping anything. Default true. | |
| resolve | No | What to do with files changed on both sides: stop (default: report them, change nothing), mine (keep the remix's), theirs (take the original's). |