How do I install the Axec Run skill?

Run npx skillmds@latest add tomevault-io/axec-run in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Axec Run safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Axec Run?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Axec Run free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Axec Run?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Axec Run by tomevault-io — Agent Skill

Name: Axec Run
Author: tomevault-io

File contents

axec run — Start a Persistent Session

Start a command in a daemon-backed background session. The process persists after the CLI returns, allowing later input/output interaction.

Usage

axec run [OPTIONS] <CMD> [ARGS...]

Options

Option	Description
`--name NAME`	Human-readable session name for easy reference later
`--timeout SECONDS`	Stream early output for N seconds before returning
`--stopword REGEX`	Stream output until regex matches, then return
`--terminate`	Kill the session after timeout/stopword triggers
`--backend pty\|pipe\|auto`	I/O backend (default: `pty`)
`--cwd DIR`	Working directory for the command
`--env K=V`	Set environment variables (repeatable)
`--json`	Emit structured JSON response

Backend Modes

pty (default): Merged stdout/stderr, fully interactive terminal. Best for REPLs and shells.
pipe: Separate stdout/stderr streams. Best for non-interactive commands where you need split output.
auto: Platform heuristics choose between pty and pipe.

Examples

Start a Python REPL

axec run --name py python3

Start a shell session

axec run --name shell bash

Run a command with split stdout/stderr

axec run --name build --backend pipe sh -c 'echo out; echo err >&2'

Start with timeout to capture early output

axec run --name server --timeout 5 node server.js

Start with custom working directory and env vars

axec run --name dev --cwd /path/to/project --env NODE_ENV=development node app.js

One-shot command with auto backend

axec run --name check --backend auto sh -c 'echo ok; echo warn >&2; sleep 1'

Best Practices

Always use --name for sessions you plan to reuse — it makes later --session references readable.
Use --backend pipe for non-interactive commands when you need separate stdout/stderr.
Use --timeout when you want to verify the process started correctly before moving on.
Use --json when parsing the output programmatically — it returns the session UUID and metadata.
Check axec list first to avoid creating duplicate sessions with the same name.

Source: SpecterShell/axec — distributed by TomeVault.

---name: axec-rundescription: Start a persistent background session with axec. Use when you need to launch a long-running command, REPL (Python, Node, etc.), shell, or background job that persists across CLI calls. Use when this capability is needed.---# axec run — Start a Persistent SessionStart a command in a daemon-backed background session. The process persists after the CLI returns, allowing later input/output interaction.## Usage```bashaxec run [OPTIONS] <CMD> [ARGS...]```## Options| Option | Description ||--------|-------------|| `--name NAME` | Human-readable session name for easy reference later || `--timeout SECONDS` | Stream early output for N seconds before returning || `--stopword REGEX` | Stream output until regex matches, then return || `--terminate` | Kill the session after timeout/stopword triggers || `--backend pty\|pipe\|auto` | I/O backend (default: `pty`) || `--cwd DIR` | Working directory for the command || `--env K=V` | Set environment variables (repeatable) || `--json` | Emit structured JSON response |## Backend Modes- **pty** (default): Merged stdout/stderr, fully interactive terminal. Best for REPLs and shells.- **pipe**: Separate stdout/stderr streams. Best for non-interactive commands where you need split output.- **auto**: Platform heuristics choose between pty and pipe.## Examples### Start a Python REPL```bashaxec run --name py python3```### Start a shell session```bashaxec run --name shell bash```### Run a command with split stdout/stderr```bashaxec run --name build --backend pipe sh -c 'echo out; echo err >&2'```### Start with timeout to capture early output```bashaxec run --name server --timeout 5 node server.js```### Start with custom working directory and env vars```bashaxec run --name dev --cwd /path/to/project --env NODE_ENV=development node app.js```### One-shot command with auto backend```bashaxec run --name check --backend auto sh -c 'echo ok; echo warn >&2; sleep 1'```## Best Practices1. **Always use `--name`** for sessions you plan to reuse — it makes later `--session` references readable.2. **Use `--backend pipe`** for non-interactive commands when you need separate stdout/stderr.3. **Use `--timeout`** when you want to verify the process started correctly before moving on.4. **Use `--json`** when parsing the output programmatically — it returns the session UUID and metadata.5. **Check `axec list` first** to avoid creating duplicate sessions with the same name.---> Source: [SpecterShell/axec](https://github.com/SpecterShell/axec) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions

Axec Run