# Your code is saved automatically

> Public channel — documentation of app 3.6.3. Follow the availability notices of each service.

Source: [Your code is saved automatically](/en/application/projet/sauvegarde/)

No setting to turn on: you just need to be signed in to your VibeStarter account.

You don’t have to think about backing up. While you work — and while your agents work — the app saves your project and uploads your code online on its own. There is no “Save” button, and that is intended.

## The cycle of a backup

1.  **You work** You or an agent edit the project’s files.
    
    _continuously_
    
2.  **The app saves** A version is created, with the message “Automatic save”.
    
    _code only_
    
3.  **The app uploads** The badge shows “Saved just now”.
    
    _online_
    
4.  **Your team and your other computers receive** Everyone moves forward on the same version.
    

The cycle loops while the project is open. It speeds up when you edit files, calms down when nothing moves, and restarts straight away when you come back to the app window.

## Where to check that it is saved

1.  In the project bar, click Versions.
2.  Read the badge at the top: **“Your code is saved and synced”**.
3.  Just below, the date of the last upload: **“Saved just now”**, then “Saved 3 min ago”.
4.  A line notes what is not covered: “Images, models and sounds stay on this machine; Roblox hosts them once uploaded.”

The same information is visible without opening the panel: a coloured dot is placed on the

Versions button of the project bar.

The buttons exist, but you don’t need them

The Host on Cloud and Sync now buttons are under

Advanced (git). The default view syncs on its own; they are only useful if you want to force an immediate upload. :::

## What goes online, and what stays with you

| Goes to the online backup | Stays on your computer |
| --- | --- |
| Your scripts and code files | All images and icons |
| Your project settings | All sounds and music |
| Text files under 2 MiB | All 3D models and their source files |
| Your version history | Any text file of 2 MiB or more |
|  | Anything your project ignores on purpose |

The sorting is based on the content of the file, not on its extension: any binary file leaves the online backup, whatever its name. **The file is never deleted** — it stays on your disk, it is simply not uploaded.

Two cases are surprising:

-   **A text file saved in UTF-16 is treated as binary.** The app looks at the first 8 KiB of the file: if they contain a null byte, the file stays on your computer. Save it in UTF-8 so that it is backed up.
-   **A git repository stored inside the project is not backed up.** Its contents stay on your computer.

When this happens, the app tells you:

> **“N file(s) kept out of the online backup”** “The online backup only keeps code. These files stay on this machine and are not synced.”

## Size limits

If your project stays stuck on “Syncing…” or “Offline — will retry automatically” even though your connection works, or on a conflict that comes back after a trim, even when you work alone, [update the app](/en/application/premiers-pas/mises-a-jour/). Version 3.6.3 fixes these blockages. Keep your local project and its files: recreating it from an old Cloud backup would not recover the changes that have not been sent yet.

Each code history saved online is limited to **50 MiB** (about 52 MB). This limit applies to the full history, even when the app only sends the latest changes. It is managed automatically; it is not an asset or account quota.

### When the history is trimmed

When the history reaches 50 MiB, the app trims it itself. It keeps the most recent versions that fit in **30 MiB** and removes the oldest ones. It therefore removes more than the simple overage, to leave room before the next trim. **Your current state is never sacrificed, and all your files stay on your machine.**

The message **“Online backup trimmed”** shows the number of versions kept, “after removing old versions or grouping identical versions”.

A trim can also happen without reaching 50 MiB: old versions may contain files that the code backup does not handle. The message then says that these files were removed from the saved history, and that old versions may have been removed too to respect the maximum size. Two versions that have the same code after this removal may be grouped together. Your current files stay on your computer.

| Weight of the latest state of your code | What happens | What to do |
| --- | --- | --- |
| Under 30 MiB | The trim keeps several recent versions | Nothing |
| Between 30 and 50 MiB | Only one version is kept, and the trim comes back soon | Slim down the project: look for large generated text files |
| Over 50 MiB | The online backup stops. The message names the largest files | Remove them from the project, or add them to the project’s ignored files |

In the last case, the backup starts again on its own as soon as the files are removed, with nothing to click.

### Recover a removed version

Removed versions are no longer in the Versions list, and there is no button to restore them. They can still be recovered by two routes, each with its limit.

**On your computer.** Before each trim, the app keeps a full copy of the old history in the app’s Linux virtual machine, which the messages call “the project environment”. The file is stored in `/home/app-user/backups/` and its name starts with `cloud-` and ends with `.bundle`. The “Online backup trimmed” message gives its exact path: “A copy of the old history stays in the project environment”.

To find an old version of a file, ask an agent in the project and give it this path. For example:

> “A copy of this project’s old history is in `/home/app-user/backups/cloud-….bundle`. Find in it the version of the file `src/…` from two weeks ago and show it to me, without changing anything in the project.”

Replace the path with the one in the message, and the file name with yours.

-   The app keeps the two most recent copies per project.
-   These copies disappear if the app’s environment is reset.

**Online.** The Cloud also keeps the old history for 14 days. During this period, support can find it: write to [support@vibestarter.pro](mailto:support@vibestarter.pro) with the project name and the date of the message.

### After a trim, on your other devices and in a team

The trim happens on a single computer. The project’s other copies follow on their own.

| Message shown | What it means | What to do |
| --- | --- | --- |
| “Project aligned with the trimmed backup” | The online history was trimmed from another device or by a teammate. Your project follows it; your changes are kept | Nothing |
| “Changes recovered” | Work saved before the trim, from another device or by a teammate, has been added to your project | Nothing |

