The Server-Manager TUI & Launchers

Beyond the web app, webAgent ships terminal-based desktop apps that make running and
managing the server friendly — no command line required.

• Desktop launcher (webagent.exe) — a polished text-UI launcher for Windows that

can install webAgent from nothing: it downloads the code, fetches its own private
Python toolchain, installs all dependencies, and downloads the browser used for
browser control. It then gives you buttons for
Launch / Restart / Stop / Open Browser / Update / Reset, watchdogs that relaunch the
server if it crashes or hangs, an animated background, and even an **embedded chat
client** so you can talk to your agent right in the launcher. The end user needs only
the single .exe.

• Server-Manager TUI — a lighter standalone manager focused on installing, linking,

running, and diagnosing a server. On Android it installs with a single pasted command
in Termux.

• Android launcher — runs the whole server on an Android phone (via Termux), with a

dependency Doctor that one-taps past the common phone-specific snags.

These are about operating the server. For where it can run, see Supported Devices & Platforms; to install by hand, see Installing & Running webAgent.

The built-in assistant

The Server-Manager isn't just buttons — it has its own built-in assistant you can chat
with right in the terminal. It talks straight to its AI provider, so it keeps working
even when the webAgent server is down, and it stays tightly focused on **two things
only: the webAgent app and the Server-Manager itself**. It's a separate, stand-alone
program — it never runs inside the web app; it drives the running server from the outside
and edits the app's files on disk as an outside helper.

What it does for you:

• Onboarding for new users. It walks you from nothing to a running server: it checks

your machine is ready (a supported Python, enough disk, a working internet connection),
helps you choose whether to install a fresh copy or **point it at a folder you already
have, and — for an existing folder — inspects it and tells you how it compares to the
official version** (is it a real install, which version, is it behind, are there unsaved
local changes) before linking it.

• A coding expert for both apps. Ask it in plain language to change, fix, or explain

something in the web app or in the Server-Manager itself; it knows where everything lives,
makes the change, and proves it works by actually running it — starting the server,
checking health, driving the screen, or replaying what the browser rendered.

• A clean, always-up server. Its standing job is to keep exactly one healthy server

running — no stale or duplicate copies quietly serving old files — and to bring it back if
it crashes, unless you stopped it on purpose.

• Careful version control. When it finishes a change it saves and publishes it, and

it pulls updates carefully so nothing you've done locally is lost — backing up first
and never doing anything destructive to your history.

• An orchestrator. For big jobs it can start background helpers that work in parallel,

then gather their results.

Related: Installing & Running webAgent, Diagnostics & the Flight Recorder,
Spawning Helper Agents, Supported Devices & Platforms.