How the clients differ
There are five clients, and parity between them is kept on purpose: the interface, the navigation and the screen names are the same everywhere. They differ not by "name" but by what the shell around them can do.
| Web UI | Desktop app | Android | VS Code | Telegram | |
|---|---|---|---|---|---|
| What it is | a page, installable as a PWA | a window with the server inside | a native client | a panel in the editor | a bot |
| Notifications | Web Push (needs https) | system ones, tray | its own service, no Firebase | the editor's notification | bot messages |
| Works with the client closed | yes | yes, from the tray | yes | no | yes |
| Separate windows | browser tabs | a second shell window | — | an editor tab | — |
| Files and git | yes | yes | yes | the editor has its own | — |
| Terminal | yes | yes | line by line | the editor has its own | — |
| Directories | any allowed ones | any allowed ones | any allowed ones | the opened folder only | the current session |
One and the same web UI arrives in three places — the browser, the app window and the VS Code panel — so a new interface feature shows up there by itself. It has to be repeated by hand only on Android.
How to choose
Just to look and reply from the phone — the web UI from the home screen. Installs in a minute, updates itself.
The phone as your main remote — the Android app: notifications there are held by a service of its own rather than by the browser, and that is noticeably more reliable.
A machine that is always on — the app in "server" mode: tray, autostart, notifications. It also serves the web UI to everyone else.
You write code in VS Code — the panel: the chat sits next to the code, no sign-in is asked for, and a file from the feed opens as a tab at the right line.
"A notification came in, answer right now" — Telegram. It doesn't even need a route to the machine.
What they all share
One navigation. The header shows the path to the section ("Home / Projects / folder"), every step leads upwards, and "back" returns where you came from rather than up the hierarchy: a chat is entered from the home screen, from a notification and from the agents screen alike.
Instant transitions. A list and a feed you return to are drawn straight from memory, neighbouring screens are prefetched, and where future cards will be there is their shape rather than an empty screen.
Settings travel. The address and the key by QR code, everything else (theme, interface size, images, notifications, titles, favourites, hidden items) is offered by a fresh client to be taken from the server on its first connection.