axec-run

Start and manage daemon-backed sessions for long-running CLI tasks.

Updated Mar 20, 2026

Search Tags:#cli #interactive #repl #command #session #background #daemon

Ready to run

npx skills add https://github.com/SpecterShell/axec --skill axec-run

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: axec-run
Source: https://github.com/SpecterShell/axec/tree/main/skills/axec-run
Command: npx skills add https://github.com/SpecterShell/axec --skill axec-run

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a durable, daemon-backed session mechanism to run long-running commands, REPLs, or background jobs that survive CLI invocations and allow later interaction.

Core Features & Use Cases

Start a daemon-backed session with a memorable name for easy reuse across commands.
Attach to an existing session to feed input and stream live output, or monitor history from previous runs.
Manage session lifecycle with options for timeouts, stopwords, and termination, and support multiple IO backends for compatibility.
Use cases include long-running data processing, interactive shells, REPL automation, and background task orchestration.

Quick Start

Start a persistent session with axec run and then attach to it to feed input and monitor output.

Frequently Asked Questions about axec-run

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

FAQPage Schema

How do I run persistent background sessions that survive across CLI invocations?▼

Persistent background sessions use a daemon-backed mechanism to maintain long-running tasks across CLI invocations. This enables durable processes that persist independently, allowing subsequent commands to attach, stream output, and feed input to the active session.

Can I attach to an existing REPL session to feed input and stream live output?▼

Yes, you can attach to an existing REPL session to feed input and stream live output. The session mechanism supports timeout-based streaming and stopword matching, allowing you to monitor real-time output or review history from previous runs.

How do I manage the lifecycle of a background job with a specific name?▼

Background job lifecycle management is handled by assigning a memorable name to a session for easy reuse. You can start a named session, interact with it across multiple commands, and terminate it when the long-running task or background job is complete.

What IO backends are available for durable command sessions?▼

Durable command sessions support multiple IO backends including pty, pipe, and auto. These options ensure compatibility across different interactive shells, REPLs, and background task environments while handling input and output streaming.

When do I need a daemon-backed session for long-running commands?▼

A daemon-backed session is needed for long-running commands, interactive shells, or REPL automation that must survive CLI invocations. It provides durable session reuse, background job orchestration, and environment variable management for continuous processing.