terminal browser multiplexer · say “toolbox”
Website · Install · Coding agents · Remote access · Security · All features
tlbx lets you use your computer's terminals and coding agents from a browser. Install it on your Windows, macOS or Linux machine, then open it from your desktop, tablet or phone. Your tools keep running when you close the browser or switch devices, as long as the host stays awake and online.
Run Codex, Claude Code, OpenCode, your usual shell, tests and dev servers in separate sessions. See files, Git changes and your app preview beside the work. tlbx is free and open source; your agent provider's usual charges still apply.
Install tlbx · Explore the features · How it works
Follow agent conversations, review changes and check the running app in one browser tab.
| Session type | Use it for | What tlbx renders |
|---|---|---|
| Terminal Session | Shells, command-line agents, editors, tests and servers | Your usual terminal, with output retained on the host |
| Agent Controller Session | Supported coding agents | A conversation view with tool calls, code changes, questions and approval buttons |
Choose the session type when you launch a tool. Both share the sidebar, files, Git view and app preview. See supported agents.
Use PowerShell, bash or zsh, and terminal apps such as btop, vim, lazygit and database shells. Split sessions into panes to watch a build, edit files and run commands side by side.
Keep several agents running and make their work easier to follow:
- Organize sessions: name, split, reorder and bookmark agents, shells and servers.
- Send screenshots:
Ctrl+V/Cmd+Vuploads an image and gives the terminal its file path. Agent Controller adds it as an attachment. - Write longer prompts: use multiline input, saved drafts, file attachments and scheduled follow-ups.
- Reuse input: open History (
Alt+H) to resend commands, prompts, images or files. - Let agents use the workspace: the
mthelpers let them send prompts, read terminal output and inspect or control the app preview. - Check the result: open your app beside the agent, try different window sizes and inspect screenshots or browser logs.
- Continue elsewhere: reconnect to the same work from another browser.
Agent Controller has built-in launch options for Codex, Grok Build, OpenCode, Gemini CLI and GitHub Copilot CLI. Features depend on the agent and its configured provider. You can add compatible ACP agents through acp-agents.json. Claude Code runs in a normal terminal session.
Install tlbx on each workstation or server you want to use. Open them in separate browser tabs, or connect them through tlbx's Hub. Each machine keeps its own files, tools and sessions.
Run one command on the machine where your tools should run. The installer sets up tlbx with password-protected HTTPS and updates.
macOS / Linux
curl -fsSL https://get.tlbx.ai/install.sh | bashWindows PowerShell
irm https://get.tlbx.ai/install.ps1 | iexOpen the address printed by the installer. Choose service mode to start tlbx automatically after login or reboot; user mode needs no administrator access. Running programs still require the host to stay awake.
These commands install the current stable release. Add --dev on macOS/Linux or -Dev on Windows only when you explicitly want the prerelease channel.
Connect your host and client devices through a trusted LAN or a private VPN such as Tailscale. Then open the host's private tlbx address in your browser.
Keep HTTPS and password authentication enabled. Restrict network access to the people and devices that need it, and keep tlbx and your VPN updated.
Cloudflare Tunnel, nginx/Caddy, LAN, and other private-network setups also work.
Important
Repositories, credentials and processes stay on your host. Coding agents may send data to their model provider according to their configuration and terms.
| Part | Behavior |
|---|---|
| Host | Your workstation or server runs tlbx and your tools |
| Execution | mthost runs terminals; mtagenthost runs Agent Controller sessions |
| Client | A browser on your desktop, tablet or phone |
| Lifetime | Sessions keep running when the browser disconnects, while the host stays awake |
| Context | Files, Git changes, retained output, notes and previews belong to the session |
Closing a browser keeps sessions running. Shutting down the host stops its processes.
For a temporary local session:
npx @tlbx-ai/midtermThe launcher downloads the stable native binary and opens a browser. Use the native installer above for a service you can return to. The npm launcher is published separately and may lag behind native releases.
browser anywhere
├── HTTPS / WebSocket ──► tlbx on home workstation ──► agents / repos / apps
└── HTTPS / WebSocket ──► tlbx on office laptop ─────► agents / repos / apps
tlbx uses .NET 10 Native AOT, TypeScript and xterm.js.
Previously named MidTerm. Existing installations update in place; executable names such as mt, mthost and mtagenthost remain compatible.
Report vulnerabilities through GitHub private vulnerability reporting, not a public issue. The security policy describes disclosure handling and the support policy identifies the supported release lines.
Every native release archive has a matching platform-specific SPDX SBOM plus GitHub build-provenance and SBOM attestations. Installers and the built-in updater additionally verify a signed manifest and every packaged-file hash. See Release integrity for verification commands and trust boundaries.
midterm-gtk is an independent, community-maintained GTK4/libadwaita desktop client with VTE terminals. It connects through tlbx's REST and WebSocket mux/state channels. It is unofficial and is not maintained or support-guaranteed by the tlbx project.
git clone https://github.com/tlbx-ai/tlbx.git tlbx
cd tlbx
dotnet build src/Ai.Tlbx.MidTerm/Ai.Tlbx.MidTerm.csprojUninstallers: macOS/Linux · Windows
tlbx is GNU AGPL v3. Commercial licensing is available from tlbx-ai.