Use cases
Start with the job.
tlbx is one self-hosted browser workspace with six common entry points. Pick the problem you actually need to solve.
Install a browser terminal on your own machine.
Use real PowerShell, bash or zsh sessions from a browser without moving the shell into a hosted cloud.
Read the selection guide → 02 · Agent CLIRun Codex or Claude Code in a browser.
Keep the provider CLI, credentials and repository on your machine while the browser becomes the control surface.
See how agent CLIs fit → 03 · Agent ControllerRun ACP-capable agents without forcing them through a terminal.
Work with structured turns, tools, diffs, questions and approvals while the runtime stays on your machine.
Compare the two session types → 04 · Agent workKeep several coding agents visible and separate.
Mix structured Agent Controller sessions, terminal-native agents and ordinary build or test sessions without losing ownership.
See the multi-agent workflow → 05 · PhoneCheck and steer a Codex run from your phone.
Reconnect through a private route without moving the runtime, source tree or terminal state onto the phone.
See the mobile workflow → 06 · Remote accessLeave the desk without abandoning the run.
Reconnect from a laptop, tablet or phone while the process and terminal remain on the host machine.
See the remote setup →Choose something smaller when it fits
tlbx is not the answer to every terminal question.
If you need to expose one short-lived command in a browser, ttyd or WeTTY may be simpler. If you need a full server administration dashboard, Cockpit is a closer fit. tlbx is for persistent native terminal sessions, coding-agent workflows and browser access across the machines where those processes already run.