Skip to main content

Android And Native Desktop

Row-Bot's mobile companion gives a paired Android device a compact view of the local app. The native desktop build adds operating-system integration such as window, tray, microphone, file-picker, and updater behaviour. Neither surface changes the approval rules of the underlying task.

Android-sized Row-Bot chat list with fictional conversations.
Chat starts with recent local threads and a New thread action.
Android-sized Row-Bot chat detail for a fictional launch checklist.
The compact thread view keeps transcript, model context, attachments, approvals, and composer controls within the phone layout.

Pair An Android Device

  1. On desktop, open Settings -> System and find Mobile Access.
  2. Read the network disclosure and choose the narrowest access mode that fits your network.
  3. Create a pairing invitation from the desktop app.
  4. Open the shown address or QR code on the Android device while both devices can reach the same Row-Bot host.
  5. Confirm the device name and access request on desktop.
  6. Revoke the device from desktop settings when it is lost, replaced, or no longer trusted.

Pairing credentials grant access to your local Row-Bot instance. Do not share a pairing invitation, expose the local server broadly, or use an untrusted network without understanding the tunnel or proxy in front of it.

Android-sized Row-Bot Activity view.
Activity keeps goals, delegated agents, approvals, and attention states available away from the desktop layout.
Android-sized Row-Bot Workflows view.
The mobile workflow view can inspect and run saved automations while preserving delivery and approval policy.
Android-sized Row-Bot Knowledge view.
Knowledge provides a compact entry point to local memory and graph review.
Android-sized Row-Bot Providers settings.
Mobile settings use the same provider categories and credential boundaries as desktop.

Native-Only Checks

Some states cannot be reproduced faithfully in browser automation: OS microphone prompts, native file pickers, tray menus, updater/restart dialogs, Computer Use takeover, and physical-device network permission. The public guide documents their intent; release review must test them on the target operating system and a physical Android device.

Troubleshooting

  • If the phone cannot connect, confirm the host, port, access mode, firewall, and network reachability shown on desktop.
  • If a token expires, pair again rather than copying cookies or local credential files.
  • If an approval is missing, open Activity and confirm the relevant thread is still active.
  • If the mobile layout opens on desktop, remove the mobile query parameter or reopen the normal local address.