wsh:input-capture

Intercept keyboard input and route keystrokes to terminal UI overlays.

5|2|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/deepgram/wsh --skill wsh-input-capture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wsh:input-capture
Source: https://github.com/deepgram/wsh/tree/main/skills/wsh/input-capture
Command: npx skills add https://github.com/deepgram/wsh --skill wsh-input-capture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Intercept keyboard input from humans temporarily to enable in-flow UI prompts and interactions.

The feature lets you freeze the terminal input, route keystrokes to overlays or panels, and control when input goes back to the shell.

Core Features & Use Cases

  • Temporary input capture that routes keystrokes to UI overlays or panels.
  • Focus-aware routing to a single active element and smooth transitions between passthrough and capture modes.
  • Supports common input patterns: text entry, menus, confirmations, and multi-step dialogs with clean release.

Quick Start

Start a capture session, present a yes/no prompt overlay, and release input when the user responds.

Frequently Asked Questions about wsh:input-capture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I capture keyboard input for terminal UI overlays?

Capture keyboard input for terminal UI overlays by starting a temporary input session that routes keystrokes to a single active panel. This freezes shell input and directs all key events to the overlay until the session ends.

What is focus-aware input routing in a terminal prompt?

Focus-aware input routing in a terminal prompt directs keystrokes to a single active element while freezing the background. It ensures smooth transitions between passthrough and capture modes for safe UI interactions.

How do I build a multi-step dialog with clean input release in the terminal?

Build a multi-step terminal dialog by starting a capture session to route keystrokes to the prompt. Once the user completes the final step, release the input capture to return control to the shell.

Can I intercept keystrokes for text entry menus without blocking the shell permanently?

Yes, you can intercept keystrokes for text entry menus using temporary input capture. It provides a safe escape hatch and clean release mechanism, ensuring terminal input returns to the shell after the overlay closes.

How does overlay lifecycle management work for terminal UI interactions?

Overlay lifecycle management for terminal UI interactions controls the capture session from start to finish. It manages input mode toggling, focus routing, and the safe release of keystrokes back to the shell.

What is the best way to manage terminal input modes for confirmation prompts?

The best way to manage terminal input modes for confirmation prompts is using a central workflow that toggles between passthrough and capture. This routes keystrokes to the prompt safely and releases input upon confirmation.