axec-output

Read unread stdout from an axec session since the last read.

Updated Mar 20, 2026

Search Tags:#logging #cli #bash #session-management #stdout #axec #incremental-output

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Print unread stdout from an axec session since the last read. Use when you need to check for new output without re-reading the full history.

Core Features & Use Cases

Incremental reads: fetch only what has been written since the last read for a given session.
Session-targeted: works with the latest session by default or a named/UUID session.
Streaming readiness: suitable for polling dashboards and long-running workflows that rely on live logs.

Quick Start

Read the new stdout from the specified axec session since the last read.

Frequently Asked Questions about axec-output

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

FAQPage Schema

How do I read incremental stdout from a bash session without re-reading full history?▼

Incremental stdout reading fetches only new output written since the last read for a given session. It tracks a per-session read cursor, returning only unread logs without re-processing the full history.

How do I monitor live logs from a long-running axec session?▼

Monitoring live logs from a long-running axec session uses incremental output streaming to poll for new stdout. This approach fetches only the unread output since the last read, making it suitable for polling dashboards and live workflows.

Can I check incremental output for a specific named session instead of the latest one?▼

Checking incremental output supports targeting a specific named or UUID session instead of defaulting to the latest one. This allows per-session read cursor tracking to fetch only the new stdout generated since the last read.

What is the best way to stream logs from iterative tasks without duplicate output?▼

Streaming logs without duplicate output is best handled by incremental reads that track a per-session cursor. This mechanism returns only new stdout written since the last read, preventing duplicate log entries during iterative task monitoring.

Does incremental session output tracking work with polling dashboards for live logs?▼

Incremental session output tracking works with polling dashboards by providing streaming readiness for live logs. It fetches only unread stdout since the last read, ensuring efficient polling without re-reading the full session history.