claude-session-driver

Drive Claude sessions in tmux by detecting pane state and routing commands.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/opensoft/dartwing-ocr-pipeline --skill claude-session-driver
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-session-driver
Source: https://github.com/opensoft/dartwing-ocr-pipeline/tree/main/.codex/skills/claude-session-driver
Command: npx skills add https://github.com/opensoft/dartwing-ocr-pipeline --skill claude-session-driver

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Operating Claude sessions manually in terminal environments is error-prone and brittle; this skill provides a disciplined driver that tracks session state, targets the correct pane, and routes inputs safely to Claude.

Core Features & Use Cases

  • State-aware session driving: identify shell vs Claude prompts and the current interaction mode to avoid sending incorrect commands.
  • Safe input orchestration: detect slash-command flows, interactive selectors, and long-running thinking periods to avoid input collisions.
  • Deterministic command delivery: target exact pane, window, and session, and wait for acknowledgment before issuing the next input.
  • Workflow versatility: supports Claude-driven Speckit tasks, follow-up questions, and structured operator prompts for multi-step workflows.

Quick Start

Attach to the target Claude session and begin driving the workflow with explicit, single-step commands as Claude prompts come back.

Frequently Asked Questions about claude-session-driver

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

FAQPage Schema
How do I automate Claude interactions in a tmux terminal session?

Automate Claude interactions in tmux using a session-aware driver that identifies pane state, routes exact commands, and prevents input misfires. The driver reads pane output to determine readiness before safely issuing the next input.

Why does my automated input collide with Claude's response in a terminal?

Automated input collides with Claude responses when lacking non-overlapping input enforcement. A session-aware driver detects interactive selectors and long thinking periods, waiting for acknowledgment before issuing the next input to prevent collisions.

How to send slash commands to Claude safely in a terminal environment?

Send slash commands safely by detecting slash-command flows and routing inputs through a deterministic driver. The driver targets the exact tmux pane and preserves command contracts to ensure safe progression through analysis steps.

Can I orchestrate multi-step Claude workflows with CLI automation?

Orchestrate multi-step Claude workflows with CLI automation by attaching a driver to the target session. The driver supports structured operator prompts, tracks session state, and provides concise progress updates for each workflow step.

What is session-aware driving for real-time Claude interactions?

Session-aware driving for Claude interactions tracks shell versus Claude prompts and the current interaction mode. This state tracking avoids sending incorrect commands and ensures deterministic command delivery to the correct pane.

Do I need tmux to automate Claude CLI sessions with a driver?

Automating Claude CLI sessions with a driver is applicable to tmux or similar terminal environments. Tmux enables the driver to target exact windows, sessions, and panes for deterministic command delivery and state tracking.