Working together on a project

Collaboration is not behind any paid tier: it is included for every VibeStarter member.

A project saved online can be shared. You invite someone by their email address, they join the project, and your two computers work on the same version of the code without anyone having to send files to each other.

Before you start

One license per person

The Terms of Service are explicit: “The use of the Service is strictly personal: one license corresponds to a single account, used by a single natural person. To use VibeStarter with several people, each person must have their own license.” Each access in the Duo offer is a separate license, meant for a separate person, and the collaboration features apply between holders of separate accounts. See the Terms of Service.

Your collaborator therefore needs their own VibeStarter account and the app installed on their computer. The project must also be saved online: if it isn’t yet, the panel shows “Project not hosted yet” with the Open Source Control button.

When the game belongs to a Roblox group

The order matters, because Roblox and VibeStarter each check on their own side.

1. The owner of the VibeStarter project must be the owner of the Roblox group. Roblox only offers a group on the consent screen to its owner; a member, even with all permissions, cannot authorize uploads on behalf of the group. See Link your Roblox account and your Open Cloud key.
2. In the group on Roblox, you give each teammate a role that allows editing experiences, so Studio lets them open and publish the place.
3. You invite them to the VibeStarter project, as described below.
4. You check Let the team publish in my name in the Team panel, then confirm with Allow. Without this box, their uploads are refused with “Publishing reserved to the owner”.

Invite someone

1. Open the project, then, in the project bar, the Team panel. The sync panel also offers a shortcut, Share with your team.
2. Under Invite, enter the person’s email address.
3. Click Invite. The confirmation shows “Invitation sent to …”. If the email could not be sent, the app says so instead: “Invitation created, email not sent”. The invitation still exists: tell your invitee, they will find it on the app’s home screen.
4. The person appears in the Collaborators list with the “Pending” badge until they accept.

How an invitation works

1. You inviteTeam panel, email address, Invite button.
   email
2. Your invitee receives a linkThe message is in English, with the subject “Invitation to …”.
   click
3. VibeStarter opens on their computerEven if the app was closed. If they are not signed in, the invitation is kept aside until they sign in.
   accepted
4. The project is in their listThey join as an Editor and receive the code with its history.

The invitation exists as soon as you click Invite. Even if the email does not arrive, your invitee finds it in their project list as a dashed card, with the Join the project button.

On the invitee’s side, two paths lead to the same result: click the link in the email, or open the project list and click Join the project on the dashed card “Invitation · Editor · from …”. The card shows the game’s name, not the name of its folder; so do the confirmation “Invitation accepted — …” and the email. For a project hosted before 3.6.0, this name only appears after the project has been synced by one of its members: until then, the invitation shows the folder name.

The account that accepts must have the same email address as the invitation. With a different address, the acceptance is refused. The panel reminds you of this below the address field.

Once the invitation is accepted through the link, the “Invitation accepted” notification offers

Open: the project is copied to the invitee’s computer and opens.

The invitation does not give access to the Roblox place

VibeStarter shares the project’s code, not the Roblox rights. To open the place in Studio, your invitee must have access on the Roblox side. If there is nothing for them to open because a teammate is already driving Studio, the app tells them; otherwise it tells them to ask the owner for access.

The two roles

There are only two roles, and an invitation always gives the Editor role.

Action	Owner	Editor
Work on the project and sync it	yes	yes
See the project’s members	yes	yes
Invite a collaborator	yes	no
Remove a collaborator	yes	no
Delete the project from the Cloud	yes	no
Rename the project	yes	no
Set the project’s Roblox context	yes	no
Publish assets on Roblox	yes	only if the owner allows it
Create a game pass or a developer product	yes	never

The project name is the name field of the vibestarter.json file, at the root of the project: the owner changes it there, or asks an agent to, and the whole team receives the new name. If an editor (or their agent) changes this field, the app puts back the team’s name in their copy and shows “Only the owner can rename the project”.

The project’s Roblox experience

A shared project belongs to one Roblox experience: the one of the place that the owner linked and opened in Roblox Studio. That is the experience the team’s publications target, and only the owner can change it.

• Editor: you can link a place from another experience to the project, for example your own test place. The code syncs there, but the project’s experience changes neither for you nor for the team, and you can Unlink it at any time, after confirmation (“Unlink this place?”): the code already sent stays there. If the owner changes experience, your copy follows on its own at the next sync.
• Owner: to change experience, link the new place to the project and open it in Studio. If the app shows “Sync paused — this folder and its Cloud project do not point to the same Roblox experience”, your copy and the project no longer agree: open the game’s place, linked to this project, in Studio. The project follows this place and the sync resumes on its own.

Let the team publish in your name

