Connection model
Wireless Debugging is preferred, with authorized USB fallback for the same selected device. AI-facing tools use an opaque device identity rather than raw ADB connection details.
- Off / Limited / Full access
- Separate Pause AI control
- Live screen and guarded input
- Apps, files, APK, settings, shell/log/network operations depending on granted capabilities
- Bundled semantic Phone Helper
Sensitive-app behavior
When a payment-sensitive app is foreground, RepoTunnel blocks AI screen observation and control paths. Android permissions and device policy remain authoritative even under Full Access.
Set up the selected Android device
Open Phone, authorize the device locally and choose the AI access level. Wireless Debugging is preferred; an authorized USB connection can provide fallback for the same selected phone.
AI tools cannot pair or select a device, increase access, change Limited grants or unpause Phone Access.
Choose capabilities for the task
- Live screen and local human control.
- Guarded AI observation, touch, typing and navigation.
- Supported app management and APK installation/removal.
- Bounded device files, settings, diagnostics, logs and network checks.
- Optional Phone Helper semantic references and transactions, with user-enabled Accessibility.
Check the actual device result
A Full access setting still respects Android permissions and vendor/device policy. Inspect the returned result instead of assuming a setting write or application operation is supported everywhere.
The bundled Phone Helper is a narrow companion to this workflow, not a general-purpose separate RepoTunnel Android app.