Termexo

<p align="center"> <img src="apps/desktop-ui/public/termexo-mark.svg" width="104" alt="Termexo logo"> </p> <h1 align="center">Termexo</h1> <p align="center"><strong>Start on your desktop. Keep going across networks.</strong></p> <p align="center"> <strong>English</strong> · <a href="./README.cn.md">简体中文</a> </p> <p align="center"> <img alt="Version 0.10.6" src="https://img.shields.io/badge/version-0.10.6-58c7a0"> <img alt="Windows" src="https://img.shields.io/badge/platform-Windows-0078D4?logo=windows"> <img alt="Tauri 2" src="https://img.shields.io/badge/Tauri-2-24C8DB?logo=tauri&logoColor=white"> <img alt="Angular 22" src="https://img.shields.io/badge/Angular-22-DD0031?logo=angular"> </p> <p align="center"> <a href="https://www.termexo.com">Website</a> · <a href="https://github.com/gemron/Termexo/releases/latest">Download</a> · <a href="https://www.npmjs.com/package/termexo">npm</a> </p> <p> <img src="website/assets/agent-claude.svg" alt="Claude Code" title="Claude Code" width="26" height="26">&nbsp;&nbsp; <img src="website/assets/agent-codex.svg" alt="Codex CLI" title="Codex CLI" width="26" height="26">&nbsp;&nbsp; <img src="website/assets/agent-opencode.svg" alt="OpenCode" title="OpenCode" width="26" height="26">&nbsp;&nbsp; <img src="website/assets/agent-antigravity.svg" alt="Antigravity" title="Antigravity" width="26" height="26">&nbsp;&nbsp; <img src="website/assets/agent-grok.svg" alt="Grok Build" title="Grok Build" width="26" height="26"> </p>

Termexo is building a local-first AI coding workbench that brings agents, models, and projects together, so development can continue securely between your computer and phone.

Today, it runs Claude Code, Codex, OpenCode, Antigravity, and Grok Build in one Windows workbench. Keep your agents running on your PC, then reconnect through your own relay from a phone or another computer's browser. Check output, answer an approval, or send the next instruction to the same live terminal across networks. Your desktop needs no public IP or router port forwarding.

| See your agents together | Know who needs you | Continue from your phone | | --- | --- | --- | | Arrange real terminals side by side, grouped by project. | Spot an agent waiting for input or approval. | Connect across networks through a self-hosted relay, or directly over a trusted LAN or VPN. |

The problem it solves

Working across multiple AI coding tools and projects means scattered windows, progress that is hard to track, repeated context when switching tasks, and work you cannot easily continue away from your desk. Termexo organizes projects and terminals into workspaces, brings agent status into view, helps resume work through native sessions and handoff packages, and extends the same running workbench to your phone or another computer.

<picture> <source media="(max-width: 600px)" srcset="website/assets/termexo-workflow-en-mobile.svg"> <img src="website/assets/termexo-workflow-en.svg" alt="Termexo workflow: projects and tasks enter a local workbench for agents, model profiles and sessions, with optional remote access to continue from another device"> </picture>

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.

Try it on Windows

Download the Windows installer — choose the EXE or MSI asset. No Rust or build tools needed.

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.

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.6 keeps workspace proxy settings effective in OpenCode v2 sessions, including after terminal restoration, and updates the OpenCode npm installer. 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.

<details> <summary><strong>More features and screenshots</strong></summary>

What Works Today

<table> <tr> <td width="50%" valign="top"> <strong>Five agents. One screen.</strong><br><br> 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. <br><br> <a href="website/assets/termexo-workbench.png"><img src="website/assets/termexo-workbench.png" alt="Termexo multi-agent workbench"></a> </td> <td width="50%" valign="top"> <strong>Know when an agent needs you.</strong><br><br> 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. <br><br> <a href="website/assets/termexo-attention.png"><img src="website/assets/termexo-attention.png" alt="Termexo agent attention notifications"></a> </td> </tr> <tr> <td width="50%" valign="top"> <strong>Pick up yesterday's conversation.</strong><br><br> Search local Claude Code, Codex, OpenCode, Antigravity, and Grok Build sessions across projects, accounts, branches, and models. Termexo restores them through the CLIs' own <code>claude --resume</code>, <code>codex resume</code>, <code>opencode --session</code>, <code>agy --conversation</code>, and <code>grok --resume</code> commands. It can reclaim a Claude session the CLI still holds open and keeps native session files read-only. <br><br> <a href="website/assets/termexo-session-center.png"><img src="website/assets/termexo-session-center.png" alt="Termexo native session center"></a> </td> <td width="50%" valign="top"> <strong>Same CLI. Different model.</strong><br><br> 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. <br><br> <a href="website/assets/termexo-models.png"><img src="website/assets/termexo-models.png" alt="Termexo model provider profiles"></a> </td> </tr> <tr> <td width="50%" valign="top"> <strong>Answer it from your phone.</strong><br><br> 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. <br><br> <a href="website/assets/termexo-phone.png"><img src="website/assets/termexo-phone.png" alt="The Termexo workbench open on a phone through remote access"></a> </td> <td width="50%" valign="top"> <strong>See what this session changed.</strong><br><br> 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 y