# VibeStarter 3.6.0 > Public channel — documentation of app 3.6.3. Follow the availability notices of each service. Source: [VibeStarter 3.6.0](/en/nouveautes/app-3-6-0/) 3.6.0 follows 3.5.1. It makes it simpler to steer your agents and brings security fixes. The vocabulary is unified, the bars can be arranged the way you want, and there is now only one launch button. Once the version is released, the update from 3.5.1 will be offered when you launch the app: [Update the app](/en/application/premiers-pas/mises-a-jour/). **This update is mandatory.** As soon as it is out, earlier versions can no longer sign in to your account: the app takes you back to sign-in, which shows “Update required” and downloads 3.6.0. Install it, then sign in again. ## Fix 3.6.3: the save no longer gets stuck after a cleanup After the online history was trimmed, the save could stay stuck, shown as “Offline”, or bring back a conflict, even on a project you use alone. On a project opened on several devices or with a team, work could be discarded. - **The save resumes after a trim**, whether you work alone, on several devices, or with a team. The other copies of the project line up on their own and show “Project aligned with the trimmed backup”. - **Work from another device or from a teammate is recovered instead of discarded.** The message is “Changes recovered”. If the same file changed on both sides and could not be merged, your version is kept and the message names the files. - **The old history stays recoverable.** The app keeps a copy on your computer before each trim, and the message “Online backup trimmed” gives its path. See [Restore a removed version](/en/application/projet/sauvegarde/#recover-a-removed-version). - **“Online save interrupted” is a separate state.** “Offline — will retry automatically” only appears when the server cannot be reached. See [The online save is interrupted](/en/application/projet/sauvegarde/#the-online-backup-is-interrupted). - **Conflicts are now called “Version conflict”**, because they also happen between two of your devices. See [Conflicts](/en/application/projet/conflits/). - **The Restore button on each version is always visible**, without hovering. - **A failed local archive is flagged.** The Backups section shows “Your projects are no longer archived every day.”, with the cause and what to do. Several archives on the same day no longer push out those from earlier days. See [local archives](/en/application/projet/versions/#going-further-back-or-to-your-images-local-archives). - **On Windows, the acceleration help is limited to diagnosis.** The app no longer offers to turn acceleration on by itself. The button on the “Reduced performance mode” banner becomes View diagnosis, and the banner can be hidden. See [Turn on acceleration on Windows](/en/aide/demarrage/#enable-acceleration-on-windows). - Relaunching the app while it is already open no longer clears the logs useful to support. Update the app and keep your local project: it may contain changes that have not been saved online yet. If a conflict resolution was already open, let it finish, then check that the save is confirmed. If it stays stuck, [contact support](/en/aide/). ## Fix 3.6.2: more reliable Cloud backups On some projects, large files kept in older versions stopped the online save from moving forward. The automatic trim failed, and the app could show “Can’t reach the cloud” when preparing a release. 3.6.2 fixes this failure and strengthens the save: - The full code history is capped at **50 MiB**. If it grows too large, the app keeps recent versions in a rolling window. The current code is still kept; an old file that is too heavy no longer removes its current version. - Two computers signed in to the same account merge their changes before replacing the online copy. A save is only confirmed once it has been received. - The local history keeps recording offline. Code that does not compile can be saved; its integration into the shared version stays on hold. - The save time reflects the last real confirmation. The release assistant waits for the ongoing sync and reports the changes still pending. - Going back to an older version of the code keeps the media and ignored files present on your computer. **Files on your computer stay in place**, including models, images and sounds that are not part of the Cloud backup. See [the size limits and version retention](/en/application/projet/sauvegarde/#size-limits). Install the update, reopen your project, and check that the online save resumes. You do not need to delete your project or recreate it from the Cloud. To publish your game, keep the same path: [publish from Studio, then save the release](/en/application/studio/publier/). ## Fix 3.6.1: your older projects get their names back After the update to 3.6.0, projects created with an earlier version showed the name of their Roblox place instead of their folder name: several cards could carry the same title, or a title like “Untitled experience”. 3.6.1 restores the folder name, on the home page as in the Cloud. Your projects and their content have not changed. To find out which folder a card corresponds to, hover over its title. See [The project name does not depend on the place](/en/application/studio/lier-une-place/#the-project-name-does-not-depend-on-the-place). ## What’s new ### Documentation within reach A **Documentation** button stays visible in the app. The main troubleshooting screens open the relevant guide directly. The website also offers access from its navigation, the download page, the offers and support. Your agents can search and read the same published documentation, with a link to its source and the version concerned. See [Get help](/en/aide/). ### Consistent collaboration across several places A shared project now keeps a single Studio sync driver for its open places. The app flags the places that are still waiting for their version and no longer keeps an old “connected” state after a lost connection. A Cloud download blocked by local files is retried automatically. Two open projects can each have their own collaborators and driver. All participants must update the app and restart Studio. See [Working with others](/en/application/projet/equipe/). ### “Swarm” becomes “Agents” The word “Swarm” has disappeared from the interface. The tab is called Agents. The presets page has lost the word too: it is called Presets. The dialogs say “Pause the agents?” and “Stop the agents?”, and the resume banner says “Paused session found”, with the Resume session button. Nothing changes in how it works: these are the same tabs, the same panels and the same sessions. The word only lingers in old videos. See [Start and steer your agents](/en/application/agents/lancer-et-piloter/) and [Presets](/en/application/agents/prereglages/). ### One tab per open project Each open project becomes a tab in the top bar, with no setting to turn on: the + placed after the tabs opens another project alongside it, and a tab’s cross closes it. Each tab shows the project’s planet, a status dot (synced, Studio not connected, error…), its connected places and its agents at work; a card details it all on hover. Tabs are reordered by dragging them. Switching projects no longer stops the agents of other projects. Search becomes a compact key on the right (Ctrl +K). See [Several projects at the same time](/en/application/projet/power-mode/). ### Two bars you arrange yourself The top bar and the project bar are rearranged with the mouse. Drag an icon to move it from one zone to another, or off the bar to hide it; the + at the end of the bar restores what you removed. Back to the default bar undoes everything. In the top bar, you pin the destinations you use, six at most: presets, the subscription, the AI Studio, settings, your statistics. In the project bar, you also pin presets, which then launch in one click, and agents, which are added in one click. See [Find your way around the interface](/en/application/premiers-pas/interface/). ### One single launch button The Launch button has left the project bar. In its place, a floating pill at the bottom of the grid: Launch _N_ agents. It only appears once an agent has been added to the tab, and disappears as soon as the work starts. Above the grid, the Before launch strip shows what will apply to this launch: asset search mode, 3D model creation method, preview before adding. It also disappears once the agents are launched. ### Your favorite agent, within reach The first agent whose connection is confirmed becomes your favorite. Its icon is pinned by default in the project bar, and it is the one the app offers prominently when a tab is empty. See [VibeStarter’s AI agents](/en/application/agents/). ### The app suggests pinning what comes back When you often open or launch the same thing, a message appears: “_Name_ comes back often — Pin it to the project bar to have it one click away?” It offers two answers, Pin and No thanks. This counting happens on your computer and stays there; No thanks is final for that item. ### A shorter start The first-launch assistant goes from eleven to **ten steps**. The “AI agents” step disappears: you connect your AI account at the first launch of an agent, or from settings, and the first one connected becomes your favorite. The Roblox Studio step is reduced to its only decision, authorizing the plugin. The sign-in screen is now called Connect this computer and stresses what makes most attempts fail: “Open the link on this computer”, followed by “Opened on your phone, it won’t sign in VibeStarter.” See [The first launch, step by step](/en/application/premiers-pas/premier-lancement/). ### Choosing VibeStarter’s disk, on Windows The app now installs **on the disk you run its installer from**, and stores its heavy data there: agent environment, projects, backups, local library. To put everything on a disk other than `C:`, move the installer file onto that disk before running it. On Mac, drop the app onto the wanted volume before its first launch: storage follows that volume, with no folder choice in the assistant. The chosen path appears under the Storage folder heading, at first launch and in Settings → Storage. Storage that is already in use does not move. See [Install on Windows](/en/application/premiers-pas/installer-windows/) and [Where your data is on disk](/en/application/reglages/donnees-sur-le-disque/). ### Your model sources stay in the project When an agent builds a 3D model for an open project, its Blender source and its render are stored in the project folder, before being sent to Roblox. They stay there with the code, on this computer, and are included in your project archives, in the Backups section of the Storage tab in settings. The online save, which only carries code, does not contain them. See [3D models](/en/application/assets/modeles-3d/). ### Tracked cancellations and clearer refunds The cancellation of AI credits is sent automatically to the payment provider. The app distinguishes a pending request from an accepted stop: the period already paid stays available until it ends. Tracking continues when you close the app. See [Cancel](/en/offres/resilier/). Refund requests are still reviewed by support. For the Solo or Duo purchase, the request must be made within 14 days of the initial purchase; its processing may happen later. The process covers a full refund when paid in full, or a refund of the first installment collected and the stop of the following ones when paying in installments. Confirmations of stop and of refund are separate: [Invoices and refunds](/en/offres/factures-et-remboursement/). ### Withdraw within 14 days The Plus or Pro subscription, the tier upgrade and the credit packs now have a 14-day right of withdrawal from the first payment of an order. Before paying, a separate checkbox asks for immediate access. In your account area, open the Purchases and payments tab and click Cancel and get a refund on the purchase concerned. The withdrawal page shows the amount refunded and the share of unused credits, and has the Withdraw from the contract here button. The same process handles the refund of the app purchase, which keeps its own policy. Monthly renewals do not open a new period. See [Withdraw within 14 days](/en/offres/retractation/). ## Services around 3.6.0 **No per-game product ships with this version.** Community, which will open the [wiki](/en/services/wiki/) and the [Discord for your game](/en/services/discord-du-jeu/), stays “Coming soon”, with no date announced. So 3.6.0 shows neither the Community tab nor its pin. **Analytics, the Thumbnail pack and the Starter pack do not ship either.** The [analytics](/en/services/analytics/) and the [thumbnail service](/en/services/miniatures/) stay “Coming soon”, with no date or price announced. You can already create thumbnails and icons with [the AI Studio](/en/application/assets/atelier-ia/): this feature is separate from the future Thumbnail pack. All four products are described in [Services for your game](/en/services/#products-per-game). ## Day to day - **The white screen fixes itself on Windows.** After three close graphics crashes, the app restarts once in compatibility graphics mode and keeps that mode. The PowerShell procedure is no longer needed — see [The app won’t start](/en/aide/demarrage/). - **Without hardware acceleration, the app says so and pauses Blender.** A “Reduced performance mode” banner appears: “Acceleration inactive: reduced performance and new Blender computations unavailable.” Agents, editing and sync remain accessible; Blender models already created can still be viewed. The View diagnosis button (Fix the problem before 3.6.3) opens the settings, on the Application tab, in the VM acceleration section. See [The app won’t start](/en/aide/demarrage/). - **A forced update installs by itself.** From 3.6.0, an “Update required” screen replaces the rest of the app, installs the requested version, then restarts. See [When an update is mandatory](/en/application/premiers-pas/mises-a-jour/#when-an-update-is-required). - **A project keeps its account.** On a shared computer, a project created with another VibeStarter account shows the mention “Other account” and does not join your Cloud. See [Several accounts on the same computer](/en/application/projet/changer-d-ordinateur/#several-accounts-on-the-same-computer). - **On Windows, the app folder is reserved for your Windows account.** The installer therefore refuses an exFAT or FAT32 disk, which cannot do that. See [Install on Windows](/en/application/premiers-pas/installer-windows/). - **The wait for the sign-in link stops after ten minutes**, with the message “The login link has expired” and the Send a new link button. - **The app warns when the agents’ temporary space fills up**: “Agent temporary storage is almost full”. See [Where your data is on disk](/en/application/reglages/donnees-sur-le-disque/). - **The app no longer runs a file opened from it.** Documents, media and Roblox files open; a script or an executable is shown in its folder. - **An agent launch that fails says so.** The error message appears on the page, and no longer only in a terminal that does not exist yet. - **The favorite agent is no longer picked at random.** Only a connection that is truly confirmed counts, instead of the first probe that responds. - **The referral is kept** when you open a purchase from the app. Before paying, check the referrer shown in your account: [The affiliate program](/en/offres/affiliation/). - **The side panel opens on the side where its icon is** in the bar. - **A skewed clock is named.** When your computer’s time is too far off, the server refuses your session. A banner says so, with the gap when it is known and the Retry button, instead of asking you to sign in again. See [I can’t sign in](/en/aide/connexion/). - The Source control panel is called Versions, and Team and settings is called Team. - When you create a project, the Project name field becomes Game name. - **Linking a place no longer renames your project.** It keeps the name entered in Game name, even after a second world is linked. See [Link a place to your project](/en/application/studio/lier-une-place/#the-project-name-does-not-depend-on-the-place). - **A project carries the same name everywhere**: tab, card, the “Roblox Studio” banner, the Ctrl + K search, the Mention a project window, delete confirmations, “Recent activity”. The “Project ready!” screen shows this name, then “Folder: …”. The Cloud carries it too: an invited teammate, or your other computer, sees the game name on the invitation and on the Open here card, before opening the project. - **Unlink asks for confirmation**, and each place of another experience has its own button in Project places. The home banner only offers it when a single place of the project is open. - **Opening a project says what it is waiting for.** A normal start shows “Connecting to Studio…”, on the opening screen as on the tab, without a warning triangle; “Almost ready — finish in Studio” only appears if you have an action to take. The tab follows the same steps, from “Opening…” to “Synced with Studio”, and goes back to “Open, Studio not connected” when you close Studio. A project without a linked place asks “Open a place in Roblox Studio”. Three cases have their own message: Studio open on another project, sync port already in use, app and Studio plugin on different versions. See [The Roblox Studio connection isn’t working](/en/aide/studio/). - **A compile error with no agent running is stated as it is**: “The code doesn’t compile”, with the steps to follow — launch an agent or fix the file. “Compile fix in progress” only appears if a code agent is running. The opening screen, the publishing assistant and the Versions panel follow the same rule, and “Publishing on hold” disappears as soon as the code compiles again. Once the place is open, “The code doesn’t compile right now” is the title of the opening screen, and its bar shows “Sync on hold”. - **A terminal is no longer counted as an agent.** The tab card shows “1 agent · 1 terminal”, and “Close the project?” names the project it is about to close. On the home page, the card of a project that has only terminals shows “Terminal open” instead of “Agents running”. - **Deleting a project says what remains.** For a project saved in the Cloud, the confirmation is titled “Delete the local copy?”: the project stays in the Cloud and reopens with Open here, on its card, which appears straight away. For a project the Cloud does not have, it warns that the project will be “lost for good”. See [Delete a project, or detach it](/en/application/projet/#delete-a-project-or-detach-it). - In Versions, the versions created by the app have a readable label, and their age is shown in the app’s language. A restore that changes no file shows “Nothing to restore”. - In the first-launch assistant, the Hardware step ends with Continue instead of Start the environment. - The interface now speaks directly to you on many screens that still used a formal tone. ## What was removed - **The “AI agents” step of the first-launch assistant.** Sign-in happens at the first launch of an agent, or in Settings → Agents & tools. - **The Launch button of the project bar**, replaced by the launch dock. - **The three fixed destinations of the top bar**, replaced by your pins. - **The Power Mode setting (“Multi-project tabs”)**, now useless: several projects always open in tabs. The status strip in the middle of the top bar also disappears; each project’s status is on its tab. - **The Roblox admin ID field** when creating a project.