Return to the right session.

All Sessions, dedicated keys, and Swarm.

All Sessions shows every agent on one key, so a new session appears without changing your layout. A dedicated Session key holds one agent: Claude Code Sessions, Codex Sessions, Cursor Sessions, Copilot CLI Sessions, Antigravity Sessions, OpenCode Sessions, Pi Sessions, or Grok Sessions.

Swarm puts waiting, done, and working totals on one key and opens the session board. Gemini CLI, Kilo, and Qwen Code each have their own Session key and also appear on All Sessions and Swarm; DeepSeek Harness has no dedicated Session key and appears on All Sessions and Swarm only.

Selected, acknowledged, and history.

A session is selected while its card is the current target of a Session key or the board. Acknowledging a waiting card marks that alert episode seen; it does not change the agent's state or answer anything. A later permission episode alerts again.

Session states include working, waiting for permission or input, done, and error. A card can also become stale after silence; silence is not proof that a session died. History is the Swarm Previous session list, described below.

Answer a waiting prompt from the deck or the screen.

When an agent waits on you, with a permission request, a question from Claude Code or Codex, or a Claude Code plan, the deck shows it first, with its chime. To answer from large keys, install the Answer profile once: select a VibeDeck Setup key in the Stream Deck app (no Setup key? drag VibeDeck → Setup onto any key) and click Install Answer profile. It works on every Stream Deck except Studio; Mobile and Virtual need a grid of at least 5 × 2. From then on, when the keys in front of you cannot answer the whole prompt, VibeDeck switches that Stream Deck to the profile, with keys for the answers to a Claude Code or Codex question (on Mini and Pedal, you step through them and choose) and Approve / Deny for permissions and plans, and switches back once no prompts are left.

The same prompt also appears as one card at the top of your screen, with the same choices. Clicking an answer leaves your keyboard in your terminal, so you can keep typing; only choosing to type your own answer moves it to the card. In the Setup key’s settings you can show the card only after you press the session’s key, choose the screen, or turn it off.

What a tap can return to.

• Terminal pane: exact tab or pane focus and typing where the terminal integration supports it. See the terminal guide.
• Desktop conversation: Claude Desktop and Codex Desktop exact conversation navigation has verification still pending. Until then, a tap brings the supported app forward.
• App focus: T3, Orca, Claude Desktop, Codex Desktop, and other GUI hosts are raised at application level. Once connected in Setup, T3 Code also opens the session’s own thread.

Typing, interruption, dictation, and approvals are separate capabilities. A host or terminal that accepts input does not make a status-only provider input-capable.

Hosts and required companions.

• OpenCode: exact TUI navigation needs the versioned TUI companion installed from VibeDeck Setup plus a restart. Setup reports Limited when it is missing. Existing terminal-only sessions retain their supported terminal focus; known GUI sessions need the companion.
• Claude VS Code: install the matching bridge extension and restart VS Code to enable the guarded navigation request. This is status and navigation only: the bridge does not enable deck typing or session dictation, even when installed.
• DeepSeek Harness: an optional companion can select a session and offer prompt or cancel control. It is not part of the standard Setup installation yet. Approvals and questions stay in the dsh web UI.
• herdr: exact workspace and pane selection through its local socket on macOS; raising the containing OS window is best effort.
• Orca: a terminal switch request is sent to a verified installed Orca CLI. The receipt means requested, not UI-confirmed, and Windows .cmd-only CLI installations are unsupported.
• tmux: exact pane injection inside any terminal when the session runs under tmux.

Install details are in the install guide, and agent-by-agent capabilities are in compatibility. Codex Direct Control setup is in the Codex guide.

Previous session in Swarm.

Previous session is an option in the existing Swarm action, not a separate action. It follows up to 20 confirmed VibeDeck visits, so it returns to a session VibeDeck actually navigated to. It skips targets that are unavailable or have been rehosted, and preserves history when navigation fails.

It is not an operating-system history and does not replay manual terminal navigation or unconfirmed URL and Orca requests. The option is pending live verification.

When the target is gone.

When a verified target is gone, replaced, or ambiguous, VibeDeck stops that navigation attempt. Some older terminal paths can resume a session in a new tab when no exact target identity is available. A card may remain visible as stale; silence alone does not prove the session is alive or dead.

A confirmed return requires a verified focus or selection result. A requested or cancelled navigation stays neutral and does not acknowledge the alert.

T3 Code: open the exact thread.

Connect T3 Code once in Setup: open T3 Code (0.1.3 or newer), open Setup from a VibeDeck key, and click Connect T3 Code. After that, tapping a Claude Code or Codex session that runs inside T3 brings T3 forward and opens that session’s thread.

VibeDeck gets read-only access to your T3 thread list. It asks T3 only when you tap a key, matches the session by its IDs, and never uses, logs or keeps your message text. The connection lasts up to 90 days; Setup shows when it ends and reconnects in one click.

Without a connection, or when VibeDeck cannot match the session to exactly one thread, a tap brings the T3 app forward as before. T3 does not confirm that a thread opened, so the key counts the app coming forward as your return. No private bridge, fork, or Accessibility workaround is used.

Try it on your own setup.

Install VibeDeck, connect your agents, and see how far session return goes with your terminal and host. The trial needs no card and ends without a charge.