Agent compatibility

Know what each agent can do from the deck.

Every available agent can show live session status. Approvals, usage, model controls, session return, and dictation depend on what each agent, host, and terminal exposes. Status-only integrations are labeled below.

Agent integrationDetermines session states, attention sounds, approvals, usage, effort, and model support.

Terminal integrationDetermines exact focus, typing, submit, clear, interruption, and Minimize Window support.

Current agent supportTerminal-dependent controls are documented separately in the terminal guide.

Swipe the table to compare every column →

Agent	Status	Return to session	Controls	Setup / details
Available now
Claude Code	Full status, usage, attention	Exact terminal pane where supported; desktop conversation preview	Approvals, model, effort, commands, dictation	Details
Codex	Core session state, weekly usage	Desktop conversation preview; app focus otherwise	Managed approvals, model, effort, presets	Details
Cursor	Core status, permission indications	App and terminal focus	Answer permissions in Cursor	Details
Copilot CLI	Core lifecycle; permission alerts only	Terminal focus where supported	Responses stay in Copilot	Details
Antigravity	Statusline states; approval alerts only	App focus	Responses stay in Antigravity	Details
OpenCode	Status, questions, approvals	Exact TUI navigation needs the companion (preview)	Allow / Deny from the deck	Details
Pi	Lifecycle, status, questions	Terminal focus where supported	Opt-in Allow / Deny	Details
Grok Build	Prompt, completion, failure, end	Terminal focus where supported	Responses stay in Grok Build	Details
Status-only integrations
DeepSeek Harness	Working, question, done observation	Optional companion navigation; not in normal Setup	Approvals stay in the dsh web UI	Details
Gemini CLI	Start, working, answer→idle, end	Session key opens the session’s terminal	Status only	Details
Kilo	Working, idle, error, end	Session key opens Kilo CLI sessions	Status only	Details
Qwen Code	Main session start, working, answer→idle, error, end, delete	Session key opens the session’s terminal	Status only	Details

Four integrations report status without deck control. DeepSeek Harness provides status observation with normal Setup on macOS; it has no dedicated Session key and its optional companion is not distributed by normal Setup. Gemini, Kilo, and Qwen are status only: each has its own Session key and also appears on All Sessions and Swarm, with no exact focus, typing, dictation, interruption, deck approval, model, or effort control. Silence and staleness are not proof that a session has died; review each provider's lifecycle limits below.

Safety (1.0.5.0). Stop (three taps within two seconds) works for input-capable sessions in iTerm2, Ghostty, tmux and herdr panes, Windows Terminal (x64) and Codex Direct Control. Context fill and cache hit rate (1.0.6.0): Claude Code, Codex and Pi. Token burn pulse and runaway or no-progress warnings: Claude Code and Codex. Subagent count and warning: Claude Code. Question alerts: Codex when its last message ends in a question (current hooks), Pi from the VibeDeck Pi extension. Status-only integrations have none of these. Read the Safety guide.

Provider details

What each integration supports today.

Every integration below ships in the current release. What differs is how much each agent, host, and terminal lets VibeDeck do.

Claude Code

Available now

Status: Live session states, attention sounds, and Claude Code usage on the deck.
Return to session: Exact terminal pane focus and typing where the terminal integration supports it. Claude Desktop exact conversation navigation has verification still pending; app focus is the current baseline.
Controls: Approve / Deny for supported prompts; “Always” keeps Claude's exact provider scope. Model, effort, commands, and dictation work through the terminal.
Claude VS Code: Status and navigation only. With the bridge extension, VibeDeck can request the owning panel, but deck typing and session dictation stay disabled even when the bridge is installed.
Setup: Install hooks from VibeDeck Setup, restart the session, then verify the first live card. Terminal permissions depend on the terminal.

Codex

Available now

Status: Core session state from installed Codex hooks, including the permission request hook. Weekly usage is read from local Codex session logs.
Return to session: Codex Desktop conversation navigation has its own verification still pending. App focus and terminal focus remain the current baseline.
Controls: Installed Codex hooks can answer Allow once or Deny from the deck on macOS and Windows; session-wide Always is available for managed sessions when Codex offers that decision. Managed Codex sessions on macOS and native Windows x64 support direct approvals, model, effort, and preset controls; unmanaged sessions retain Codex's native model picker and terminal prompts.
Setup: Codex 0.150.0 or newer is required for Direct Control. Connect plain codex from local Setup for the shortest path; the dedicated launcher is only a fallback. See the Codex guide.

