Architecture
A browser control plane.
Native work underneath.
tlbx does not emulate the tools you already use. It keeps their actual processes alive and makes them operable from the web.
Browser
Terminal rendering, files, browser panes, session navigation and explicit user input.
mthost
Authenticated HTTPS/WebSocket host, session state, history, uploads and orchestration APIs.
Native PTY
PowerShell, bash, zsh and the real coding-agent CLI continue running on the target machine.
Compatibility is part of the architecture.
The product name can change without invalidating installed systems. Service identifiers, configuration locations, PWA identity, executable names and release asset names remain stable. Update discovery moves through get.tlbx.ai, with the previous GitHub coordinate retained as a fallback during migration.
Agents see the control surface too.
Repository state, browser actions, terminal activity and attention signals are exposed through deterministic APIs and the mt CLI. The control plane is an outlet for the agents already running in tlbx—not another intelligence layer making guesses about their work.