Devices & Connectivity

My device isn’t showing up in the AI client

Make sure the AGI Android app is installed and signed in to the same account used by OAuth or your API key
Open Settings > Developer connection in the Android app and confirm it reports Connected
Use Connect or Refresh on that page if the connection is stale
Confirm Accessibility and overlay permissions are enabled
Ensure the phone has an active internet connection
For API-key connections, verify the configured key matches the one at platform.agi.tech/me/api-keys
Try disconnecting and reconnecting the MCP server in your client

The tool list depends on your account and registered devices:

If you only see list_devices and set_default_device, no Android device is registered. Install the AGI Android app, sign in, and reconnect
Reconnect the MCP server from your client so it calls tools/list again
Update the AGI Android app to the latest version - device tools appear when a compatible app advertises them
Confirm Settings > Developer connection reports Connected
Run list_devices, then phone_device_status to confirm the selected device is online and not paused
Make sure the server URL is https://api.agi.tech/v1/mcp
Confirm the client completed OAuth or is sending the configured Authorization header on tool-list requests

Run phone_device_status to verify which device was selected and when it was last seen
Open Settings > Developer connection on that phone and use Refresh
Check the device’s internet connection
If you have multiple devices, run list_devices and use set_default_device before starting a session
Start a new session only after the intended device reports online

Call phone_device_resume for the selected device before starting new work
Device pause blocks new tasks but does not stop an already-running task
Use phone_task_cancel or phone_session_end if you also need to stop current work

After a session starts, its session_id determines the target device, and task controls use the device that owns the task_id - changing the default device does not reroute existing work
Check is_default in list_devices output, and set it deliberately with set_default_device before starting workflows