Persistent sessions
Working directory, scrollback, process state, title, notes, drafts, and attachments remain bound to the session rather than the browser tab.
FEATURES / 01
The workspace around the agent.
MidTerm does not replace terminal-native coding agents. It gives them durable sessions, spatial organization, normal browser input, inspectable app state, and a control surface that moves with you.
SESSIONS / 02
Work survives the browser.
Every terminal is a real PTY on the host. Disconnecting a client does not stop the shell, agent, build, or server behind it.
Split and reorder
Keep an agent, test runner, logs, and app server visible together. Reorder sessions as the work changes; save durable sessions as bookmarks.
Machines as tabs
Run independent MidTerm instances at home, at work, or on a server. Open each host in an adjacent browser tab without collapsing their trust boundaries.
Reconnect anywhere
Use the same workspace from desktop, laptop, tablet, phone, browser, or installed PWA. The browser is a client, not the owner of the work.
MidTerm · workspace ×
INPUT / 03
Agent CLI ergonomics.
Normal terminal input stays direct. MidTerm adds the composition and media surfaces that long prompts and visual debugging need.
Images with the normal shortcut
Paste a screenshot with Ctrl/Cmd + V. MidTerm uploads it to the session’s host and inserts a usable path; structured sessions can stage it as an attachment.
Exact, per-session input
Direct Enter-submitted text, multiline prompts, text pastes, images, and files form a timestamped session timeline. Replay or remove an item without mixing unrelated sessions.
Command Bay
Draft multiline prompts, attach files, capture a camera image, preserve unfinished input, schedule a follow-up, or send immediately into the real terminal.
Correct terminal semantics
Direct typing and terminal control keys remain PTY input. Deliberate submission boundaries preserve multiline content instead of mistaking line breaks for separate commands.
CONTEXT / 04
The work stays beside the shell.
Agents do better when the surrounding evidence is reachable without rebuilding context in unrelated tools.
Browse the host
Navigate session-scoped files, upload and download artifacts, preview common formats, and insert paths back into the active terminal.
See repository state
Watch one or more repositories per session with branch, ahead/behind, staged, modified, untracked, and recent-commit context.
Dev Browser
Dock the app under construction beside the terminal. Inspect text, DOM outline, console and proxy logs, execute precise actions, and capture screenshots.
Artifacts, not screen scraping
Expose files and browser evidence through explicit surfaces. The agent can reason from the same output you inspect instead of guessing from a flattened remote desktop.
AGENT-VISIBLE / 05
MidTerm can be operated from inside MidTerm.
Generated mt helpers and authenticated JSON APIs expose deterministic control. No extra model, transcript classifier, or brittle “busy” heuristic is required.
Address exact sessions
Send a prompt, keys, slash command, or interrupt to a named session. Fan out deliberate work across several agents and retrieve bounded results.
Read state explicitly
Query session activity, attention, scrollback, browser status, repository state, capabilities, and ordered events through typed surfaces.
Agent-authored control data
Agents can publish work items, exact status, checkpoints, todos, mail needing attention, and next steps. MidTerm stores and relays the meaning; it does not invent it.
Optional voice control
A separate provider-backed voice service can operate the same explicit MidTerm tools. The terminal product and its public website remain fully usable without it.