Skip to content

Presets

A preset saves a team of agents, the way their panes are arranged on screen and, for a Terminal pane, the command to run at startup. You can then relaunch it in one click, on this project or on another. The subtitle of the page sums it up: “Create reusable agent configurations for your projects.” A preset can also be pinned to the project bar: its icon then launches it in one click, in a new tab.

A preset contains neither your project nor your conversations: it only describes the makeup of the team.

  • Know which agents you want to work together. See VibeStarter AI agents.
  • Have an idea of how the tasks are split: two agents on the same subject get in each other’s way and use up your quota twice.
  1. Open the Presets page, then New Preset.
  2. Give it a name in the “Preset name…” field.
  3. Add the agents that make it up: one button per agent (Claude Code, Codex, Terminal…) adds a pane, numbered “#1,” “#2,” and so on.
  4. Arrange the layout of the panes, then click Save (Update for an existing preset).

The layout is set with the mouse, by dragging a pane by its header. The help shown on screen says so: “Drag the panes to rearrange them.”

A reading tip: keep on screen the agent you watch the most, and put the others in a row below. You can always enlarge a pane with Ctrl + B, then the zoom key.

A Terminal pane has a “startup command” field, preceded by $. The app says when it is used: it “Runs on launch,” in that terminal. AI agent panes do not have this field: their instruction is written in their pane, once launched.

From a project’s workspace, the app offers “Select presets for your tabs.” There are two ways to proceed:

  • Launch this preset now opens a tab and starts its team.
  • Add to launch queue stacks several presets, then the Launch button, followed by the number of tabs, opens them all at once.

Below the list, the “Launch without a preset” section lets you put together a team by hand for this time only: “This configuration won’t be saved as a preset.” To keep a team, create it from the Presets page.

  • A preset does not remember conversations. To pick up work in progress, use a pause instead. See Pause and resume a session.
  • It does not reserve memory. A preset of eight agents on a machine that is just enough for memory will trigger the automatic queuing.
  • It does not get around the Studio queue. Only one agent drives a place at a time, whatever the number of panes open.

“The page says ‘Presets could not be loaded.’” Your presets could not be read. They are still intact: the app saves nothing until it has read them again. Click Retry. Just after the app starts, the page shows “Loading…” while the environment starts up.

“Is a preset tied to a project?” No. You reuse it on any project.

“How many agents should a preset contain?” As many as your machine can support, and above all as many distinct tasks as you have to hand out. See Launch and drive your agents.

“Can I mix different agents?” Yes. A team can combine Claude Code, Codex, and a Terminal in the same tab.