By default, only the owner publishes to Roblox. The Team panel offers the option

Let the team publish in my name, called Publish in my name on the collaborator’s side. Once it is turned on, editors read “The owner allows publishing in their name — you can publish.”; otherwise they read “Publishing reserved to the owner”.

Ticking the box is not always enough. Under “For it to work for your teammates:”, the owner’s card lists what is still missing, with its status:

• their Roblox account is linked to VibeStarter;
• the game is linked to the project: the owner has opened the published place once in Studio, with the project open in their app;
• the game belongs to the Roblox account they linked, or to a Roblox group they own (the app cannot check this last point).

As long as one of these points is missing, the card shows “Allowed, but not possible yet” instead of “Publishing allowed”, for the owner as well as for editors.

Monetization is never delegated

The app says so to both sides: “Game passes and developer products are created by the owner only, even when publishing assets in their name is open to you. This is not an API key matter.” This authorization only covers publishing assets.

What you see of each other

• Who is online: the badge shows “1 teammate online”, and the name of the person who has Roblox Studio open.
• Who drives Studio: the project tab shows “X syncs Studio”, with “X is connected to Roblox Studio and syncing this project — nothing to open on your side.” Only one member drives the live Studio sync at a time. The foot of the Team panel names the current driver, “X drives Studio”, or “No one is driving Studio at the moment”: this is not necessarily the owner.
• Who integrates the changes: “X integrates the changes”, and “X seems stuck” if work is waiting to be integrated and this computer has not moved forward for 30 minutes. If your own work waits too long to be integrated, the app tells you: see When your work is waiting on someone else.

See When two changes cross for what happens when your two works overlap.

Several places, one Studio driver

For an experience with one, two, three or four places, the app assigns the Studio sync to a single computer for the whole project. The first collaborator signed in to Studio takes this role; opening another place on someone else’s computer does not create a second driver.

Open the places to sync on the driver’s computer. If a place is open elsewhere and is not synced by them, the app lists the places waiting. The project is ready when all known open places have received the same version. Closed places of the experience are not checked.

To hand over, the driver closes the Studio windows for this project. The takeover on the other computer can take about thirty seconds. A network outage can also pause the sync temporarily: the app waits for recent proof before declaring the project ready.

All participants must have updated VibeStarter and restarted Studio to load its plugin. An old version on one of the computers does not benefit from this shared assignment.

Two collaborations at the same time

With two projects open, you can work with one person on one project and another person on a second project. Each keeps its teammates, its backup and its Studio driver. Closing the first project does not interrupt the second.

The person who integrates the code changes can be different from the Studio driver. If their app stays connected but no longer progresses, another collaborator can take over. A short delay protects the sends already in progress.

Remove someone, or cancel an invitation

Situation	Button	What is shown
The person has joined the project	Remove access	“Remove access?” — “… will no longer have access to this project.”
The invitation is not accepted	Cancel the invitation	“The invitation sent to … will be cancelled.”

Access is cut immediately. The local copy the person has on their computer stays with them: their app shows “Sync stopped — you no longer have access to this project” and the copy is no longer shared. If they open it again, this copy is saved online as a new project under their name, separate from yours.

The owner cannot be removed from the project.

Limits

• Two people do not work on the same task. The code merges on its own; two different designs of the same feature, no.
• Code written outside VibeStarter will be overwritten. An associate without a license who modifies the files with another tool is not in the loop.
• Only one person drives Roblox Studio at a time on a given project.
• The invitation email is in English, but the app is in French.
• Invitations are limited to 30 per hour per account, and to 10 per hour for the same recipient address.

Frequently asked questions

Does my collaborator need VibeStarter Plus? No. Cloud and collaboration do not depend on any subscription. They need their own app license and their own access to a coding AI.

How long does it take for my teammate to receive what I change? About a minute when you both have the project open. It can rise to six minutes when the computer that integrates the work has just changed: the new one waits for the previous one to finish writing. Nothing to do, it works on its own.

My invitee does not receive the email. The invitation still exists: ask them to open their project list in VibeStarter, the invitation card is there. When the email could not be sent at all, the app warns you at the time of the invitation.

Can my collaborator see my code? Yes, that is the principle: the project’s content is shared between the project’s members, and no one else. See the privacy policy.

My teammate gets a permission error when publishing an asset. Go through the four steps of When the game belongs to a Roblox group: group owner, role in the group, invitation, box ticked. It is almost always the first or the last one that is missing.

What happens to the work of someone I remove? What they had already sent and that has been integrated is part of the team’s version and stays there.

Going further

• When two changes cross
• Where your project lives
• Link your Roblox account and your Open Cloud key
• Your account and your data