# Several projects at the same time

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

Source: [Several projects at the same time](/en/application/projet/power-mode/)

Each project you open becomes **a tab in the top bar**. Several projects stay open side by side, each with its own agents and its own sync with Roblox Studio. Switching from one tab to another, or going back to the home screen, stops nothing: the agents of the other projects keep working, and their online backup and your teammates’ presence keep going.

There is nothing to turn on. Before, this way of working was a beta setting, “Power Mode”: it disappeared in 3.6.0, and opening a project always adds a tab.

## Open another project

1.  Click the + placed after the project tabs, in the top bar.
2.  Choose a project in the Open another project menu. Each project there shows its planet; the ones already open in Roblox Studio come first. All projects takes you back to the home screen.

Opening a project from the home screen or the command palette adds it in the same way. A project that is already open is not duplicated: the app switches to its tab. On the home screen, the cards of open projects show the mention Open. When everything is open, the menu says so: “All your projects are open.”

## Read a project tab

Each tab shows the state of its project, whether it is on screen or not. It shows the project’s **planet** (the same as on its home screen card), the **number of connected places** (screen icon) and the **number of agents and terminals running** (robot icon, or terminal icon when the project only has terminals). When agents are working, a halo surrounds the planet.

A **badge** on the planet shows the worst state in progress:

| Badge | What it means |
| --- | --- |
| Red | The sync is interrupted, a compile stopped for lack of memory, the app and its Studio plugin are not on the same version, or the Studio channel is stopped |
| Orange | The code does not compile (ask an agent to fix it, or start one), a team conflict is waiting, or a Studio notice needs an action, for example when a teammate is playing |
| Pulsing | Opening in progress, or waiting for Studio: nothing to do |
| Green | Synced with Studio |
| Gray | Open, Studio not connected |

A small triangle follows the project name when the badge is red or orange. The status in words then gives the cause: “Sync interrupted”, “App update needed”, “Out of memory”, “Version conflict pending”, “Compile fix in progress” when a code agent is running in the project, “The code doesn’t compile” when none is running, or the project’s Studio notice shown on screen (for example “Waiting for place synchronization”, when a teammate is playing).

A normal start is not an alert. The pulsing badge appears without a triangle, and the tab follows the steps of the opening screen, in this order:

| The tab shows | What happens |
| --- | --- |
| “Opening…” | the app prepares the project: code, tools, dependencies, first compile, start of VibeStarter Sync |
| “Connecting to Studio…” | the project is ready and its place is open in Studio: the plugin connects |
| “Sending your code to Studio…” | Studio is connected, the code goes out |
| “Synced with Studio” | Studio has received the project: the badge turns green |

If no place of the project is open in Studio, the tab goes from “Opening…” to “Open, Studio not connected”. When you close Studio, it also goes back to “Open, Studio not connected”: “Connecting to Studio…” only appears if a Studio window responds. The plugin that re-attaches follows the same rule as the start: “Checking Studio”, “Plugin re-attaching”.

During a closing, a launch, a pause or a stop of agents, a spinning indicator replaces the badge on the tab of the project concerned.

**On hover**, a card details everything: state in words, places, agents, last sync. It counts agents and terminals separately: “1 agent · 1 terminal”, or “1 terminal” for a terminal alone. For the project on screen, it adds its notices — Studio channel not connected, sync or compile problem, places driven by a teammate or by an agent — and the

Reconnect Studio button when possible. The number of places on the tab on screen opens the places menu: link a place, see who drives what.

## Organize your tabs

-   **Reorder**: drag a project tab to the position you want.
-   **Many projects open**: the tabs shrink until they only show their planet, then the last ones move into a … menu.
-   **Sessions of a project**: the project bar, below the top bar, shows the agent tabs of the project on screen, and nothing from another project. Its + adds a session to this project. Closing its last session leaves an empty session: closing a session never closes the project.

## Close a project

Click the cross on its tab, or click it with the wheel. If agents or terminals are running, the app asks for confirmation, naming the project: “Close the project?” — “The agents and terminals of ‘…’ stop, and its sync with Roblox Studio too.” Closing a project stops its agents and its sync; the other projects do not move.

## What is specific to each project

| Specific to each open project | Follows the project on screen |
| --- | --- |
| The agent tabs and paused sessions | The side panels: versions, notes, team |
| The sync with Roblox Studio | The session resume banner |
| The compile state and the presence of your teammates |  |
| The online backup and its indicator |  |
| The conflict resolution and the Studio driver |  |

You can collaborate with two different people on two open projects: the members and the Studio driver of each project stay independent. See [Working together on a project](/en/application/projet/equipe/#two-collaborations-at-the-same-time).

## Limits

-   **Eight open projects at most.** The ninth is refused. If a sync slot is already taken by other software on your machine, the real limit may be lower.
-   **No project switching during a launch or stop of agents.** Wait for the operation to end; agents that are running, however, do not block anything.
-   **Only one playtest at a time per Roblox experience.** Two places of the same experience cannot be tested together: Roblox Studio kicks out the first. Two different experiences, on the other hand, can be played at the same time, including from two open projects side by side. See [Several worlds in one game](/en/application/studio/plusieurs-mondes/).
-   **No walls between projects.** Open projects share the same environment and the same memory: there is no security isolation, and no memory budget reserved per project. Two projects loaded with agents share the same machine.

## Frequently asked questions

**Where did the Power Mode setting go?** It was removed in 3.6.0: what it turned on became the normal way of working. You have nothing to do; an old saved setting is simply ignored.

**How do I go back to a single project?** Close the tabs of the other projects. With a single project tab, the app behaves as before.

**How many agents can I run across several projects?** The limit is your machine’s memory, not the number of projects. See [Launch and steer your agents](/en/application/agents/lancer-et-piloter/).

**Do I need to open several projects to work on several worlds of the same game?** No. Several places of the same experience belong to a single project: [Several worlds in one game](/en/application/studio/plusieurs-mondes/).

## Going further

-   [The interface, zone by zone](/en/application/premiers-pas/interface/)
-   [Where your project lives](/en/application/projet/)
-   [Sync, explained](/en/application/studio/synchronisation/)
-   [Have an agent test a feature](/en/application/agents/playtest/)