TUI-use vs Wasp

TUI-use is an open-source library that gives AI agents the ability to interact with traditional interactive terminal (TUI) applications — think vim, htop, ssh sessions, database CLIs, and legacy text-based UIs that were never designed for programmatic control. Instead of requiring a GUI or a REST API, TUI-use interprets terminal output as structured state and sends synthetic keystrokes back, enabling agents to "see" and "drive" any TUI application as if they were a human at a keyboard. The project was born from a real pain point: AI coding agents can call bash commands and write files, but they fail badly the moment a tool opens an interactive prompt waiting for user input. TUI-use solves this by building a state machine layer over PTY (pseudo-terminal) interfaces, letting agents read the current screen buffer, detect interactive prompts, and respond intelligently. It ships with adapters for common TUI patterns and a clean API that works with any LLM tool-use framework. The Show HN post attracted genuine interest from the ops and DevOps community — many existing workflows depend on tools that expose only an interactive terminal interface. TUI-use fills a real gap in the "AI agents that control computers" space by handling the long tail of CLI programs that have no API, no GUI, and no intention of ever getting one.

Wasp uses a simple DSL to define full-stack web apps — routes, auth, background jobs, email. Compiles to React + Node.js + Prisma. Configuration over code.