Show HN: Unterm – A pure-Rust terminal for humans and AI agents Unterm released a pure-Rust cross-platform terminal (macOS, Linux, Windows) built on its native next-core engine that exposes the terminal to external AI agents over MCP, offering 152 authenticated JSON-RPC methods plus auth.login for spawning shells, running commands, reading pane state, capturing screenshots, recording sessions and running the Agent Cockpit. Since v0.68 the terminal adds leases that expire and cannot be replayed, isolated workspaces and verifiable evidence bundles, and since v0.55 it serves as an Agent Cockpit with per-pane agent state, a waiting-first Inbox, fleets of N agents in N isolated git worktrees and a Review page for diffing, merging or rolling back their output. Every Unterm window starts a local MCP server and HTTP settings server on auto-allocated ports, both auth-token gated and bound to 127.0.0.1, with 9 built-in languages and per-instance discovery files under ~/.unterm/instances/. The terminal AI agents can drive. If Unterm is useful to you, a ⭐ on GitHub helps other people find it. Cross-platform terminal macOS / Linux / Windows built on Unterm's native next-core terminal engine, with one design bet: the terminal itself is controllable from the outside by any AI agent over MCP. Claude Code, Codex, Gemini CLI, Cursor, Aider, your own scripts — they all get the same JSON-RPC surface 152 authenticated methods plus auth.login to spawn shells, run commands, read pane state, capture screenshots, record sessions, and run the Agent Cockpit. Theme, language and unterm.conf are not on MCP; they are set through Web Settings, unterm-cli , or the file. Since v0.68 the terminal is also something an orchestrator can govern rather than merely call: it publishes what it can do and how dangerous each capability is, works under leases that expire and cannot be replayed, keeps agents inside workspaces that cannot see each other, and can hand you an evidence bundle for a task that somebody who was not there can verify. Since v0.55 the relationship runs both ways: agents drive the terminal from outside, and the terminal is an Agent Cockpit for the agents running inside it — live per-pane agent state, a waiting-first Inbox, fleets of N agents on one task in N isolated git worktrees, and a Review page to diff / merge / roll back what they produced. The other 2026 terminals each pick a different side: Warp embeds AI inside a closed cloud Oz , Ghostty stays out of your way and lets you bring your own tools, iTerm2 is Mac-only. Unterm picks the third side — terminal as MCP-controllable surface, deliberately keep AI generation out of the terminal, let external agents grip it through the API, and give the human one cockpit to run them all from. Practical implications: - Every Unterm window starts a local MCP server line-delimited JSON-RPC over TCP and a local HTTP settings server Web Settings page on auto-allocated ports. Both are auth-token gated, both are 127.0.0.1-only, no cloud round trip. - Settings live in the browser , not the terminal. Cell-grid TUIs can't deliver modern form UX no proper text inputs, no live preview, no color picker . The in-terminal ▼ menu holds quick actions and links out to the Web Settings page — configuration itself happens in the browser. - 9 languages out of the box : en / 简体中文 / 繁體中文 / 日本語 / 한국어 / Deutsch / Français / Italiano / हिन्दी. Auto-detects from system locale, can be overridden in Web Settings or via unterm-cli lang set