phone_wait — Claude Code prompt: what it does and how to install
The phone_wait Claude Code prompt waits for text, an activity screen, or a settled phone display. Its Android port responds to accessibility events.
Apache-2.0 ★ 9,488 updated 2026-11-16
.claude/commands/phone_wait.mdWhat phone_wait does
The prompt waits for text to show up or vanish, for a target Activity to open, or for the phone display to settle. Invoke it after an action that begins loading, rather than checking the screen at fixed intervals.
Set a condition tied to the result you need, such as specific text or an Activity. A stability timeout alone does not establish that the screen is unusable: animations, video, and timers can keep running. After a bounded wait, inspect the screen and continue if the target is visible.
What it helps with
- wait for a label to appear on the phone screen
- wait for a loading indicator to disappear
- wait for a target Activity to open
- continue once the target is visible even if an animation keeps running
Example prompts for the agent
- Wait until the phone shows the text “Done”.
- Wait for the loading indicator to disappear.
- Wait for the results Activity to open, then continue.
How to install phone_wait
Manually: put the files in place
.claude/commands/phone_wait.mdHow to use
Paste the text at the start of a chat or into project instructions
Questions about phone_wait
How do I install phone_wait in Claude Code?
Save the prompt as .claude/commands/phone_wait.md.
What does phone_wait do?
It waits for text to appear or disappear, a target Activity to open, or the phone screen to settle after an action starts loading.
Does a stability timeout mean the screen is unusable?
No. Animation, video, or timers may continue; after a bounded wait, continue if the target is visible.
Source text
phone_wait.md · Apache-2.0
Wait for text to appear or disappear, an activity class to open, or the phone screen to become stable. The Android port wakes on accessibility events. Use this after an action that starts loading instead of repeatedly observing at a fixed interval. Prefer appear/disappear/activity conditions for the result you actually need. A stability timeout does not prove the screen is unusable: animation, video and timers may never stop. After a bounded wait, observe and continue if the intended target is identifiable; do not loop on stable waits for decorative motion.
© wangzan101 · Apache-2.0 · wangzan101/Mika