Run the project in the user's open R3 editor
r3_editor_runPress the Run buttons of the user's open R3 editor: start physics, code, audio and music (all of them, or the ones named in systems), exactly as the user's own click does — a paused simulation resumes. Use it to TEST what you built: run it, then look with r3_editor_capture and read live values with r3_editor_inspect. Changes nothing saved. It shows the named project first (focused, scrolled into view): the systems start for every project open in that tab, but only a project on screen moves. The scene only moves while that tab is in front: a browser pauses a background tab, and the answer then says the scene is NOT advancing. Needs the editor:run right.
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": {
"projectId": "<projectId>"
},
"name": "r3_editor_run"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| systems | No | Which of the editor's Run / Stop buttons: physics, code, audio, music. Leave out for all of them. | |
| projectId | Yes | A project open in the user's editor (r3_whoami lists them). |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| shown | No | ||
| action | Yes | ||
| answer | Yes | This answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guidance. | |
| editor | Yes | ||
| systems | Yes | ||
| projectId | Yes |