SoAI Connect loads your server's WebUI in Android WebView. It adds Android permission handling and local data controls, plus native notifications and Wake-on-LAN.
SoAI WebUI features on the phone
The sidebar shows the pages your account can use. Open Chat for conversations and knowledge, or
Automation for scheduled work. Models requires Model read access (MODEL_READ),
and Files requires Files reading (FILE_EXPLORER_READ). Terminal requires
Terminal and shell access (TERMINAL_USE); it appears for an administrator or for a standard account that has been
granted that permission. Changes made in these pages are saved by the server and appear in other WebUI sessions.
| Feature | Phone behavior |
|---|---|
| Camera and microphone | SoAI Connect asks for Android permission when the SoAI page requests capture access. |
| External links | Links to another HTTP or HTTPS origin open in an external application. Other application links ask for confirmation, except email and telephone links. |
| File upload | The Android file picker supplies the selected file to the SoAI page. |
| Page recovery | Open the app's top menu and select Reload. A crashed WebView also shows a reload action. |
Native notifications
SoAI Connect receives alerts from your own server over a background connection. It does not send them through a Google push provider or require a Google account. It can forward tool approvals, agent questions, secret requests, automation results, mail events, and calendar updates or reminders.
- Open the toolbar menu, select Settings, then find Privacy.
- Turn on Android Notifications. This switch appears after the app has connected to a server.
- On Android 13 or newer, grant notification permission when prompted.
- Open Android's battery settings for SoAI and choose Unrestricted or the equivalent setting.
- Enter a device name on the same settings page and select Save device name.
The name identifies the phone under WebUI Settings, Users,
Active devices and sessions. The Users tab requires an administrator account with
User administration (USER_ADMIN) permission. Its session list contains sessions for the signed-in account, not
every user on the server. See Administration overview for the owning user and
session-management guidance.
Android may suspend the connection while battery optimization is active. Alerts still appear in the WebUI's notification center when Android forwarding is off. The background service needs a connected server and a valid session. While it runs, Android keeps an ongoing SoAI notifications active notification visible.
Wake-on-LAN
Open SoAI Connect's Settings, then Power. Enter the server machine's MAC address
and select Wake now. The default UDP port is 9; you can set another port and a custom
broadcast address for networks that need them.
Enable Wake-on-LAN in the server machine's firmware and operating system first. The network must also carry the broadcast packet to that machine. Wake now confirms that the phone sent the packet, not that the machine started.
Privacy and session controls
These controls are in SoAI Connect's Settings.
| Control | When it appears | Result |
|---|---|---|
| Change server | After the app has saved a connected server. | Clears WebUI session data, the saved server, its certificate pin, and notification delivery history, then returns to connection setup. Device identity, Wake-on-LAN values, and general preferences remain. If Android notifications were enabled, that preference applies again after you sign in to another server. |
| Clear Cache | After a non-incognito WebUI page has loaded and populated the cache. | Removes the current web cache without changing the selected server. |
| Incognito Mode | Always. | Clears cookies, cache, page history, form data, and web storage when you turn it on and whenever the app leaves the foreground. It turns native notifications off. |
| Logout | While the app has an authenticated session for the saved server. | Asks the server to revoke the session, clears local WebUI session data, and returns to that server's sign-in screen. |
| Reset Trusted Certificate | After you use Trust always for the currently saved server and certificate. | Removes the saved certificate fingerprint for the current server and reloads the WebUI. |
If the server cannot confirm logout, SoAI Connect offers a retry or a local clear. A local clear removes the phone's
credentials but may leave the server session active. If you used an administrator account with
User administration (USER_ADMIN) permission, sign in through another browser, select the
Settings button at the right of the header, choose Settings, then select
Users. Under Active devices and sessions, find the phone
by its device name and select Revoke. The
Administration overview explains the required account permissions.
That session list appears only for Administrator accounts. If you use a regular account and need the server to revoke it, choose Retry after the server is reachable instead of clearing the phone first.
Limits
| Limit | Effect |
|---|---|
| Android only | The published release requires Android 8.0 or newer. The product name is SoAI Connect. |
| Background delivery depends on Android | Battery policy, network loss, or an expired server session can interrupt native notifications. |
| No app store release | Open the SoAI Connect repository, select Releases, and install the signed APK from there. |
| No client-certificate authentication | Use a supported server authentication and TLS setup. |
| No offline mode | The app needs a reachable SoAI server to load data or run work. Cached pages do not form an offline WebUI. |
| One selected server | Use Change server before you pair the same installation with another instance. |
SoAI Connect versions do not follow server versions. Open the SoAI Connect repository, select Releases, and update the APK from there. The WebUI update flow does not update the app on your phone (it updates the server only).