wsh:tui

Integrate full-screen terminal applications inside wsh sessions with keystroke control.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Interacting with full-screen terminal applications (TUIs) often requires leaving a shell or using separate tooling; wsh provides an integrated environment to host and control TUIs within the same session, preserving context and screen state.

Core Features & Use Cases

  • In-session TUI control: operate vim, lazygit, k9s, htop, and other full-screen programs inside a single wsh session.
  • Keystroke-driven navigation: send keys, wait for redraw, and read updated screens to drive TUIs reliably.
  • Parallel session orchestration: manage multiple TUIs across sessions for concurrent workflows.

Quick Start

Attach to a TUI-enabled wsh session and start interacting with full-screen terminal applications.

Frequently Asked Questions about wsh:tui

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

FAQPage Schema
How do I control full-screen terminal applications like vim or htop inside an automated shell session?

Full-screen terminal applications like vim or htop are controlled inside shell sessions by sending deterministic keystroke sequences, waiting for screen redraws, and reading updated screen states to drive TUIs reliably.

What is the best way to orchestrate multiple TUI sessions across parallel terminal workflows?

Multiple TUI sessions are orchestrated across parallel workflows by hosting full-screen programs inside a single integrated shell environment, which preserves context and manages screen state for concurrent operations.

Can I run interactive terminal programs like lazygit and k9s without leaving my shell environment?

Interactive terminal programs like lazygit and k9s can be run without leaving the shell by attaching to a TUI-enabled session that handles alternate-screen modes and in-session application control.

How does keystroke-driven navigation work when automating full-screen TUIs in a shell?

Keystroke-driven navigation works by sending specific keys to the full-screen TUI, waiting for the application to redraw, and reading the updated screen state to confirm the interaction succeeded predictably.

Does interacting with full-screen TUIs require separate tooling or leaving the current session context?

Interacting with full-screen TUIs does not require separate tooling or leaving the session context, as the integrated shell environment hosts and controls the applications while preserving screen state.