Know when Claude needs you.

Two sessions running. One needs an answer.

Imagine Claude is working on a feature in one terminal and reviewing a change in another. When a session waits for permission or input, its card shows that attention state. You can keep working until there is something to answer.

1. See the state. A Claude Code Sessions key shows Claude sessions. All Sessions includes your other supported agents, and Swarm opens a session board.
2. Return to the work. Tap to bring a supported terminal pane forward. Exact focus depends on your terminal and host; app-level focus is available on some GUI paths.
3. Review and respond. Read the actual request before using a supported approval control. Seeing or acknowledging an alert does not approve a command.

The 22-second illustrated overview shows the general workflow. For a recorded hardware example, see the local dictation demo.

Connect Claude Code in five steps.

1. Get your trial key. Request the full 14-day trial, open the confirmation email and confirm. An eligible request receives a separate license email with the key and download link.
2. Install VibeDeck. Download the installer for your operating system, double-click it, then add the VibeDeck Setup action to your Stream Deck. Follow the install guide.
3. Activate and select Claude Code. Paste the license key into Setup. Select the detected Claude Code integration; review the configuration changes before installing hooks. Setup preserves existing hook arrays and creates backups.
4. Restart your Claude Code session. Send a prompt so the new hooks can report a live session. Check Setup if the integration reports a limited or needs-review state.
5. Add Claude Code Sessions. Put it on a free key and confirm that the session appears. Test returning to the terminal before adding more controls.

Start with the keys you will actually use.

• Claude Code Sessions: keep session state and attention visible. Add All Sessions or Swarm if you also use other agents.
• Approve / Deny: answer supported permission prompts after reviewing them. “Always” retains Claude's provider-specific scope.
• Model, effort and commands: control the selected Claude Code session through a supported terminal integration.
• Dictation: insert a transcript into a supported terminal session for review. Read the dictation guide before configuring input or auto-send options.

VibeDeck does not replace Claude Code or buy access to it. It puts supported status and controls on hardware you already use.

Check the host, not just the agent name.

For terminal sessions, exact pane focus and typing depend on the terminal integration. The full Claude Code compatibility entry lists the supported controls.

Claude in VS Code: the bridge provides status and a guarded navigation request. It does not enable deck typing or session dictation in the GUI panel. Desktop conversation selection also has separate verification limits; do not assume terminal controls work in every app.

See the session navigation guide for app focus, companions and missing targets. Using Codex too? Its managed control setup is in the Codex guide.

If the first session does not appear.

• No live card: confirm that the license is activated and the Claude Code integration is selected in Setup. Restart the affected session and send a new prompt.
• Status works, but input does not: check the terminal control level. A GUI session or limited host may support status without typing or dictation.
• Still stuck: contact [email protected] with your operating system, Stream Deck version, terminal and the Setup status message. Do not send API keys or private project content.

Test it with your own Claude workflow.

The trial includes the full plugin for 14 days, with no card and no automatic charge. If it fits your setup, VibeDeck is $19 paid once for two computers. Buy with the same email as the trial, including any +alias, to keep the same key. A different purchase email receives a new key.