executor

Orchestrate persistent interactive CLI processes with JSON-structured start, send, read, and stop primitives.

5|5|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/open-vela/.claude --skill executor-open-vela
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: executor
Source: https://github.com/open-vela/.claude/tree/main/skills/executor
Command: npx skills add https://github.com/open-vela/.claude --skill executor-open-vela

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Persistent interactive CLI processes require maintained state across commands and reliable I/O, which standard shells and one-off commands can't provide.

Core Features & Use Cases

  • Start, interact with, and terminate long-running CLI programs (REPLs, debuggers, database CLIs, simulators) with programmatic control.
  • Maintain stateful stdin/stdout communication, capture logs, and support multiple concurrent sessions.
  • Avoid terminal-emulation overhead when non-interactive I/O is sufficient, with optional terminal features via tmux when needed.

Quick Start

Start a new interactive process with executor_start, send inputs with executor_send, read outputs via executor_read_output, and stop it with executor_stop.

Frequently Asked Questions about executor

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

FAQPage Schema
How do I maintain state across commands in persistent interactive CLI processes?▼

To maintain state across commands in persistent interactive CLI processes, you can orchestrate long-running programs by sending sequential inputs and reading outputs programmatically. This avoids terminal-emulation overhead while preserving stateful stdin/stdout communication.

What's the best way to automate interactions with REPLs and database CLIs?▼

Automating interactions with REPLs and database CLIs is best handled by using start, send, read_output, and stop primitives to manage programmatic control. This allows reliable stateful communication and logging without manual terminal intervention.

Can I run multiple concurrent interactive CLI sessions simultaneously?▼

Yes, you can run multiple concurrent interactive CLI sessions simultaneously. The system supports managing several persistent processes at once, maintaining isolated state and capturing I/O logs for each independent session.

Does interactive CLI state management work with embedded simulators and debuggers?▼

Interactive CLI state management works effectively with embedded simulators and debuggers by providing ongoing interaction and logging. It orchestrates persistent processes to maintain state across sequential debugging commands.

When should I use tmux for interactive CLI processes instead of non-interactive I/O?▼

You should use tmux for interactive CLI processes when terminal emulation features are required, opting for non-interactive I/O otherwise. This avoids unnecessary overhead when simple stateful stdin/stdout communication is sufficient.