Mobile Admin
Standalone mobile-optimized PWA at /mfor managing agents on the go — check agent status, answer the operator queue, toggle autonomy, and reach the fleet-level controls from a phone.
How It Works
Navigate to http://localhost/m on a mobile device (or any browser) and sign in with the admin password. The page manages its own sign-in; it never redirects to the desktop login.
Install as a PWA via Add to Home Screen for a native app experience.
The interface has three tabs (below).
Each tab refreshes every 15 seconds while it is open, and pull-to-refresh forces one. A refresh that fails keeps what is on screen and says when it was last fetched, with Retry.
Mobile Tabs
Signed In Without the Admin Role
The fleet list and fleet health are admin-only. If you open /m with a session that is not an admin's (for example, one already signed in to the main app), the Agents tab says The fleet list is admin-only on mobile. and points you to your own agents on the desktop dashboard, with Open the Queue — which lands on the Queue sub-tab. There is no Retry, because retrying cannot succeed, and the 15-second poll stops asking; a pull-to-refresh checks again, so a role granted in the meantime shows up. The System tab says Fleet health and fleet actions are admin-only and hides the four fleet actions. Any other failure still shows the usual error with Retry.
Answering the Queue
A queue card shows the agent, the priority, the type — Needs approval, Question or Heads up— the title and the question. The question renders the agent's Markdown (lists, emphasis, code), and the title and option labels render inline formatting, the same as on the desktop page and in the Workspace. The controls depend on the type, and they match the desktop page:
If the send fails on the network, the card keeps your selection and note and shows the error inline so you can retry. If the item was answered, cancelled or expired elsewhere in the meantime, a banner says This item is no longer pending (already answered, cancelled or expired) — your response was not recorded. and the card leaves the list.
Every request from /m is bounded to 30 seconds, so a request that never answers cannot leave a button disabled for the life of the tab.
A Dedicated Mobile Interface
There is no desktop equivalent — this is a dedicated mobile interface.
API Compatibility
Mobile Admin uses the same backend API as the desktop UI. No additional endpoints are required. All authenticated API calls work identically from the mobile interface. The respond body it sends is the same as the desktop's — see Approvals.