wezterm

Observe and control WezTerm panes via CLI in GUI and headless modes.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/almazom/agents_slash_skills --skill wezterm-almazom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wezterm
Source: https://github.com/almazom/agents_slash_skills/tree/main/wezterm
Command: npx skills add https://github.com/almazom/agents_slash_skills --skill wezterm-almazom

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

WezTerm pane orchestration helps you observe, read, and control panes across GUI and headless mux modes, reducing manual switching and errors.

Core Features & Use Cases

  • Observe pane content with wezterm cli get-text and read from adjacent panes.
  • Send commands and keystrokes to panes using wezterm cli send-text, and split panes to spawn workers or workbenches.
  • Manage session structure across GUI and headless environments, including spawning workers, naming workspaces, and migrating from other multiplexers.

Quick Start

Spawn a worker pane in GUI mode and verify activity with an immediate startup snapshot.

Frequently Asked Questions about wezterm

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

FAQPage Schema
How do I automate WezTerm pane control from the command line?

Automate WezTerm pane orchestration by using the WezTerm CLI to list panes, get-text for reading content, send-text for keystrokes, and split-pane to spawn workers across GUI and headless mux modes.

Can I read text from adjacent WezTerm panes without switching windows?

Yes, you can read text from adjacent panes without manual switching by executing the wezterm cli get-text command to observe content dynamically across active GUI and headless mux sessions.

Does WezTerm CLI support headless mux mode for background workers?

Yes, WezTerm CLI supports headless mux mode, allowing dynamic pane discovery, spawning workers, and managing session structure entirely in the background without a graphical interface.

What is the best way to migrate from other terminal multiplexers to WezTerm?

Migrating to WezTerm involves using its CLI to spawn workers, name workspaces, and split panes, replicating your existing session structure while leveraging dynamic discovery in GUI or headless mux modes.

Do I need Bash tooling to split panes and send keystrokes in WezTerm?

Yes, Bash tooling is required to execute WezTerm CLI commands like send-text for keystrokes and split-pane for spawning workbenches, enabling automated pane management and session orchestration.

Why use WezTerm CLI for pane management instead of manual terminal switching?

Using WezTerm CLI for pane management reduces manual switching and errors by automating observation, text reading, and keystroke dispatch across multiple panes in both GUI and headless environments.