Termexo

Let one AI operate your other coding agents.

English · 简体中文

Website · Download · npm

           

Use MCP to let AI operate Claude Code, Codex, OpenCode, 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 five 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

The problem it solves

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

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.

Try it on Windows

1. Download the Windows installer — choose the EXE or MSI asset. No Rust or build tools needed.
2. Open Termexo and create a workspace for a project folder on your PC.
3. Start a terminal with an installed agent. If none is installed, check detection and install a CLI from Settings.
4. 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.

Let one AI operate another: start in three steps

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:

1. Open Settings → AI control (MCP). Enable the local server, keep automatic connection checked, and allow terminal access; also allow task access if you want to create and execute tasks. Click Apply and check for Running.
2. Start a new agent terminal in Termexo, or restart an existing one. Claude Code, Codex, OpenCode, Grok Build, and Antigravity CLI support automatic connection, with no address, token, or configuration file to copy.
3. Send this to the AI terminal and check that it returns the actual workspaces and terminals on your PC:

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.

After that, try a project task:

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 five agent types. Task-board execution supports Claude Code, Codex, OpenCode, and Grok Build. Start Antigravity in the workbench first, then operate its terminal through MCP. The terminal creation tool creates a Shell.

“Sent” and “started” do not mean “finished.” Continue reading output and task status, and check code changes and test results as the task requires. MCP is off by default and available only on the host PC; phone remote access is a separate feature, and the agent's own tool approvals still apply.

Online illustrated guide · MCP reference and troubleshooting

From your desk to your phone, through your own relay

1. Open a project on your PC and start Claude Code, Codex, OpenCode, Antigravity, or Grok Build.
2. Follow the termexo-relay documentation to deploy an HTTPS relay reachable by both devices, or use an entry point from its administrator.
3. Enable Remote Access in Settings, enter the relay address, and enroll with an enrollment code or relay account.
4. 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.

Latest release

v0.10.13 cleans up the Windows proxy environment, applies the default network profile to every terminal, rescues session scans on older OpenCode CLIs, strips instruction markup from Codex session titles, and separates completed tabs from the selected one. Start using MCP. 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.

More features and screenshots

What Works Today

Five agents. One screen. Run Claude Code, Codex, OpenCode, 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, 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.

Why Termexo

AI coding tools usually run in isolated terminals and sessions. As the number of projects grows, developers have to remember:

• which terminal belongs to which project, branch, and agent;
• which sessions are running, waiting for input, or waiting for approval;
• how to resume a specific Claude session;
• how model, endpoint, API key, and MCP configurations fit together;
• which parts of a workspace can actually be restored after an application restart.

Termexo uses the Workspace as its organizing unit and turns this scattered state into a local control plane that is observable, recoverable, and extensible.

Implemented Features

_{Models, endpoints, and credential entry are managed in one place. Stored secrets are never returned to the frontend.}

Design Goals

1. Local first — Project paths, terminals, session indexes, and configuration stay on the local machine by default. Termexo does not require a Termexo cloud service.
2. Preserve native agent semantics — Prefer native session and configuration mechanisms instead of pretending that a terminated process is still alive.
3. Coordinate terminals, do not replace them — Termexo provides the workbench, state, and orchestration layer. Commands still run inside real PTYs and agents.
4. Make agent state observable — Map agent-specific events into common running, thinking, input, approval, completed, and failed states.
5. Keep security boundaries explicit — Secrets belong in the operating-system credential store, not in SQLite, snapshots, hook payloads, or logs.
6. Grow into a multi-agent architecture — Evolve around adapters, PTY, hooks, snapshots, and routing boundaries so more CLIs can be added without rebuilding the core.
7. Extend workspaces across trusted devices — Add sharing, remote access, mobile approvals, and collaboration without weakening local ownership or security boundaries.

Current Boundaries

