Instant new session (Ctrl+T fast path)
Starting a new session feels instant: the empty panel appears and the text box is focused in the same frame you press the key, with no spinner and no flicker. It works by quietly keeping one real, empty session prepared in the background, so the work that used to happen after the keypress has already happened before it.
On this page
What it is
What it does
Pressing Ctrl+T (or N) to start a new Claude Code session in the current project now feels instant — the empty session panel appears and the composer textarea is focused in the same frame you press the key, with no spinner, no "Starting…" flicker, and no round-trip to the main process before the panel paints.
It works by quietly preparing one real, empty session ahead of time. While you're working in a project, Omniscio keeps a single genuine blank session ready in the background — a real database row with a real CLI process, not a fake placeholder — and keeps its panel pre-rendered off-screen. When you hit Ctrl+T, Omniscio just reveals that already-prepared panel. The work that used to happen after you pressed the key (create the row, spawn the process, mount the panel, attach the textarea) has already happened before you pressed it.
If no prepared blank is available for any reason — you've already started typing in it, the kill switch is set, the project can't be pre-warmed, or the background prep hasn't finished yet — Ctrl+T falls through to the normal launch path. While that spawn runs, the sidebar's new-session button shows the same "Setting up workspace…" state it shows when you click it, and pressing Ctrl+T again is ignored until the launch settles — so the shortcut never looks like it was missed and never starts a second session. Nothing breaks; it's just not as fast that one time.
Where to find it
There is nothing to open — press Ctrl+T (or N) in the current project and the new session is simply there, text box focused. It is on by default; Settings → Performance → "Pre-load new sessions" can turn it off.
How it behaves
What the user sees
- Ctrl+T / N is immediate. The new blank session is active and the cursor is in the composer before you've finished lifting your finger off the key. You can start typing your first message with zero perceptible delay.
- No duplicate empty sessions. Mashing Ctrl+T five times in a row does not create five empty sessions. The first press reveals the prepared blank; the rest land on that same session (the background prep is idempotent — it reuses an existing blank instead of minting a new one).
- Your typed text is never lost. If you've started typing a message into the blank session and then press Ctrl+T again, Omniscio will not swap you onto a different blank or reset your draft. The fast path deliberately refuses any blank that has draft text in it, so a half-written message is safe. (This is a direct defense against a historical bug — see "The two regressions it avoids" below.)
- The session is real from the first frame. There's no moment where a fake/temporary session shows up and then gets replaced by "the real one." What you switch into on Ctrl+T is the real session, with a real ID, that was created in the background — so there's no flicker, no re-mount, and no risk of your first keystrokes landing on a placeholder that's about to be thrown away.
- It only ever opens a session Omniscio prepared for you. A session that something else created — an agent spawning work through the CLI, a bug-intake auto-spawn, a wave of audit fixes — is never a candidate, even while it is still empty and waiting for its first message. That distinction is not cosmetic: such a session can sit empty for a while, because its prompt waits behind worktree setup, so "looks empty at this moment" is not the same as "yours to start".
- A slow or failed start never deletes a session that exists. If a new session takes longer to start than the screen is willing to wait, or its start reports a failure while it is still being built, it stays in the sidebar with your text still in its message box, and becomes usable when it finishes starting (see "A slow mint is not a failed mint" below).
- A failed start saves your message. If a new session truly could not be created, a warning says so and that your message is saved. Try again opens a new session with your words already in the box. If you miss the warning, your next new session in that project starts with them anyway, once. Nothing is ever sent for you.
- A slow build never bounces it. A session you start skips the wait for a spare worktree folder and builds its own straight away when none is free. If the build is still slow — a busy disk — the window keeps the new session, and anything you have typed into it, on screen for as long as Omniscio is still building it, instead of giving up after two minutes (fixed 2026-10-18).
- It's scoped to the project you're in. The prepared blank belongs to the active project. Switch to a different project and Omniscio prepares a blank for that project (after a short debounce), so Ctrl+T is fast in whichever project you're currently looking at.
How pre-warmed sessions look in the sidebar
A pre-warmed blank looks like any other new session — it gets the same auto-numbered "Session N" name (e.g. "Session 42") a session gets when you create one yourself, and it isn't badged or specially marked. It simply sits ready at the top of the project's list. The fast path recognizes it structurally (an empty ready session), never by its name, so the ordinary numbered name costs it nothing, and its sidebar status dot is a plain solid dot like every other session's.
Once you press Ctrl+T and start typing, your first message triggers the usual automatic title generation, so "Session N" is replaced by a real title describing your conversation (exactly like any other new session). If you use numbered names instead of AI titles, the blank simply keeps its "Session N" — already the correct final name, nothing to replace. The recognizer that lets the auto-titler rename a placeholder blank lives in session-placeholder-name.ts — see session-placeholder-name-contract.md.
Blanks were briefly (2026-06-11 → 2026-07-01) labeled "Session Ready" with a pulsing dot; that name stranded permanently whenever an AI title never landed (always, in numbered-name mode), so it was reverted to the plain numbered default. The "Session Ready" recognizer is kept only so any blank still saved with the old name gets re-titled.
Turning it off
The pre-warm is on by default. If you'd rather not have Omniscio create sessions in advance — for example, if you want tighter control over what gets created in the background — you can turn it off in Settings → Performance → "Pre-load new sessions." When off, Ctrl+T works exactly as it did before this feature: a normal session spawn (~700 ms), no background preparation, no pre-created blank waiting in the sidebar.
There's also a developer-level environment variable kill switch (AMC_DISABLE_INSTANT_NEW_SESSION=1) that force-disables both the background pre-warm and the Ctrl+T fast path regardless of the setting. The setting and the kill switch are independent gates — either one being off disables the feature.
The two regressions it avoids
This feature exists in the shadow of two specific bugs from Omniscio's history. Both were the reason a naive "make Ctrl+T instant" attempt was dangerous, and the design is shaped around never reintroducing them.
The phantom session. An earlier fast-new-session attempt showed a fake session immediately (a temporary client-side placeholder) and then swapped in the real session once the backend caught up. The user's words: "It would only be a fake thing at the start, and then the real thing would appear later on." That swap caused flicker, lost focus, and a window where keystrokes could land on the soon-to-be-discarded placeholder. This design never uses a placeholder. The blank that Ctrl+T reveals is a genuine
sessionsrow, created in the database by the background pre-warm before you ever press the key. There is nothing to swap — the "fast" session and the "real" session are the same object.The typed-text overwrite. A second historical bug "sometimes it would overwrite the user's message that they'd already started typing." If you'd begun composing a message and then triggered a new-session action, the draft could get clobbered. This design refuses to touch any blank with a draft. The "is there a typed draft?" check lives in the renderer's store layer (where drafts actually live), and a blank that has any draft text is excluded from the fast path — so Ctrl+T can never land you on, or reset, a session you're mid-way through typing into.
What didn't change
- The "+" button. A plain click on the + icon in the Sessions panel header (or on the empty-state New Session button) takes the same instant pre-warmed path as Ctrl+T (
tryFastNewSession), and falls back to the normal launch path on a miss. Only a specialised launch — an SSH remote, a chosen provider, forced isolation, or an OpenClaw project — runs the fulllaunchSession()path. (The slow path still benefits from the backend's existingfindBlankSession()reuse, so it also won't create duplicate blanks — that behavior predates this feature.) - Blank-session reuse on the slow path. The backend's
findBlankSession()dedupe (don't create a second empty session when one already exists) is unchanged and still runs on theSESSION_LAUNCHpath. The pre-warm uses the same helper, so the two paths agree on what counts as a reusable blank. - openclaw / codex / gemini / antigravity / opencode. Those projects are never pre-warmed and always take the normal launch path on Ctrl+T. DeepSeek and Kimi projects ARE pre-warmed — they run the Claude binary, which is what the gate actually tests.
- Mobile. Mobile gets the instant reveal too — and as of 2026-06-20 the panel is pre-built there as well. The background pre-warm (the blank
readyrow) runs on mobile, and all three mobile new-session controls — the footer New Session button, the inbox-group +, and the breadcrumb + — route through ONE shared action (startNewSessionMobileinlaunch-and-reveal-session.ts) and so hit the fast path (tryInstantNewSession) exactly like desktop Ctrl+T (skipping it on mobile was a bug fixed 2026-06-17; the breadcrumb + was the LAST to be unified, 2026-06-23 — it previously calledlaunchSessiondirectly and only navigated on a non-null return, so a tunnel-timeout left the tap dead, no navigate and no toast). What used to stay desktop-only was the panel pre-mount: a phone has no multi-panel keep-alive pool, so the new-session screen was rebuilt from scratch on every tap (the textarea + chat subtree assembled live inside the slide — the "fast-path activates instantly but the screen still rebuilds" gap). That's now closed by a mobile warm host: Omniscio keeps ONE new-session panel mounted heavy in the background (the single-panel mobile counterpart of the desktop P3 render-warm), so tapping New Session reveals a ready composer instead of constructing one. It's flash-free because an empty blank's box is one line tall (a browser can't measure a hidden textarea, so pre-mounting pre-pays the expensive subtree build, not the measurement). So the warm panel is ready even for the most common gesture — open a project and immediately tap New Session. As of 2026-06-27 the blank is reserved and inserted optimistically the instant you enter a project: the renderer picks the new session's id locally (safeRandomUUID) and shows the real blank synchronously (a transient "New Session" label until the backend row lands), then confirms it with the backend underneath using that same id — so the warm host has a blank to reveal on the first tap regardless of network. That closes the last quick-tap gap: previously the blank waited on a ~quarter-secondSESSION_ENSURE_BLANKround-trip over the phone tunnel, so a fast tap inside that window fell to the "Starting session…" spinner (the "still not instant on a quick tap" report). It mints no extra sessions (the same one-per-project blank, just shown before the round-trip finishes) and is gated to spawnable Claude projects (there is no session cap to check). The backend creates the row with the same reserved id (no id-swap — the phantom-session class the postmortems forbid); if the create ever fails it rolls back cleanly (you're never stranded on a removed row), and if another device already minted a blank it adopts that one. Non-Claude / rare transient-failure cases still fall back to navigating immediately and revealing the real composer the instant the session activates (theSESSION_LAUNCHEDpush beats the worktree build), keeping you in that session even if the launch request later times out. Gated by the same "Pre-load new sessions" setting; kill switchAMC_DISABLE_MOBILE_BLANK_PREWARM=1. Seekeep-alive-pool-contract.md("Mobile surface — the new-session PANEL is pre-mounted hidden" + the mobile miss path) and start-a-new-session.md. - Virtual projects and the Inbox. Ask Omniscio, the Gmail/SMS virtual hosts, and the Inbox can't host a spawnable session, so they're excluded from the pre-warm trigger.
Related
- start-a-new-session.md — the full new-session flow, the + button, launch targets, and what happens when there's no account or the folder is missing.
- keyboard-shortcuts.md — Ctrl+T / N and every other binding; the new-session action is rebindable like the rest.
- keep-alive sessions / lazy content load — the broader "make switching sessions instant" effort this builds on; the keep-alive pool and render-warm pump are shared machinery.
Last verified 2026-10-18