MidTerm — your coding agents, your machines, any browser

Install · Agent ergonomics · Remote access · All features

Run your coding agents on your machines. Steer them from anywhere.

Name: MidTerm
Author: tlbx-ai

Start Grok Build, Codex, Claude Code, OpenCode, Antigravity CLI, Copilot CLI—or several at once—where the repos live. MidTerm keeps every session alive and puts control in any browser.

Your machines are browser tabs. Your agents keep working when you leave.

Codex, Claude Code, and Grok Build running concurrently on a home workstation controlled from a MidTerm browser tab beside another MidTerm host

Agent CLI ergonomics

MidTerm runs any terminal-native tool in a real PTY, but it is shaped around long-running coding agents:

Run many: split, reorder, bookmark, and revisit independent agent, shell, test, and server sessions.
Paste screenshots normally: Ctrl+V / Cmd+V uploads the image to the host and inserts its path. Structured agent sessions stage it as an attachment.
Compose real prompts: multiline input, per-session drafts, files, drag-and-drop, camera capture, reusable actions, and scheduled follow-ups.
Reuse exact inputs: each session's History top-bar menu (Alt+H for the active session) keeps direct Enter-submitted text, multiline prompts, pastes, images, and files replayable in place.
See what needs you: Operator separates machine facts from agent-published status, todos, mail, coding tasks, next steps, and checkpoints across hosts.
Let agents operate MidTerm: generated mt helpers expose history, capabilities, direct multi-session dispatch, ordered events, and the control plane as stable JSON.
Verify the result: open the app beside the agent; inspect DOM, console/proxy logs, responsive layouts, and screenshots.
Leave and return: sessions survive browser disconnects, device changes, and travel.

Codex, Claude Code, Grok Build, OpenCode, Copilot CLI, and Antigravity CLI sessions controlled concurrently in MidTerm

Not SSH in a browser

SSH opens a shell connection. MidTerm reopens the machine's living context: agents, terminals, files, Git, notes, logs, and app previews.

Run one independent MidTerm instance per host. Open your home workstation, office laptop, or server as adjacent tabs. Bring LAN, VPN, or reverse-tunnel connectivity; MidTerm becomes the working interface.

A browser anywhere connects to independent MidTerm instances on a home workstation, office laptop, and server; each machine keeps its own repositories, agents, and processes

Install

The native installer configures the service, password-protected HTTPS, and updates.

macOS / Linux

curl -fsSL https://tlbx-ai.github.io/MidTerm/install.sh | bash

Windows PowerShell

irm https://tlbx-ai.github.io/MidTerm/install.ps1 | iex

Open https://localhost:2000. Choose service mode for a host that should survive logouts and reboots; user mode needs no administrator access.

Private remote access

MidTerm is not a VPN or hosted relay. You choose the network path.

Recommended default: put the MidTerm host and your client devices in the same Tailscale tailnet—or use an equivalent WireGuard mesh VPN—and open MidTerm through its private address instead of exposing it publicly.

This is a strong security baseline: tailnet traffic is end-to-end encrypted, and grants/ACLs can restrict which identities and devices reach the host. Keep MidTerm's HTTPS/password authentication enabled, use least-privilege rules, and keep both products updated.

Cloudflare Tunnel, nginx/Caddy, LAN, and other private-network setups also work.

A MidTerm session remains on its host while browsers at a desk, on a laptop, and on a phone reconnect to it from different locations

[!IMPORTANT]
MidTerm has no repository-hosting cloud. Repos, credentials, tools, and processes stay on each host. Agent-provider traffic remains subject to that provider's configuration and terms.

System boundary

Part	Behavior
Host	One independent MidTerm instance exposes one machine
Execution	Real PTYs use that host's repos, credentials, tools, hardware, and network
Client	Any authorized browser; several hosts can sit in adjacent tabs
Lifetime	Browser connections are transient; agents, shells, tests, and servers persist
Context	Working directory, scrollback, Git, files, notes, logs, and previews stay with the session

Structured agent controls are runtime-dependent. Every terminal-native tool still works through its real PTY.

Trial fallback

For an ephemeral loopback trial:

npx @tlbx-ai/midterm

The launcher downloads the stable native binary and opens a browser. Use the native installer for persistent remote operation.

Architecture and source

browser anywhere
   ├── HTTPS / WebSocket ──► MidTerm on home workstation ──► agents / repos / apps
   └── HTTPS / WebSocket ──► MidTerm on office laptop ─────► agents / repos / apps

MidTerm uses .NET 10 Native AOT, TypeScript, and xterm.js.

git clone https://github.com/tlbx-ai/MidTerm.git
cd MidTerm
dotnet build src/Ai.Tlbx.MidTerm/Ai.Tlbx.MidTerm.csproj

Uninstallers: macOS/Linux · Windows

MidTerm is GNU AGPL v3. Commercial licensing is available from tlbx-ai.