# Roblox Studio connection doesn't work

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

Source: [Roblox Studio connection doesn't work](/en/aide/studio/)

VibeStarter talks to Roblox Studio through a plugin, `VibeStarter Sync`, which the app installs itself every time it starts. You don’t have to install anything or turn anything on in the Studio menus. When the connection fails, the message on screen almost always tells you what to do: look for yours in the tables below.

## The three habits that fix most cases

1.  **Open a place in Studio.** The plugin attaches by itself within a few seconds, but only if a place is open.
    
2.  **Restart Roblox Studio after each VibeStarter update.** If Studio was running during the update, its plugin is out of date and the connection goes nowhere.
    
3.  **Close the Studio windows you aren’t using.** Several open windows slow down the analysis of the place, sometimes to the point where it fails.
    

## The plugin doesn’t attach

| What the app says | What to do |
| --- | --- |
| Studio is open, but VibeStarter’s plugin is not attached yet | Open a place. If it never attaches, close and reopen Roblox Studio. |
| Sync plugin out of date — relaunch Roblox Studio | Close Studio and reopen it. The app installs the updated plugin when it starts. |
| Auto-connecting… that never finishes | Restart Studio. If it keeps happening, check that the open place is linked to the project. The plugin has no connect button. |
| VibeStarter’s Studio channel could not start | Another program, or a VibeStarter that is still open, is using the ports the app reserves for Studio (34873 to 34877). Close it, then restart the app. |
| Taking longer than expected. Check that Studio responds and close unused Studio windows. | Keep only one Studio window open, and check that no game test is running. |
| App update needed — the app and its Studio plugin are not on the same version, so sync can’t start. | The VibeStarter installation is incomplete or only partly updated. Update or reinstall VibeStarter, then restart Roblox Studio. Nothing to do in Studio. The same title stays on the project tab, with a red dot. |
| VibeStarter Sync failed to start. — The sync port for this project is already in use, often by a previous session that is still closing. | Click Retry on the line. If it happens again, close the project and open it again. For another cause, the line shows the error after “Message from VibeStarter Sync:”. |
| In the Studio output: “VibeStarter answered, but this copy of its Studio plugin does not hold the app’s current installation credential.” | The plugin Studio loaded is not the one the app installed. Restart Studio. If the message comes back, click Check and repair the plugin in Settings → Workspace, then restart Studio. |
| During a game test, in the Studio output: “VibeStarter answered, but no account is validated in it yet” | The app hasn’t validated your account yet. Sign in to VibeStarter. The plugin then attaches by itself. |

## The open place isn’t recognized

| What the app says | What to do |
| --- | --- |
| The open place isn’t linked to this project | Click Link this place. |
| A different place is open — open this one instead | Open the place shown. Use this place links the one that is open, but **detaches it from its original project**. |
| Studio is open on …, another project open in the app. | All the Studio windows belong to a project open in another tab. Open this project’s place in Roblox Studio: it connects by itself. To use a place that is already open here instead, first close the tab of the project using it. |
| Working without a confirmed place | Your code still syncs; Studio hasn’t confirmed yet which place it is. Leave the place open. |
| A place published a moment ago is no longer recognized | Publishing a draft changes its identity on Roblox. The plugin reattaches by itself from version 1.0.13; restart Studio if needed. |
| A second world doesn’t appear | Publish this place at least once, or link it by hand from Project places. |
| This place already contains scripts | You are creating a project on a place that is not empty: the app warns you that it will write an identity marker to it. |

## We are two on the project

| Situation | What to do |
| --- | --- |
| Two people are syncing this project | **Only one person drives all the places.** Otherwise the two versions diverge. |
| Studio shows that another person is syncing this place | This is the Team Create lock. Wait: the connection happens when the other person stops. |
| A test session is taken over by someone else | Only one game test per experience. Start tests from the app: two manual launches are not protected. |
| “Sync on hold — … not the same Roblox experience” | Only the owner sees this: they open the game’s place linked to this project in Studio, and the sync resumes. |

## The code doesn’t reach Studio

| Situation | What to do |
| --- | --- |
| My changes made in Studio have disappeared | The sync goes **one way only**, from the app to Studio. Edit the code in the app. In Studio, `Ctrl+Y` (or `⌘+Y`) right after the cancel alert recovers what was just overwritten. |
| The code doesn’t compile right now | It’s not blocking: Studio keeps the last valid version. Open place, it’s the title of the opening screen, and its bar shows “Sync on hold”. An agent working on the code fixes the error; if none is running, start one or fix the file yourself. |
| Compilation ran out of memory | Read the sentence under the title. “Compilation memory insufficient”: ask an agent to adjust the project’s compilation limit; **closing agents does not raise this limit.** “Out of available memory”: close unused agents or projects, then request a new compilation. |
| The agent says it can’t act in Studio, even though the code arrives | In Settings → Workspace, the plugin card shows “Studio tools not loaded yet” and the reason. Check your Internet connection, then click Check and repair the plugin. |
| I wrote my code, but players don’t see anything | Publishing is still a step in Studio: File → Publish to Roblox, for each world. |
| My images and sounds are not in the backup | The online backup only includes the code. Media lives on your computer, and on Roblox once published. |

## Captures and game tests fail

| Situation | What to do |
| --- | --- |
| A capture is refused in `Run` mode | `Run` has no client: ask for a test in `Play` mode. |
| A capture is refused in a multiplayer test | Do a `Play` with a single player for the visual check. |
| The capture times out, or a simulated click does nothing | A minimized Studio window pauses its rendering. Restore the window and run the action again. |
| An agent is waiting its turn for Studio | Only one agent drives a place at a time. The others keep working on the code while they wait. |

## Publishing an asset or a product fails

| Situation | What to do |
| --- | --- |
| The asset goes to my personal account instead of the group | The owner of the place must be readable: link the place, open it, and publish it at least once. |
| Roblox refuses an upload for lack of permission, even though I have rights in the group | Only the **owner** of the group can authorize VibeStarter for that group, on the Roblox consent screen. A member goes through the invitation to the project and the checkbox “Let the team publish in my name”. See [Working with others on a project](/en/application/projet/equipe/#when-the-game-belongs-to-a-roblox-group). |
| Roblox says the scope is not allowed | Your Open Cloud key must have the Game Passes and Developer Products permissions, for both reading **and** writing. |
| Monetization was working, then stops for no reason | Roblox disables an Open Cloud key after **60 days without use**, even if it was set to never expire. Create the key again and paste it in. |
| A ninth project won’t open | Sync handles up to eight projects at the same time. Close one of them. |

## Limits

-   **The sync goes one way.** The code is written on the VibeStarter side; the 3D world is built in Studio, by hand or by agents, and lives in the place.
-   **A place that has never been published has no identity on Roblox**: it is recognized only by the marker the app writes.
-   **The plugin and the app work as a pair.** A plugin older than the app refuses the actions it doesn’t know — which is why you restart Studio after each update.
-   Nothing guarantees that a future version of Roblox Studio will keep the same behavior: changes on the Roblox side have broken the connection before.
-   Capture and game test measurements were made on Windows. On Mac, these same features are not guaranteed to work the same way.

## Going further

-   [Connect VibeStarter to Roblox Studio](/en/application/studio/)
-   [Sync, explained](/en/application/studio/synchronisation/)
-   [Link a place to your project](/en/application/studio/lier-une-place/)
-   [Publish your game and track your versions](/en/application/studio/publier/)
-   [Link your Roblox account and your Open Cloud key](/en/application/studio/compte-roblox/)