android-phonelisted

# Android Phone Use this skill when the user explicitly invokes Android Phone or asks to inspect, control, test, debug, screenshot, navigate, type on, or automate their Android phone. Android Phone is the Android analogue of Computer / Browser: - Computer controls macOS apps. - Browser controls Codex's in-app browser. - Android Phone controls a developer-authorized Android phone through ADB. ## Source Of Truth Prefer the Android Phone MCP tools over clicking a scrcpy mirror window. The mirror is useful for human visual feedback, but ADB is the control layer. Use the tools in this order: 1. `list_devices` or `get_device_info` to confirm the target device. 2. `screenshot` for visual state. 3. `dump_ui` when structured UI text, bounds, or package/activity context is useful. 4. `tap`, `swipe`, `type_text`, `press_key`, `press_back`, or `press_home` for actions. 5. Re-observe with `screenshot` or `dump_ui` after meaningful actions. If no device is connected but Wireless debugging is already paired, ask the user for the current `IP address & Port` from the Wireless debugging screen and use `connect_wifi`. Do not ask the user for a wireless pairing code unless pairing is actually needed. Pairing grants persistent debug access and should be handled explicitly. ## Safety Treat the phone as the user's real local environment. Before filling any form on the phone, check whether fields request credentials, financial information, medical/legal information, contact details