VyroAI

Loading...

Split Screen — Up to Four Projects at Once

Player slots like a video game: two projects side by side or stacked, four in a grid — each with its own chat and its own run.

What Split screen is

Split screen puts up to four of your projects in one window, each in its own numbered player slot — P1 to P4, like a console game. A slot is not a preview or a read-only copy — it is the whole Code Studio, with its own chat, its own model, its own files and its own generation running. Every slot can be building at the same time.

It is for the jobs where one project is the reason you are in the other: a plugin and the config it reads, a bot and the plugin it talks to, or the version you are copying from beside the version you are writing.

The address is /ide/split, but you never need to type it — see the next section.

Opening it

  1. On the Projects page, switch the card-size toggle (the two icons beside the sort control) to Small rows, then press Beside on a project's row. The default Big cards view has no Beside button, and neither does a phone-width window. It opens next to the project you last had open — both slots arrive filled. — press “Beside”
  2. Or, from inside a project, open a menu on the Code Studio toolbar and pick “Open beside”. Your project takes the P1 slot.

    Which menu depends on the project type: on plugins, mods and Discord bots it is the ▾ beside the main Build & Export / Check Code button; on every other type it is the ⋯ menu at the right of the bar. It is in one of them, never both. It is not a button on the bar itself — that changed on 6 September 2026.

  3. An empty slot shows a join screen naming your projects — press one and it opens in place, without leaving the split.

The first door, on the project's own row in your list — in the Small rows view only; the Big cards view has no Beside. The second door is Open beside, a row in one of the Code Studio toolbar menus of a project you already have open — the Build ▾ on plugins, mods and bots, the ⋯ menu everywhere else.

Reading the screen

Keyboard shortcuts

These four work only on this screen.

ShortcutWhat it does
`Ctrl`/`Cmd` + `Shift` + `→`Move the focused project to the next slot
`Ctrl`/`Cmd` + `Shift` + `←`Move the focused project to the previous slot
`Ctrl`/`Cmd` + `Shift` + `X`Swap the two on-screen panes
`Ctrl`/`Cmd` + `Shift` + `\`Leave Split screen and go back to one editor

Moving panes around is safe — but the ✕ is not

Moving a project to the other side or pressing Swap never stops a generation. A project you take off screen is parked, not closed: its editor keeps living in the background, its run keeps going, and the strip still shows its dot — bring it back whenever you like.

The ✕ on a pane is the exception, and it changed. While that half is generating the ✕ is greyed out and says "AI is busy — wait for this run to finish", so you cannot close it mid-run by accident. And in the two-pane layout, closing a half leaves split screen altogether — which stops every run that was going. VyroAI asks first: "Close this half and stop N runs?"

Ending a session also stops its run: closing a project from the strip, or picking one to close in the too-many-projects question below. If that project is still generating, VyroAI asks first — an idle one closes without a question, because there is nothing to lose.

Files that were already written stay in your projects. Stopping a run loses the rest of the run and the credits it had spent, not the work it had finished.

The one move that still stops everything: leaving Split screen

Going back to the single editor closes the whole split screen, and even the project that survives reopens fresh — so every run stops. When something is still generating, VyroAI asks before letting you leave.

Want a different layout mid-build? Move, swap, park and switch layouts freely — that is all safe. Save leaving Split screen for when the runs are done.

Four projects at once is the ceiling

You can have up to four projects open in Split screen at the same time — all four on screen in the 4-way layout, or two on screen with the rest parked in the strip, every one of them able to keep a run going. Opening a fifth asks which one to close, with the idle ones named first. Nothing is ever closed silently.

Every generating pane is its own bill

Nothing here queues a second run and there is no combined spend readout — each pane shows only its own state. Builds in parallel cost what that many builds cost, and it is easier to forget the one you are not looking at.

If you are watching your balance, run one slot at a time, and keep Profile → Usage open in another tab.

On a phone or a narrow window

Below roughly a laptop's width the two-up layout collapses to one pane at a time and the strip becomes the switcher — a pane narrow enough to fit twice on a small screen is too narrow to read code in.

The pane you cannot see is not killed if it is working: a hidden pane that is still generating stays alive out of sight and finishes. Resizing your window across that threshold does not stop anything either.

The Open beside row itself refuses below 1024px: it stays in the menu and tells you why — Open beside needs a window at least 1024px wide — rather than quietly disappearing.

Split View is the fastest way to compare two versions of the same idea: duplicate a project, open the copy beside the original, and give each pane a different instruction. Both answers are on screen at once instead of scrolled apart in one chat — just remember you are paying for both.

Where to next

31 of 37 in Code Studio (IDE) · Last checked 11 September 2026 · Previous: Keyboard Shortcuts