tui-tester

Automates terminal UI testing of Gemini CLI behavior and visual output.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/rameshkumarchouhanr/gemni-cli --skill tui-tester-rameshkumarchouhanr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tui-tester
Source: https://github.com/rameshkumarchouhanr/gemni-cli/tree/main/.gemini/skills/tui-tester
Command: npx skills add https://github.com/rameshkumarchouhanr/gemni-cli --skill tui-tester-rameshkumarchouhanr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Verifying that code changes to a terminal application produce the correct interactive behavior and visual rendering is tedious and error-prone when done manually. This Skill provides a structured protocol for automating TUI testing of Gemini CLI, including session management, visual validation, and regression checks. ## Core Features & Use Cases - Behavioral Verification: Confirm that code changes result in the expected terminal interactions using the agent-tui automation tool. - Visual Validation: Ensure the TUI renders correctly across different terminal sizes and states via screenshot-based checks. - Regression Testing: Automate interactive workflow checks to prevent breaking existing functionality. - Use Case: After modifying the Gemini CLI prompt rendering, build the project, launch it in an automated terminal session, type a command, and assert that the expected output text appears. ## Quick Start Ask the AI to test your local Gemini CLI changes by building the project and verifying the help command output in an automated terminal session.

Frequently Asked Questions about tui-tester

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

FAQPage Schema
How do I test Gemini CLI terminal output automatically?

Use the agent-tui tool to run the CLI in an automated terminal session, then send keystrokes and assert on expected output text. Build the project first with npm run build, then launch with agent-tui run and verify output using agent-tui wait with the --assert flag.

How to automate TUI testing for a command-line application?

Start the agent-tui daemon, launch your CLI in a managed session, and follow an action-wait-screenshot-verify loop. Execute one command per turn, capture screenshots to validate rendering, and use text assertions to confirm expected terminal output.

Why does agent-tui show os error 61 during testing?

Error os error 61 indicates the daemon connection failed. Restart the daemon by killing the agent-tui tmux session, stopping the daemon, removing temporary files in /tmp, and starting a fresh tmux session running the daemon in the foreground.

How do I avoid workspace trust prompts when testing Gemini CLI?

Set the GEMINI_CLI_TRUST_WORKSPACE=true environment variable before launching the CLI to bypass trust modals that steal focus during automated tests. Also set GEMINI_CLI_HOME to isolate test configuration from your personal settings.

What should I do when an agent-tui wait command times out?

Take a fresh screenshot to diagnose the current terminal state when a wait times out. The screenshot reveals whether the expected text failed to render, the session stalled, or the CLI is in an unexpected state requiring a different action.