openconductor-tester

Launch OpenConductor in a tmux session for isolated end-to-end testing.

3|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/wilfoa/openconductor --skill openconductor-tester
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openconductor-tester
Source: https://github.com/wilfoa/openconductor/tree/main
Command: npx skills add https://github.com/wilfoa/openconductor --skill openconductor-tester

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires asciinema, agg, python3, git, and includes scripts (resource) and assets (resource) components.

What problem does it solve?

Running and reproducing terminal-based agent behaviors is error-prone and environment-sensitive; this Skill provides an isolated, repeatable tmux-based workflow to run OpenConductor, reproduce user-reported issues, and validate attention-detection heuristics without affecting a user's real configuration.

Core Features & Use Cases

  • Isolated E2E Testing: Launch OpenConductor in a detached tmux session with isolated config, logs, and state to reproduce bugs safely.
  • Terminal Capture & Visuals: Capture rendered terminal text and produce pixel-accurate screenshots for debugging and Telegram notifications.
  • Interactive Input Simulation: Send keystrokes and mouse events into the session to reproduce permission dialogs, question dialogs, long-running spinners, and scrollback behaviors.
  • Log Inspection & Validation: Tail structured JSON logs to verify attention checks, auto-approve behavior, and Telegram bridge events.
  • Use Case: Reproduce a user bug where a Claude Code spinner is missed, verify attention classifier output, and capture the terminal snapshot to attach to an issue.

Quick Start

Build the OpenConductor binary, start it in a detached tmux session with isolated config and logs, then capture the visible screen and logs for analysis.

Frequently Asked Questions about openconductor-tester

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

FAQPage Schema
How do I isolate terminal sessions for end-to-end testing without affecting my real config?

Isolated end-to-end testing uses a detached tmux session with isolated config, logs, and state paths to reproduce bugs safely without modifying your real environment.

Can I capture terminal screenshots to debug attention heuristics like spinners and permission dialogs?

Yes, you can capture terminal screenshots to debug attention heuristics by rendering the visible terminal text and producing pixel-accurate snapshots using optional tools like aha and Playwright.

How do I simulate interactive input to reproduce question sequences in a tmux session?

To simulate interactive input to reproduce question sequences in a tmux session, you send simulated keystrokes and mouse events directly into the detached session to trigger the desired agent behaviors.

What dependencies do I need to run automated terminal testing for OpenConductor?

You need an OpenConductor build, tmux, asciinema, agg, python3, and git to run automated terminal testing, with optional tools like aha and Playwright for rendering terminal screenshots.

How can I validate auto-approve behavior and Telegram bridge events during integration testing?

You validate auto-approve behavior and Telegram bridge events during integration testing by tailing structured JSON logs in the isolated environment to verify attention checks and notification outputs.

Why does my terminal scrollback fidelity break when reproducing agent behaviors?

Terminal scrollback fidelity can break when reproducing agent behaviors due to environment sensitivity, which is why using an isolated and repeatable tmux-based workflow is recommended for validation.