
Show HN: Termexo – one AI operating your other coding agents, on Windows
Let one AI operate your other coding agents.
以下正文同步自 Hacker News 最新,版权归原站所有,已转换为易读排版。
Let one AI operate your other coding agents.
Use MCP to let AI operate Claude Code, Codex, OpenCode, Pi Agent, Grok Build, and Antigravity terminals.
Give a connected AI an instruction. Through Termexo, it can find another agent's terminal, send a prompt, submit it, and read the actual reply. Watch the process or take over in the same Windows workbench, with working, approval, and completion states in view.
All six agents run in real terminals on your PC. Termexo also organizes projects into workspaces, resumes native sessions, and lets you reconnect from your phone through your own relay, a trusted LAN, or a VPN.
Watch 30 seconds of real v0.10.6 desktop use: completion notifications, return to a session, reply, and review two Antigravity sessions side by side. Includes Chinese and English captions; waiting intervals are cut.
Download for Windows · Watch the demo · Share first-use feedback
With several AI coding tools running, you spend time sending requests, checking progress, and copying replies between windows. Termexo's local MCP lets a connected AI handle those terminal operations. Workspaces, the task board, and status alerts help you follow the process; native sessions and handoff packages help you resume work, and remote access lets you continue away from your desk.
Scenarios for individuals and enterprise developers
Scenario Individual developers Enterprise team members How Termexo helps
Multiple projects Maintain work projects, a side product, and open-source repositories Organize each business project's development environment Workspaces group project folders, terminals, layouts, and configuration, reducing window switching.
Agent task allocation and progress Assign agents to implementation, tests, and code review Engineers assign tasks, follow progress, and approve results Side-by-side terminals, a task board, status indicators, and approval reminders reduce repeated output checks.
Resuming and handing off work Resume yesterday's session or continue with another agent Summarize goals, progress, and next steps to help another engineer take over Search and resume supported native sessions; carry task context in a handoff package.
Long tasks and remote access Check progress, answer approvals, and send instructions from your phone Leave tasks running on a development PC and reconnect through a controlled entry point A self-hosted relay or trusted LAN / VPN connects to the same running terminal; the host PC must stay on.
Models and account configuration Manage subscriptions and API profiles; choose a model for each task Manage providers, compatible gateways, and network configuration Model, account, and network profiles in one place, with quota visibility for supported providers.
Control over the development environment Run projects and agents on your own PC and host your own remote entry point Run the workbench in an environment controlled by your organization and manage your relay Workbench state stays local and remote access is optional; agent and model configuration determines where model requests go.
Available today and planned: These scenarios center on individuals and team members operating their own workbenches, with people assigning tasks and handling approvals. Shared workspaces, granular permissions, centralized audit, and broader automatic orchestration are part of the long-term product direction, not a ready-made enterprise administration platform.
Download the Windows installer — choose the EXE or MSI asset. No Rust or build tools needed.
Open Termexo and create a workspace for a project folder on your PC.
Start a terminal with an installed agent. If none is installed, check detection and install a CLI from Settings.
Run a task and watch its status in the terminal tab and right panel. Enable phone access later if you need it.
Already have Node.js 18.18+? Run:
npx termexo@latest
Requires Windows 10 build 17763+ and WebView2 Chromium 111+. Install and configure your chosen agent CLI and model access; Termexo does not include a model subscription. MIT licensed. No Termexo account required.
MCP connects AI to Termexo. Ask in everyday language; no tool names or code required. Install and sign in to the agent CLIs you want to use, then:
Use Termexo MCP to list my workspaces and terminals, and tell me which are running. Do not change anything yet.
A diagram of implemented capabilities, not a software screenshot. Keep the Termexo desktop running during use.
For a first exchange, open an OpenCode terminal in Termexo, then tell the connected AI:
Use Termexo MCP to find the running OpenCode terminal in the current workspace. Send hi, submit Enter, and read its reply. If several terminals match, list their names so I can choose.
Use Termexo MCP to create a Claude Code task in the current project titled “Map the project.” Use its configured default model. Read the project and explain its main folders, how to run it, and its test entry points without changing files. Start the task, inspect the terminal to confirm the prompt was submitted, and summarize the actual output.
Existing-terminal interaction works with all six agent types. Task-board execution supports Claude Code, Codex, OpenCode, Pi Agent, and Grok Build. Start Antigravity in the workbench first, then operate its terminal through MCP. The terminal creation tool creates a Shell.
Online illustrated guide · MCP reference and troubleshooting
Open a project on your PC and start Claude Code, Codex, OpenCode, Antigravity, or Grok Build.
Follow the termexo-relay documentation to deploy an HTTPS relay reachable by both devices, or use an entry point from its administrator.
Enable Remote Access in Settings, enter the relay address, and enroll with an enrollment code or relay account.
Open the generated relay link or scan its QR code on your phone. Complete the required relay login and desktop access-token check to reconnect to your terminal.
The desktop opens an outbound tunnel, with no public IP or router port forwarding required. Keep the PC on with Termexo running and connected to the relay. Direct access over a trusted LAN or controlled VPN is also available.
Relay login and the desktop access token are independent checks. After the v2 handshake, session frames use AES-256-GCM; the relay forwards encrypted terminal sessions. The relay has Linux, macOS and Windows x64 / arm64 binaries and container deployment; the Termexo desktop application is for Windows.
The image shows the mobile interface. Read the phone connection guide for the complete setup. Remote access is off by default. The relay browser entry point requires HTTPS; direct desktop access uses self-signed HTTPS by default. Keep the token private. Closing Termexo or stopping the PC ends the running processes.
v0.10.14 makes installation and updates easier for six Agents, adds Pi Agent, uses the official Antigravity updater, and keeps pending and completion reminders flashing until acknowledged. Full changelog.
If Termexo helps your workflow, a Star on this repository helps other developers discover it. Found a problem? Open an issue with your Windows version and reproduction steps.
Trying it for the first time? Tell us what worked or where you got stuck. A short report is enough.
Six agents. One screen.
Run Claude Code, Codex, OpenCode, Pi Agent, Antigravity, and Grok Build side by side in as many real PTY terminals as you need, choose which stay visible, and arrange them in a custom 1–6 row/column grid. Reorder tabs by dragging, close one with the middle mouse button, and drive the workbench from the keyboard. Each workspace remembers its folder, tabs, layout, model, and theme.
Know when an agent needs you.
Waiting for input, waiting for approval, completed, and failed states are distinct. A persistent banner, native Windows notification, and taskbar flash bring you back to the exact terminal that needs attention.
Pick up yesterday's conversation.
Search local Claude Code, Codex, OpenCode, Pi Agent, Antigravity, and Grok Build sessions across projects, accounts, branches, and models. Termexo restores them through the CLIs' own claude --resume, codex resume, opencode --session, agy --conversation, and grok --resume commands. It can reclaim a Claude session the CLI still holds open and keeps native session files read-only.
Same CLI. Different model.
Point Claude Code at Anthropic, DeepSeek, MiniMax, GLM, or a custom Anthropic-compatible endpoint. Save providers as profiles, keep API keys in Windows Credential Manager, and switch every Claude terminal in a workspace together.
Answer it from your phone.
Turn on remote access and any phone, tablet, or second computer connected through your own relay, trusted LAN or VPN opens the whole workbench in a browser — the same workspaces and the same live terminals, reading and writing the very PTYs the desktop is running. Terminals scroll by finger, the layout folds down to one terminal with panels that float over it, and the link is HTTPS behind an access token you can reveal, turn into a QR code, or rotate.
See what this session changed.
The Git view follows the active terminal and measures against the HEAD that terminal started on: the files it touched, the commits it made, and a unified or split diff of any one of them. It keeps reading while you are in it, so the list stays current without a refresh, and it comes back to the file and layout you left it on.
Turn a task into a running agent.
The task board keeps projects and tasks with priorities and acceptance criteria. Hand one to Claude Code, Codex, OpenCode, or Grok Build and it becomes a real terminal, moving through todo, executing, completed, and verified as that terminal reports its own status.
Let it run without babysitting.
Start any agent with automatic confirmation — --permission-mode auto for Claude, --approve-for-me for Codex, --auto for OpenCode, --dangerously-skip-permissions for Antigravity — so the AUTO chip on a terminal means the same thing whichever agent drew it.
Termexo is local by default: it has no account, cloud service, or required sync. Workspace state stays in local SQLite storage, credentials stay in Windows Credential Manager, and Claude/Codex session histories are read-only. The agent CLIs still connect to the providers you configure under their own terms and privacy policies.
The interface is available in Simplified Chinese, English, Spanish, French, German, Japanese, and Korean. It follows the Windows language automatically, or you can choose a language from the main toolbar and keep that choice across restarts.
AI coding tools usually run in isolated terminals and sessions. As the number of projects grows, developers have to remember:
Termexo uses the Workspace as its organizing unit and turns this scattered state into a local control plane that is observable, recoverable, and extensible.
Termexo supports detecting, installing and launching Pi Coding Agent, status tracking, native session resume, task-board execution and remote terminal operation.
npm install -g --ignore-scripts @earendil-works/pi-coding-agent pi
Run /login in Pi to configure a provider, then select Pi Agent from Termexo's new-terminal menu. Leave the model blank to use Pi's configuration, or enter provider/model. The continue option uses --continue; Session Center resolves a native session ID to its transcript file before launching --session.
Termexo stores its extension in its own runtime directory and injects it with --extension. Pi transcripts, credentials, model settings and extension configuration remain read-only. Current Pi releases can register Termexo MCP through the extension; older releases without registerMcpServer retain launch, session and status support. Pi has no per-tool confirmation CLI flag, so its launch dialog does not offer one.
Set TERMEXO_PI_PATH to override the exec
正文由 探How 从来源站点 RSS 同步,内容未经改写;遇到排版缺失或需要图片、视频时请以原文为准。