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.
Client
Terminal rendering, files, browser panes, session navigation and explicit user input. Vanilla TypeScript plus xterm.js — no framework runtime.
Web server
Authenticated HTTPS/WebSocket server: session state, input history, uploads, Git watching, the Dev Browser proxy and the agent-facing APIs. Native AOT .NET.
Process hosts
mthost owns the real PTYs, so shells and agent CLIs survive web-server restarts and updates. mtagenthost runs provider-backed Agent Controller runtimes.
Two session runtimes. One workspace.
mthost owns native PTYs for shells, CLIs and TUIs. mtagenthost owns provider-backed Agent Controller sessions and forwards canonical ACP events for turns, tools, diffs, questions and approvals. Both session types share tlbx navigation, repository context, files, browser tooling and access controls.
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.