WINDOWS WORKBENCH / MOBILE REMOTE ACCESS

At your desk. Or on your phone.

Claude Code, Codex, and OpenCode. One Windows workbench. Check output and send the next instruction from your phone. Your agents keep running on your PC.

Keep your PC running. Enable remote access, then connect with a token over a trusted LAN or VPN.

PS npx termexo@latest
How to connect your phone ↗
Termexo - A local Windows workbench for Claude Code and Codex | Product Hunt
Local-first · MIT open source Windows 10 / 11 One command to start
One workspace. Two ways in. LAN / VPN
01RUN ON YOUR PC
Termexo desktop workbench with project sidebar and two agent terminals

Your agents and project stay on the host. No session to move or restart.

02CONTINUE ON YOUR PHONE
Remote · HTTPS
Actual Termexo screenshots. Illustrative devices and connection, not a live session.
Explore the workbench
Claude CodeCodex CLIOpenCodeTask boardMulti-accountDeepSeekMiniMaxGLMMCPNative PTY
01 / WORKBENCH

Four agents. One screen.

Open as many terminals as you like, then choose which ones stay visible and arrange them in a grid that fits how you work. Switch to another project and back, and everything is exactly where you left it.

Claude Code + Codex CLI 2 × 2 grid · 3 projects open
Termexo with two terminals side by side in a grid, each showing its own command output
Open as many as you want

Every session stays alive in a tab. Show the ones you are watching right now.

6 × 6 Arrange your own grid

Anything from 1 to 6 rows and columns. Each project remembers its own layout.

5+ Swap the model, keep the CLI

Same Claude Code you already know, pointed at a different provider.

0 No sign-up, no server

Your projects and API keys stay on your computer. Termexo has no cloud to log into.

02 / NEVER MISS ONE

It tells you when an agent is stuck.

An agent sitting on an approval prompt helps nobody if you are looking at a different window. Termexo flashes the taskbar, sends a system notification, and keeps a banner on screen until you deal with it — for every project you have open, not just the one in front of you.

  • Waiting for approval, waiting for input, and finished all look different at a glance
  • Works even when the Termexo window is already focused
  • Click the banner to jump straight to that terminal
A red banner across the top of Termexo reading waiting for approval, above a Claude terminal stopped at a permission prompt
One agent needs a decision. The other is still working.
Termexo session centre listing four past Claude Code and Codex sessions, each with a resume button
Every local session, searchable and one click from resuming
03 / NOTHING IS LOST

Pick up yesterday's conversation.

Claude Code and Codex already save your sessions on disk. Termexo simply lists them so you can search and reopen one — it calls the CLI's own resume, so the full context comes back. Nothing you close is really lost.

  • Search across every project by name, path, branch, or model
  • Resumes through the real `claude --resume` and `codex resume`
  • Your session files are read-only — Termexo never edits or deletes them
04 / MODEL ROUTING

Same CLI. Different model.

Keep using Claude Code, but point it at DeepSeek, MiniMax, GLM, or your own compatible gateway. Save each one as a profile and switch between them in two clicks — no reinstalling, no editing config files by hand.

  • Anthropic, DeepSeek, MiniMax, GLM, or any compatible endpoint
  • API keys go into Windows Credential Manager, never a plain text file
  • Switch every Claude terminal in a project at once
Termexo model profile settings listing Claude Sonnet, DeepSeek, MiniMax, and GLM profiles
Keys are stored by Windows — the app only ever sees whether one exists
Termexo task board with four columns — todo, executing, completed and verified — and a task running as an agent terminal
A task carries its acceptance criteria from todo through to verified
05 / TASK BOARD

Hand the work to an agent.

Write down what needs doing and what counts as done, pick the agent and the project, and the task opens as a real terminal. It reports its own progress back to the board, so you can see what is running without reading four terminals at once.

  • Todo, executing, completed, verified — the terminal moves the card
  • Send a task to Claude Code, Codex, or OpenCode
  • Reject a result with a note and it goes back for another round
