Download for macOS
Skill

agent-tui

@google-gemini Updated 2026-09-15

Main Agents: Do NOT use this skill directly. If you need to test the TUI, invoke the `tui_tester` subagent. Drive terminal UI (TUI) applications programmatically for testing, automation, and inspection. Use when: automating CLI/TUI interactions, regression testing terminal apps, or verifying interactive behavior. Also use when: user asks "what is agent-tui", "what does agent-tui do", "demo agent-tui", "show me agent-tui", "how does agent-tui work", or wants to see it in action.

aiai-agentscligeminigemini-apimcp-clientmcp-server

Install

git clone https://github.com/google-gemini/gemini-cli /tmp/gemini-cli && ln -s /tmp/gemini-cli/.gemini/skills/agent-tui ~/.claude/skills/agent-tui

From README

🚨 CRITICAL: macOS Daemon Workaround & Gemini CLI 🚨 When using agent-tui in this macOS environment, the default background daemonization process crashes, causing Connection refused (os error 61) errors. You MUST start the daemon manually shielded from TTY hangups before running any agent-tui commands. Using nohup is insufficient; you must use tmux to provide a fully isolated pseudo-terminal. To support parallel runs, only restart the daemon if it is not currently running: Session ID vs PID (Crucial for Reconnection) When agent-tui run returns JSON, it includes both a sessionid and a pid. The pid is purely informational (the OS process ID of the child command). You do not use the pid to reconnect or issue commands. You must always use the sessionid (e.g., --session ). If the daemon crashes (os error 61), the pseudo-terminal is destroyed. Even if the child pid survives as an orphan, you cannot reconnect to it.