Launch terminal apps in a headless virtual terminal and assert output.
npx skills add https://github.com/microsoft/aspire --skill hex1b
Please help me install this Agent Skill. Skill: hex1b Source: https://github.com/microsoft/aspire/tree/main/.agents/skills/hex1b Command: npx skills add https://github.com/microsoft/aspire --skill hex1b
Hex1b removes flaky, manual testing and demo recording of terminal-based apps by letting you programmatically control interactive programs, inspect what they render, and wait for specific output reliably.
Start a process in a virtual terminal and then assert that the expected text appears before sending any input: run dotnet hex1b terminal start with a command, then use dotnet hex1b assert on the returned terminal id with the target text and a timeout.
High-intent search queries and answers about installing and using this skill.
Automate testing for interactive CLI and TUI applications by launching them inside a headless virtual terminal, injecting keyboard input, and asserting expected text appears before proceeding. This removes manual verification and timing flakiness.
Capture screenshots of terminal output as text, ANSI, SVG, PNG, or HTML to create deterministic assertions and visual evidence. This allows automated tests to verify that expected menus, errors, or prompts render correctly.
Yes, you can send keyboard and mouse events to a headless terminal process. You inject input into a specified terminal id and use wait operations with timeouts to ensure the application is ready for the next interaction.
The best way to record deterministic demos for interactive REPLs and shells is to script the interactions inside a headless virtual terminal. This ensures repeatable runs by capturing output and injecting input without manual intervention.
Terminal automation requires a deterministic terminal start. You launch the process inside the headless virtual terminal and then use wait and assert operations with timeouts to verify the startup sequence completed before sending input.
Interactive terminal tests fail due to timing issues when input is sent before output is ready. Avoid this by using text presence and absence assertions with timeouts to wait for expected output before injecting subsequent keyboard or mouse events.
dotnetAutomate Aspire CLI end-to-end tests using Hex1b terminal scripting.
erbsland-devConvert captured ANSI terminal output into ANSI, HTML, or plain text artifacts.
ElbertePlinioAutomate terminal TUI applications via a virtual pseudo-terminal backend.
clineAutomate terminal UI interaction and testing in headless environments.
