Autosave
The editor saves your changes to the server right away. Both values you edit manually and changes the AI applies are kept without pressing a save button. This page explains how saving works, what Cloud Save and the 실시간 (Live) indicator in the bottom bar mean, and how saving differs from checkpoints.
The tests on this page were done in the oasisw.ai editor (macOS Chrome) on 2026-10-26 to 29.
Changes are kept immediately
When we changed a value and refreshed right away, the new value was still there.
- We changed X of
Box'sPositionto3, pressed Tab, and refreshed the tab immediately. When it reopened, the value was3(2026-10-29, 1 run). - After moving an entity, renaming a scene, adding a component, and importing
Ammo, we reopened the editor in a new tab. All of the changes were still there (2026-10-29, 1 run). - Changes the AI applied to the scene were also still there after a refresh (tested on 2026-10-26).
Some things are not saved. Entities you expanded in HIERARCHY went back to collapsed after a refresh.
Bottom bar indicators
| Indicator | What we observed |
|---|---|
| Cloud Save | When clicked, it briefly changed to Saving... and then back to Cloud Save, and Saved to cloud appeared on the right side of the bottom bar (1 run). All the changes above were kept even without clicking it |
<project name> — <scene name> | The project and scene currently open |
Green dot and 실시간 (Live) | Appears to mean you're connected to the server. Right after opening the editor, 연결 중… (Connecting…) appeared briefly |
| Action name at the far right | The last action you performed, such as Update Transform or Add Entity. Undo reverts this action |
Here is what we saw in the browser about how saves are sent (2026-10-29).
- Regular edits are sent as you make them over the server connection that the
실시간indicator refers to (one per scene). We changed a value and watched for 30 seconds, and no separate save request was sent. - Clicking Cloud Save sends one more request that uploads the entire current scene to the server. Then
Saved to cloudappears.
So you don't normally need to click Cloud Save. Use it when you're worried about saving, for example after the connection drops and comes back, to upload the whole scene once.
When the connection drops
Once, while assets were downloading, Disconnected from the server. Reconnecting… appeared for a few seconds and then the connection came back on its own (2026-10-26, 1 run).
On 2026-10-29 we deliberately cut the live connection. It reconnected on its own within 1 second, and a Position value we changed in the meantime was still there after a refresh (1 run). The bottom bar showed 실시간 the whole time.
On the same day we turned off Wi-Fi for about a minute (1 run).
- After Wi-Fi was off, the bottom bar still showed
● 실시간, and no disconnection message appeared on screen. - While disconnected, we changed BlueBox's
PositionY from 2.5 to 4. The field kept showing 4. - CONSOLE logged
클라우드 저장에 실패했습니다(Cloud save failed) 4 times, and the error count on the left of the bottom bar turned red and showed 4. - When we turned Wi-Fi back on,
Saved to cloudappeared at the bottom right, and Y was still 4 after a refresh.
Edits made while disconnected were saved once the connection came back. However, the ● 실시간 indicator alone doesn't tell you the connection is down. If the error count in the bottom bar turns red and goes up and CONSOLE shows 클라우드 저장에 실패했습니다, treat it as disconnected and stop editing until it reconnects. After it reconnects, check that Saved to cloud appears; if it doesn't, click Cloud Save once.
Pending Verify whether edits are kept if you close or refresh the tab while disconnected
AI work and saving
Changes the AI makes are applied to the scene as it works, and from the moment they're applied they are saved just like manual changes.
AI work runs separately from the editor tab. In a test on 2026-10-29, the work ran to completion and the results stayed in the scene both when we refreshed the editor tab right after clicking 예 (Yes) (1 run) and when we closed the tab and reopened it a minute later (1 run).
Saving vs. checkpoints
Autosave keeps overwriting "the current state". It doesn't leave points to return to an earlier state. If you need a point to return to, create a checkpoint in the VERSION CONTROL window. Creating one before giving the AI a large task, in particular, gives you somewhere to go back to if you don't like the result.
| Autosave | Checkpoint | |
|---|---|---|
| When | Automatically, on every change | Only when you create one |
| What's kept | One current state | One per checkpoint you create |
| Reverting | Only recent actions, with Undo | Everything, back to that point |
To create a checkpoint, see Save and restore your work with checkpoints.