Where your data is on disk

VibeStarter writes to two places: a profile folder, with your preferences and logs, which always stays in your user profile, and a storage folder, with the agents’ environment, your projects, your backups and your local library.

The storage folder

This is the one that grows. The app calls it Storage folder and summarizes its contents as “Your projects” and “Their backups”. Its path is shown in plain text at the

Hardware step of the first launch and in Settings → Storage.

Windows

It follows the drive of the installer. You are not asked anything: the app installs on the drive its .exe was launched from, and its data\ folder goes below it. The Hardware step shows this path with the note “Chosen automatically”. Data that is already there keeps its location, and some preferences and caches stay in the Windows profile.

The drive is therefore chosen before installation. See Install on Windows.

Mac

It follows the volume where the app is installed. Same rule as on Windows, without a question. In Applications, on the system drive, the storage folder lives in your personal library. On another volume, the app creates a Vibe Starter Data folder next to it. To put everything on an external drive, drop the app onto that drive rather than into Applications, before the first launch. Settings and some caches stay in your personal library.

The choice locks as soon as you work

Once projects, assets or Blender workshops have been written, the folder is locked: “This storage is already in use. Your data stays in its current location; moving it is not available here.” There is no feature to move a storage that is already in use.

If the drive is unplugged at startup, the app does not recreate anything elsewhere. It shows “The selected storage folder is unavailable. Reconnect the drive and restart VibeStarter; your data will not be replaced.”

The folders

Windows

User profile — always on the system drive
%APPDATA%\com.ert.vibe-starter\
└── settings.json          your preferences

%LOCALAPPDATA%\com.ert.vibe-starter\
├── logs\                  app logs
└── secure-store.json      local secret vault (credential store fallback)

Storage folder — on the installer’s drive
<program folder>\data\
├── vm\                    agent environment, projects, local backups
├── library\               local asset library
└── blender-workshop\      Blender work

Mac

On the system drive:
~/Library/Application Support/com.ert.vibe-starter/
├── settings.json          your preferences
├── secure-store.json      local secret vault (credential store fallback)
├── vm/                    agent environment, projects, local backups
├── library/               local asset library
└── blender-workshop/      Blender work

On another volume:
<app folder>/Vibe Starter Data/
├── vm/
├── library/
└── blender-workshop/

Settings: always in Application Support, as above
~/Library/Logs/com.ert.vibe-starter/   journaux de l’application

A project has no separate folder on your disk: it lives in the agents’ environment, the vm folder. It also contains its own working files, including the saved test scenarios, stored in its .vibestarter/tests/ subfolder.

Sources and temporary files

The useful sources needed to resume work (editable sounds, scripts, models and reports) must stay in the project. You can ask the agent to keep them before finishing. Media kept on your disk is not automatically backed up online.

The general temporary space of the agents uses the disk, with a limited capacity. It is emptied when their environment restarts. The app does not clear this space during a task. This cleanup does not touch files kept in the project.

If the app shows “Agent temporary storage is almost full”, ask the agents to keep the useful sources in the project and to delete their own unneeded temporary files. Do not delete the files of another agent that is still working.

Your logs

File	Contents
Vibe Starter.log	The current session
Vibe Starter.previous.log	The previous session
crash-<timestamp>.log	A crash report, if there was one

Each file is capped at 20 MB.

The log starts over at each launch

At launch, the app shifts the current log to Vibe Starter.previous.log and starts writing again. After an incident, retrieve both files before launching a second time: the second launch erases the trace of the incident. The steps for reporting a problem are in Find your logs and report a bug.

The Storage tab

The Settings → Storage tab brings together four sections.

Storage usage and management. The detail of what the app takes up: local library, shared assets and online project backups. The section also shows the path of the

Storage folder, read-only: it cannot be changed from the settings. Online code backups are not subject to the asset quota: they are two separate counters.

Asset destination. Two separate choices, one for generated assets and one for imported assets: stay local, or share with the community. The setting applies to the next assets and does not move what is already published. See Where your assets go.

Downloads. The folder where the app drops what you download. It must stay inside your Downloads folder: the app shows “Choose a folder inside Downloads.”

Backups. Daily archives of your projects, kept on this computer, with the two buttons

Back up now and Restore. Restore opens the “Restore from this archive?” window, where you tick the projects to put back in their state of that day. An archive contains the whole project (code, images, sounds, models), except the folders it rebuilds on its own (node_modules, out…). If the automatic archive fails, the section shows “Your projects are no longer archived every day.”, with the cause and what to do. The full procedure is in Go back to a previous version.

What is backed up elsewhere, and what is not

What you have	On your disk	Backed up online
Project code	Yes	Yes. See Your code is saved automatically
Project images, sounds, 3D models	Yes	No
Local asset library	Yes	No, and no sync between machines
Preferences and logs	Yes	No

A project cannot be copied from your file explorer: it lives in the agents’ environment. What gets set aside on your disk is an archive from the “Backups” section, or the entire vm folder with VibeStarter closed. See Switching computers.

Limits

• A storage that is already in use cannot be moved, either from the app or from the settings.
• The drive is chosen by installing the app on it, not inside the app: run the installer from that drive on Windows, drop the app onto it on Mac.
• The local library does not sync between your machines.
• The local secrets vault is not a place to edit by hand. See Your API keys and credential store.
• Deleting an asset from your local library does not delete the asset already published on Roblox.

Frequently asked questions

VibeStarter takes up a lot of space. This is expected. The agents’ environment, the projects and the local library live in the storage folder. Plan for the recommended 20 GB. See Check that your computer is compatible.

Can I move the storage folder somewhere else? No, not once it contains data. The choice is made at the very start, by installing the app on the drive you want.

Does the uninstaller remove my storage folder? No, it keeps it. On Windows, however, its data deletion checkbox erases the profile folder, where an installation from before 3.6.0 may also have stored its projects. See Uninstall VibeStarter.

Can I delete the contents of logs? Yes, they are logs. Keep them if you have an incident to report.

Are my projects lost if I uninstall? No, as long as you leave the data deletion checkbox of the Windows uninstaller unticked. See Uninstall VibeStarter.

Going further

• Your code is saved automatically
• Where your assets go
• Find your logs and report a bug