wsh:core

Send input, wait for idle, and read screen output via the wsh terminal API.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides essential background knowledge about the wsh terminal API, enabling developers to understand how to interact with terminal sessions, send input, read screen output, wait for idle, and manage visual elements like overlays and panels.

Core Features & Use Cases

  • Understands terminal session lifecycle: server daemon, HTTP API, and MCP interface; handles sending input, waiting for idle, reading the screen, and creating overlays and panels.
  • Demonstrates the fundamental loop for automation: send input, wait for idle, read the screen, and decide next steps to drive tasks.
  • Use-cases include building AI-assisted terminals, debugging and automating workflows, and layering visual UI elements atop terminal sessions.

Quick Start

Load the wsh core module and experiment with sending input, reading the screen, and creating overlays.

Frequently Asked Questions about wsh:core

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

FAQPage Schema
How do I integrate an AI agent with a terminal session to send input and monitor output?

You can integrate an AI agent with a terminal session by using the wsh terminal API to drive input, wait for idle states, and read screen output to decide the next automation steps.

What is the fundamental automation loop for interacting with terminal sessions?

The fundamental terminal automation loop involves sending input to the session, waiting for the terminal to become idle, reading the screen output, and then deciding the next steps to drive tasks forward.

How do I manage real-time terminal events and session lifecycles for workflow automation?

You manage real-time terminal events and session lifecycles by interfacing with the wsh server daemon, HTTP API, and MCP interface to handle input, monitor output, and control session states.

Can I create visual UI elements like overlays and panels atop terminal sessions?

Yes, you can create and manage visual UI elements like overlays and panels directly atop terminal sessions using the core primitives provided by the wsh terminal API.

Do I need the MCP server interface to build AI-assisted terminals and automate workflows?

The MCP server interface is available as a core component of the wsh terminal API to help build AI-assisted terminals, automate workflows, and handle real-time session interactions.

Why should I wait for idle before reading the screen during terminal automation?

Waiting for idle ensures the terminal has finished processing previous commands, making the screen output stable and readable before your AI agent decides on the next input to send.