Working with the agent
Approvals, permission modes, checkpoints and spending limits.
Describe what you want in the chat: a mechanic, a level, a fix. The agent reads your project, plans, changes code and the editor, then play-tests and looks at the result before it reports back.
Replies in the rose view use the same readable formatting as chat, including headings, lists, bold text and code. They update as the agent responds.
Completed message footers show the model and time spent. Check Settings → Account → Analytics for credit usage and balances.
Choose the Focus chat expand icon in the chat sidebar header to expand the conversation. The Show game view collapse icon brings the game view back. Hover over either icon to see its label; the compose icon starts a New chat.
In expanded chat, game controls sit in a separate row beneath the header. Play and Stop stay visible, while the More game controls menu contains Art to game and Play in window. The editor's current state appears as text rather than a disabled action button.
You can keep typing while it works. A new message waits in a queue, and Steer hands it to the agent at its next step.
Claude and Codex detection
If Claude or Codex is not detected after installing or signing in through its CLI, fully close and reopen Ryuo. If it still is not detected, restart your computer. Ryuo checks the CLI again when it starts.
Permission modes
Anything that changes files, the editor or spends credits asks for your approval first, depending on the mode you pick above the chat:
| Mode | Asks before |
|---|---|
| Manual | every file edit, command, editor change and paid generation |
| Accept edits | commands, editor changes and paid generation; file edits go ahead |
| Auto | nothing, except actions that always ask, such as restoring a checkpoint |
Checkpoints
Before the agent's first change in a task, Ryuo saves a checkpoint of your project's code, content and settings. If a change goes wrong, ask the agent to show what changed and restore the files you choose. It refuses to overwrite a file you've changed since.
Checkpoints are not version control. Keep using Git or your usual backups.
Spending limits
Each task has limits, which you can change in Settings:
| Limit | Default |
|---|---|
| 3D generation | 150 credits |
| Images | 8 |
| Videos | 2 |
| Audio clips | 30 |
| Model spending stop | 3,000 estimated credits |
When a limit is reached, the agent stops and asks you before continuing.
The model spending stop uses estimated Ryuo credits for one task. Work already running can take usage above the stop, and local assistant subscriptions are separate. Existing saved limits keep their value.
Progress and recovery
Ryuo reopens your selected chat when you restart the app, including answers you already gave. If you left on New chat, it stays empty; earlier conversations remain in Sessions. Chats tied to another Ryuo account require signing back into that account.
If a reply or question was interrupted, your conversation stays visible. Answer the last question to continue, or type a follow-up in the chat box. Work does not restart automatically, and past approvals are not reused. Long conversations may be shortened when passed back to the assistant, so saved project files remain the reference for implementation details.
The assistant is instructed to explain what it is about to do, report major stage changes, and explain failures and the next recovery step. You should not need to repeat decisions already in the conversation.
When using Codex, edits and commands go through Ryuo's permission modes. A technical message about Codex's native read-only mode does not mean your project is read-only. Ask the assistant to use Ryuo's tools; you do not need to change Codex's sandbox configuration. A denial in Ryuo still applies.
Ryuo shows when it is saving a recovery point, compiling, opening Unreal or connecting editor tools. File and compiler progress is shown when known; editor startup shows elapsed time instead of a countdown. Expand a tool row for technical details and phase timings.
A connected editor with unchanged inputs can be reused after a successful compile in the same session. Function-body changes can use a Windows hot patch; structural changes still need a planned restart. A compile error needs diagnosis before another restart. Review build error starts that diagnosis, while Review recovery in the conversation previews saved files before any restore.
A failed play test explains whether its log was unavailable, a scripted action failed, runtime errors appeared, or a capture did not show the running game. A screenshot by itself does not make the test pass. On Mac, Ryuo reads Unreal's native log folder as well as project-local logs. Resolve missing-log or connection problems before repeating the test; these do not prove your game logic is broken.
Long conversations initially show the latest 200 messages. Show earlier messages loads more without deleting history. Choose Show all for search before searching the complete conversation.
Make room to write
Drag the top edge of the message box up to make it taller, or down to shrink it. You can also use Expand message box and Shrink message box. With the resize handle focused, use the arrow keys, Home or End. Your draft and attachments stay in place.