In both cases, if the same file was changed on both sides and the two versions cannot be merged, **your version is kept**. The message names the files concerned: “For these files, the two versions did not match and yours was kept”. Compare them with your teammate or your other device if you were expecting one of these changes.

Before 3.6.3, these situations could block the backup, shown as “Offline”, or set work aside.

## The states you may see

| What is shown | What it means | What to do |
| --- | --- | --- |
| “Your code is saved and synced” | Everything is fine | Nothing |
| “Cloud backup pending” | Some local changes do not have a confirmed online copy yet | Leave the project open; the backup resumes automatically |
| “Syncing…” | An upload or a download is in progress | Nothing |
| “Team synchronization pending” | Your copy is saved, but the team’s work is not yet fully checked or integrated | Let the sync finish |
| “Changes received, waiting to apply locally” | The team’s version has arrived, not yet placed in your folder | Nothing, it applies on its own |
| “Publishing to the Cloud…” | Your work is saved, not yet in the online version | Nothing; Publish now restarts the upload straight away |
| “Offline — will retry automatically” | The server cannot be reached: no network, or the service is unavailable | Nothing, it restarts on its own |
| “Online backup interrupted — will retry automatically” | The online backup fails for a reason other than the network | See [below](/en/application/projet/sauvegarde/#the-online-backup-is-interrupted) |
| “Session expired — reconnect to sync” | Your account session has expired | Reconnect button |
| “Agent is resolving a conflict…” | Two changes cross, and an agent merges them | Nothing — see [Conflicts](/en/application/projet/conflits/) |
| “Conflict to resolve — launch an agent” | No agent is available to merge them | Launch an agent in the project |
| “Conflict still not resolved — check on the agent” | The conflict has been open for ten minutes | Check on the agent, or launch another one |
| “Maintenance mode — sync paused” | The project is parked on the version in production | Finish the fix in progress |
| “Online backup suspended — …” | The code alone exceeds the maximum size | Remove the files named in the message |
| “Sync stopped — you no longer have access to this project” | The owner removed you from the project | Your files stay with you; ask for a new invitation |
| “Sync stopped — this project no longer exists” | The owner deleted it from the Cloud | Your files stay with you; once reopened, your copy becomes a new project of yours |
| “Sync stopped — this project is no longer available” | The upload is refused, without a more precise cause | Your files stay with you; if it lasts, see [Get help](/en/aide/) |
| “Sync stopped — the local copy of this project is damaged” | Disk full, or file system error | Free up disk space, then reopen the project |
| “Sync paused — … not the same Roblox experience” | Owner: your copy points to another experience | Open the game’s place linked to this project in Roblox Studio |
| “Corrupt git object database” | Often after a sudden shutdown of the computer | Repair button: your files are not touched |

Repair removes what is damaged in the history and puts the project back on its last healthy version. **Your files stay as they are**: what you have changed since then goes into the next automatic backup.

Restoring from the Cloud erases your local changes

If repair is not enough, the app offers Restore from the Cloud. This button replaces the local copy with the latest online version. The changes that had not yet been sent are lost. It is a last resort.

## The online backup is interrupted

“Offline — will retry automatically” means one thing only: the app cannot reach the server. Either your computer has no network, or the service is unavailable.

“Online backup interrupted — will retry automatically” means something else: the server answers, but the backup fails because of the state of the project’s local copy. Before 3.6.3, these cases were also shown as “Offline”.

-   **During the first minute of consecutive failures**, the badge stays on “Syncing…”.
-   **After one minute**, it changes to “Online backup interrupted — will retry automatically”. The app keeps trying on its own.
-   **After five minutes**, a line is added. It says since when the backup has been failing, reminds you that “Your work stays saved on this computer”, and gives a technical detail.

What to do:

1.  Restart VibeStarter.
2.  If the state comes back, write to [support@vibestarter.pro](mailto:support@vibestarter.pro) and paste the technical detail shown in the line.

## Frequently asked questions

**Do I still need to save in Roblox Studio?** Yes. VibeStarter saves your code; what you change by hand in Studio goes through Studio’s own process. See [Sync, explained](/en/application/studio/synchronisation/).

**Why does the indicator stay on “Saved 4 min ago”?** This date matches the last backup confirmation received. A simple check without a new transfer does not reset it. The upload rhythm calms down when the project is at rest, and wakes up when you resume your work.

**What happens if I close the app in the middle of work?** The app tries to create a local version when the window goes to the background and before a normal close, even without a connection. This does not guarantee an upload to the Cloud before closing: check the badge if you want to get these changes back on another computer. At the next launch, the sync resumes on its own.

**And if I have no connection?** You keep working normally. The state shown is “Offline — will retry automatically”. Local versions keep being saved; the upload resumes when the network returns. The same state appears when the service is unavailable. A compile error does not block the backup of your code, but its publication to the shared version waits until the code compiles.

**Are my backups lost if my asset quota is full?** No. The quota applies to the community asset bank, never to Cloud projects.

**And my images, sounds, 3D models?** They are not uploaded, but the app keeps them in a daily archive of your projects, on your computer. If this archive fails, the backups screen says so. See [local archives](/en/application/projet/versions/#going-further-back-or-to-your-images-local-archives).

## Going further

-   [Where your project lives](/en/application/projet/)
-   [Going back to an earlier version](/en/application/projet/versions/)
-   [Switching computers](/en/application/projet/changer-d-ordinateur/)
-   [Where your assets go](/en/application/assets/ou-vont-tes-assets/)