Cursor

Available now

Status: Core session status and permission indications. Cursor has no documented external permission decision hook.
Return to session: App and terminal focus only; there is no deck path that selects an exact Cursor conversation.
Controls: Answer permissions in Cursor. No deck approval decision and no model controls.
Setup: Install hooks from VibeDeck Setup, then restart Cursor.

Copilot CLI

Available now

Status: Core lifecycle events. Permission prompts produce permission alerts only.
Return to session: Terminal focus where the terminal integration supports it.
Controls: Notifications show permission or elicitation attention, but responses remain in Copilot's native UI.
Setup: Save the hook file from VibeDeck Setup beside the VibeDeck-owned Copilot file.

Antigravity

Available now

Status: Statusline states for work, questions, completion, errors, and native approval attention.
Return to session: App focus; no exact conversation selection.
Controls: Approval prompts produce approval alerts only and are answered in Antigravity's UI.
Setup: Install the statusline wrapper and point Antigravity's single status line command at it.

OpenCode

Available now

Status: Working, questions, permissions, idle-complete, error, and session deletion from the installed plugin.
Return to session: Exact TUI navigation needs the versioned TUI companion installed from Setup and a restart. Setup reports Limited when it is missing. Existing terminal-only sessions retain supported terminal focus; known GUI sessions need the companion.
Controls: Approve / Deny questions and permissions from the deck; “Always” keeps OpenCode's exact provider patterns. No model or effort controls.
Setup: Install the OpenCode plugin from Setup and the companion from its local Setup entry; foreign files and commented configuration need the manual path.

Pi

Available now

Status: Lifecycle, status, and question events from the installed extension.
Return to session: Terminal focus where the terminal integration supports it.
Controls: Optional Allow / Deny when Pi is started with --vibedeck-approvals.
Setup: Install the extension from VibeDeck Setup and restart Pi with the approval flag when you want deck decisions.

Grok Build

Available now

Status: Prompt, completion, failure, and session end.
Return to session: Terminal focus where the terminal integration supports it.
Controls: No deck approval and no model controls; responses stay in Grok Build.
Setup: Install the Grok hooks from VibeDeck Setup and restart the session.

DeepSeek Harness

Status observation

Status: Working, question, and done observation through hooks. Questions and plan approval light the card as needs attention; approvals themselves stay in the dsh web UI and cannot be answered from the deck.
Return to session: An optional companion can select a session and offer prompt or cancel control. It is not installed by normal Setup, and no local filesystem installation recipe is published here.
Controls: Observe-only from the deck. Approvals and questions remain in dsh. Commands and dictation into a dsh session are not supported.
Setup: macOS with dsh web or headless. The companion is not distributed by normal Setup, and Windows control parity is not claimed.

Gemini CLI

Status only

Status: Start, working, answer→idle, and end reported through native hooks, with the last observed state kept on the key.
Return to session: A Gemini CLI Sessions key opens the session’s terminal; cards also appear on All Sessions and Swarm.
Controls: Status only: no typing, dictation, interruption, deck approval, model, or effort control.
Setup: Native hooks installed from VibeDeck Setup. macOS and Windows verification are still pending.
Limits: Cancellations and errors are not fully observable. An answer boundary settles to idle rather than proving final success.

Kilo

Status only

Status: Working, idle, error, and end from the CLI or VS Code plugin.
Return to session: A Kilo Sessions key opens Kilo CLI sessions; cards also appear on All Sessions and Swarm.
Controls: Status only: no typing, dictation, interruption, deck approval, model, or effort control.
Setup: Install the CLI or VS Code plugin. Activation in the real runtime is still pending.
Limits: There is no reliable settled-success done; idle does not mean proven success.

Qwen Code

Status only

Status: Main-session start, working, answer→idle, error, end, and delete.
Return to session: A Qwen Code Sessions key opens the session’s terminal; cards also appear on All Sessions and Swarm.
Controls: Status only: no permission response, deck typing, dictation, model, or effort control.
Setup: Supported hook mode installed from VibeDeck Setup. Verification in the real runtime is still pending.
Limits: Subagents are excluded, and an answer boundary may settle to idle rather than proving success.

Terminal compatibility

Now check focus, typing, and window control.

Your terminal determines how precisely VibeDeck can return to and control the selected session. Session navigation, including desktop conversations and companions, is covered in the session guide.

Compare terminals Session guide