Multica vs TUI-use

Multica is an open-source platform that reframes coding agents as autonomous teammates rather than tools you prompt manually. Instead of babysitting an agent through one task at a time, you assign work through a unified dashboard, agents execute autonomously, stream real-time progress, and report back like a human engineer would. The architecture is a three-tier stack: a Next.js frontend, a Go backend with WebSocket streaming, and PostgreSQL with pgvector for semantic memory. Local agent daemons auto-detect which CLI tools are available — Claude Code, Codex, OpenClaw, or OpenCode — and manage full task lifecycles from assignment through completion. Teams can build reusable skills that persist across agents and projects, meaning the second time you ask your agent to do something, it's already done most of the thinking. Released as v0.1.26 on April 11, 2026, Multica has already accumulated 8,100+ GitHub stars. It's vendor-neutral and fully self-hostable, distinguishing it from hosted platforms like Twill or cloud-locked managed agent services. For teams that want the efficiency of AI agents without handing over their codebase to a third party, this is the most practical open-source option available today.

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.