Tether QVAC SDK vs TUI-use

Tether — yes, the stablecoin company — has launched QVAC, a fully open-source SDK for building on-device AI agents that work offline, peer-to-peer, and without any dependency on centralized cloud infrastructure. Built on a customized fork of llama.cpp called QVAC Fabric, it supports text completion, embeddings, vision, OCR, speech-to-text, text-to-speech, and translation — all running locally on Linux, macOS, Windows, Android, and iOS with a single unified API. What makes QVAC architecturally distinct is the Holepunch protocol stack underneath it: models can be distributed peer-to-peer, inference can be delegated across devices without centralized infrastructure, and the roadmap includes decentralized swarms for training and fine-tuning. Once a model is cached locally, the SDK works fully offline — making it suitable for air-gapped deployments, field work, and restricted-network environments. Tether is also running a developer grants program to fund projects building with QVAC, specifically targeting local-first AI and payment applications. With $27B+ in stablecoin reserves behind it, Tether has the runway to sustain a multi-year open-source effort here — which is more than most AI SDK projects can say.

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.