Session setup presets (set a whole launch in one click)
A preset is a saved launch configuration: engine, model, thinking level, where the session runs and which MCP servers it gets. Pick one from a new session's Session setup card and every chip is set at once instead of five separate choices.
On this page
What it is
Every new session has a launch configuration — which tool runs it, which model, how much thinking, whether it runs locally or in the cloud, and which MCP servers are attached. Choosing those by hand every time is the friction presets remove.
A preset stores exactly that set. Applying it stages the choices into the new session's draft; it does not start anything, so you can still adjust one chip afterwards before you send your first message.
Where to find it
- On a new session's Session setup card, the Preset button in the card's top-right shows the preset currently in use. Open it to pick another.
- From the keyboard: Alt+P opens the preset menu, then the number keys 1–9 apply a preset.
- On the phone: a new session's draft has the same preset menu. Phone presets cannot set MCP servers, since the phone has no local server process to attach. The list opens right beside the Preset button and stays beside it: if the screen moves under it — the keyboard closing after your first tap, the setup card scrolling — the list moves with it instead of hanging at the top of the screen or shrinking to a sliver.
- The switch: Settings → Lab → Session Setup Presets turns the feature on or off.
How it behaves
- One click sets every chip. A preset carries the engine, model, thinking level, run location and MCP server set together; picking it stages all of them into the draft.
- You can see when you have drifted. Once a chip differs from the preset it came from, a bar appears saying the launch is edited, with three choices: reset back to the preset, save the change as a new preset, or update the preset in place.
- You can edit the AI a preset uses. Open a preset's menu and choose Edit preset… to change its name and icon, and its harness, model and thinking level right there — no need to set the chips on a session first. Editing a preset changes only what that preset will apply; it never touches a session you are already working in.
- A default can fill a blank session once. One preset may be marked as your default; a brand-new session starts from it, and it never overrides a choice you already made or a hub's own defaults.
- A preset that cannot run is greyed out, not silently applied. If its provider is not ready, or its custom provider has been removed, the row is unpickable. A Cloud preset only applies where Cloud is available — otherwise nothing changes and the reason is shown.
- Fifty presets, short names. You can keep up to fifty presets. A name is limited to 60 characters and an icon to a single short emoji-style glyph.
- Deleting is undoable. Removing a preset shows a toast with an Undo, so a mistake costs one click to reverse.
- It never changes what is already running. A preset configures a session that has not started; applying one cannot alter a session already in flight.
Related
- Start a new session — the new-session screen a preset configures.
- Start a new session, part 2 — the launch pickers a preset stages.
- Quick Launch — the same presets available from the Quick Launch window's engine popover.
- Settings reference — where the Lab switch and the related settings live.
Last verified 2026-11-10