Your exact environment
The agent runs in a real PTY beside the repo, SDKs, databases, devices, and private services already configured on that machine.
REMOTE AGENTS / 01
Your AI agents stay on your machines. You don’t.
Run Codex, Claude Code, Grok Build, OpenCode, Antigravity CLI, Copilot CLI, or an ordinary shell where the repos and tools already live. MidTerm keeps each session alive and gives you its control surface in any browser.
LOCAL EXECUTION / 02
The work does not travel.
This is remote control, not a cloud clone. The process, filesystem, credentials, hardware, and network stay on the host you chose.
Close the browser
The agent, build, server, and scrollback keep running. Reopen the same session from a laptop, phone, tablet, or another desktop.
Use the CLIs you trust
MidTerm does not proxy the model or replace its interface. It hosts whatever terminal-native agents and ordinary console programs you install.
One boundary per machine
Home workstation, office laptop, and server remain separate systems. Adjacent browser tabs make them reachable without pretending they are one computer.
MidTerm · remote workspace ×
MULTI-HOST / 03
Three places. One workday.
You can be away from every host and still operate each one in its native context. No repo transfer and no remote desktop scene to decode.
| Home workstation | Long-running agents, local models, GPUs, large checkouts, databases, and services continue at home. |
|---|---|
| Office laptop | Its private repo, credentials, company network, and separate MidTerm instance remain at work. |
| Your browser | From a vacation rental, train, sofa, or phone: open both hosts as tabs, inspect the exact sessions, and continue. |
BROWSER CONTROL / 04
No SSH session to reconstruct.
SSH is a transport. MidTerm preserves the working surface around the terminal so reconnecting means returning to the work, not rebuilding it.
Find the exact agent
Named, ordered, split, and bookmarked sessions retain working directory, process state, notes, drafts, attachments, and input history.
Files, Git, and the app
Inspect repository state, browse files, download artifacts, and keep the app under construction beside the terminal.
Browser-native ergonomics
Paste screenshots normally, compose multiline prompts, use camera or files, and recover exact per-session input from the timeline.
Agent-visible control
Typed helpers and authenticated APIs let agents query sessions, publish status, and operate exact MidTerm surfaces without brittle transcript guessing.
PHONE + TABLET / 05
The small screen is a real control surface.
MidTerm does not collapse the terminal into a limited chat proxy. It makes the same persistent workspace usable when the device in your hand is the only screen available.
Type into the real terminal
Use the terminal itself, its touch controls and special keys, or Command Bay when a long multiline prompt needs room before it is sent.
Keep the active line visible
The mobile layout follows the visual viewport so the focused terminal and composer stay above the on-screen keyboard instead of hiding behind it.
Paste or capture evidence
Paste screenshots with the normal shortcut, choose a file, or take a camera image. MidTerm uploads it to the correct host and gives the CLI a usable path.
Resume instead of reconnecting
Open MidTerm in the browser or install it as a PWA where supported. Named sessions, scrollback, drafts, attachments, and input history remain with the host session.
PRIVATE NETWORK / 06
Keep the path private.
MidTerm provides password-protected HTTPS and authentication. For remote access, the practical default is Tailscale—or another private WireGuard mesh—between the host and the device carrying your browser. There is no mandatory MidTerm relay.
Set up and verify private Tailscale access →
Read the real two-host field guide and tool comparison →