• All five supported agents can be detected and launched on Windows, with native sessions discoverable and resumable from the session center. Status events and launch options vary by CLI; compatible-provider model switching currently applies to Claude terminals.
• Termexo restores terminal configuration after an app restart. An exited operating-system process is not treated as still running; resume a historical agent session explicitly from the session center.
• Native session files remain read-only. Cross-agent handoff uses a redacted context package rather than rewriting a provider's private transcript.
• Git session changes are repository deltas observed since terminal start; concurrent editors or other terminals may contribute.
• Cross-network phone access needs a running PC connected to a self-hosted relay. Shared workspaces, granular permissions, and centralized audit are long-term plans.

See Termexo.md for the complete product plan and V0.2 architecture for current technical boundaries.

Build from source

These requirements are for contributors building Termexo, not for installing the release.

Requirements

• Windows 10 build 17763 (October 2018) or newer, the first to carry the pseudo console the terminals run on;
• the WebView2 runtime at Chromium 111 or newer — the interface states its colours through color-mix() and oklch(), which older runtimes drop. Termexo says so and offers the download when it finds an older one, and Windows 11 and the installers both provide a current runtime;
• Node.js ^22.22.3, ^24.15.0, or >=26.0.0;
• Rust stable and Visual Studio C++ Build Tools for the desktop runtime;
• a local installation of at least one agent CLI (Termexo can also install and upgrade them).

1. Clone and install frontend dependencies

git clone https://github.com/gemron/Termexo.git
cd Termexo
npm --prefix apps/desktop-ui install

2. Run the browser preview

npm run dev

Open http://127.0.0.1:4200. Browser mode uses a simulated terminal with help, status, git status, and clear, making it suitable for UI development and review.

3. Run the desktop application

npm run tauri:dev

Desktop mode uses real PTYs. If Claude Code is not available on PATH, specify it:

$env:TERMEXO_CLAUDE_PATH = "C:\path\to\claude.exe"
npm run tauri:dev

How It Works

flowchart LR
    UI["Angular Desktop UI"]
    IPC["Tauri Commands"]
    PTY["PTY Service"]
    Adapters["Agent Adapters"]
    Hooks["Hooks / Event Pipeline"]
    DB[("SQLite")]
    Vault["Windows Credential Manager"]
    Agents["Claude Code / Codex"]

    UI <--> IPC
    IPC --> PTY
    PTY --> Agents
    IPC --> Adapters
    Adapters --> Agents
    Agents --> Hooks
    Hooks --> DB
    IPC <--> DB
    IPC --> Vault

• Angular UI — workspaces, terminal layouts, session center, settings, and Inspector.
• Tauri Commands — a minimal IPC boundary between the frontend and desktop core.
• PTY Service — creates, writes to, resizes, and closes real terminal processes.
• Agent Adapters — Claude/Codex installation detection, read-only session scanning, and native launch/resume.
• Hooks Pipeline — receives agent lifecycle events, deduplicates them, and maps common terminal states.
• SQLite / Credential Manager — stores structured local data and sensitive credentials separately.

Data and Security

For compatibility with early installations, the database filename and some internal Tauri identifiers still use a legacy name. This does not affect the Termexo product name or new TERMEXO_* environment variables.

Roadmap

See open issues for ongoing work and CHANGELOG.md for released changes. Planned work has no promised delivery date.

Repository Layout

Termexo/
├── apps/desktop-ui/       # Angular desktop UI and browser preview
├── src-tauri/             # Rust core, PTY, agents, hooks, database, and commands
├── docs/architecture/     # Architecture notes for implemented versions
├── docs/images/           # README screenshots
└── Termexo.md             # Product design and long-term roadmap

Development and Verification

npm run build
npm test
cargo test --manifest-path src-tauri/Cargo.toml
npm --prefix apps/desktop-ui run e2e:smoke
npm run tauri:build

With the local development server running, regenerate the README screenshots with:

npm run capture:readme

Contributing

Use Issues to report bugs, discuss design decisions, or propose features. Before submitting code, make sure the change fits the current release scope and add tests for behavior changes.

License

Released under the MIT License.