SmolDocling vs TUI-use

SmolDocling is a 256-million-parameter vision-language model from IBM Granite that converts documents — PDFs, scanned papers, tables, charts, forms — into clean, structured text with remarkable accuracy for its size. It introduces a new markup format called DocTags that captures not just text but document structure, reading order, and element types (headings, captions, tables, code blocks) in a way that downstream models and parsers can reliably consume. The "smol" in the name is intentional: at 256M parameters, SmolDocling runs fast enough to be deployed in production pipelines where larger VLMs would be prohibitively slow or expensive. Despite its compact size, IBM reports it achieves state-of-the-art performance across multiple document type benchmarks — outperforming much larger models on structured document parsing tasks. The key innovation is the DocTags format, which gives the model a precise vocabulary for describing document elements rather than trying to reconstruct structure from freeform text output. Built on top of the docling project (58.7k GitHub stars), SmolDocling is open source under Apache 2.0 and available on HuggingFace. The technical report is on arXiv (2503.11576). For teams building RAG pipelines, document intelligence tools, or any system that needs to ingest unstructured documents at scale, this is a practical, deployable solution.

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.