06 / ANY DEVICE

The same workbench, in your hand.

Turn on remote access and a phone, a tablet, or the laptop in the other room opens the whole workbench in a browser. Not a read-only mirror: the same workspaces and the same live terminals, so the agent stopped on an approval gets its answer while you are away from the desk.

  • Encrypted to your own machine, entered with a token you can scan as a QR code and rotate whenever you like
  • Terminals scroll by finger and take the size of whichever screen is being used
  • Nothing passes through a Termexo server — the link runs between your own devices
A phone showing the Termexo Git view over remote access, in front of the desktop workbench it is connected to
The same terminal the desktop is running, one screen at a time.
07 / FEATURES

The things you keep doing by hand.

Most of the friction with coding agents is not the model. It is remembering which terminal was doing what, and setting it all up again tomorrow.

WORKS TODAY

Close it. Reopen it. Still there.

Project folder, grid layout, which terminals were open, what model each was running, even the colour you picked — it all comes back with the workspace.

WORKS TODAY

Nothing you close is lost

Find any past Claude Code, Codex, or OpenCode session across your projects and reopen it with its full history intact.

claude --resume · codex resume · opencode --session
WORKS TODAY

Hand a task to an agent

Write down the task and what counts as done, pick an agent, and it opens as a real terminal that reports its own progress back to the board.

WORKS TODAY

Try a cheaper model on the same task

Point the same CLI at a different provider, switch back if the result is worse, and keep every key in secure storage.

WORKS TODAY
Claude CoreRUNNING
Claude ReviewWAITING APPROVAL
Codex TestsTHINKING

Know the moment it needs you

Waiting, thinking, needs approval, done, failed — shown in the tab, the panel, and the taskbar, across every project at once.

WORKS TODAY

Works in your language

Follow Windows automatically or switch between Chinese, English, Spanish, French, German, Japanese, and Korean at any time.

WORKS TODAY

See your quota before you burn it

Check how much of your plan is left and when it resets, before you decide which model to send the next task to.

WORKS TODAY

Approve it from your phone

Open the workbench in your phone's browser, over an encrypted link to your own machine, and let the agent through the approval it has been waiting on.

08 / ROADMAP

What comes next.

Everything above already works. Here is what has shipped, and what is being built next — anything still marked planned is not being sold as finished.

V0.3SHIPPED

Run several agents side by side

Claude and Codex detection, separate logins, resume, custom grids, model profiles, seven interface languages, and everything saved locally.

V0.4SHIPPED

Accounts, installs, and networks

Install or upgrade the CLIs in one click, keep several logins apart, set up proxies for a company network, and watch how much plan quota is left.

V0.5–0.6SHIPPED

Handing work between agents

Session summaries, moving a task from one agent to another, routing work, and notifications.

V0.7–0.8YOU ARE HERE

Reaching your desk from anywhere

The workbench opens on a phone or a second computer over an encrypted link to your own machine, driving the same live terminals. Paired devices, roles, and an audit trail come next.

09 / PRIVACY

Your work. On your computer.

Termexo has no account, no server, and nothing to sync. Remote access is the one link out, and it is the kind you switch on yourself, hand a token to, and switch off just as fast.

01

Local by default

Your project paths, sessions, terminal state, and settings sit in a file on your disk. There is no cloud service to sign into.

02

Your API keys are not in a config files

Keys go into Windows Credential Manager. The app stores only a reference, and the interface can tell you a key exists but never show it back.

03

Your agent files are read-only

Termexo reads what Claude Code and Codex write, and uses their own resume commands. It never rewrites, renames, or deletes your session history.

BUILD WITH US

One command. No account.

The npm package ships the whole Windows app. Run it, and if you do not like it, delete it — nothing was created anywhere else.

Built in the open, under the MIT license. If Termexo helps your workflow, a GitHub Star helps others discover it. Bug reports and contributions are welcome too.