automatically control and record tui application sessions from the terminal
93
94%
Does it follow best practices?
Impact
89%
4.45xAverage score across 3 eval scenarios
Risky
Do not use without reviewing
Pipeline batch interaction pattern
Uses --json flag
0%
100%
Daemon status check
25%
100%
Daemon start if needed
42%
100%
Pipeline used for interaction
0%
100%
Type + press Enter steps
0%
100%
Wait condition in pipeline
0%
100%
Session ID captured
0%
100%
Screenshot taken
0%
100%
Session killed
50%
100%
Daemon stopped
0%
0%
Output captured to file
100%
100%
Terminal session recording
Uses --json flag
0%
100%
Daemon status check
0%
100%
Daemon started if needed
0%
100%
--record flag used
0%
100%
--record-path set correctly
0%
100%
Output directory created
100%
100%
Session ID captured
0%
100%
Session killed to finalize
0%
100%
Cast file exists
100%
100%
Daemon stopped
0%
0%
Pipeline or type+press used
60%
100%
Wait strategies and error handling
Uses --json flag
0%
100%
Daemon check and start
0%
100%
Appropriate wait strategy
53%
100%
Timeout increased
0%
100%
Screenshot on timeout
33%
100%
Error state captured
100%
100%
screen_hash used
0%
0%
Retryable check
0%
0%
Session killed
0%
100%
Daemon stopped
0%
0%
Build report written
100%
100%