phone_sms_login — Claude Code prompt: what it does, how to install
phone_sms_login — a prompt for Claude Code and ChatGPT logs into an Android app via SMS on explicit user request. Device credentials stay local and never reach the model.
Apache-2.0 ★ 9,488 updated 2026-11-16
.claude/commands/phone_sms_login.mdWhat phone_sms_login does
The prompt guides the assistant to complete SMS-based authentication for a specified Android package. The host machine selects a trusted local profile containing account details and interface mappings, captures the matching incoming SMS, inserts the verification code, and taps the sign-in button. It confirms login status strictly on-device using local OCR checks on the landing screen.
The prompt strictly forbids reading codes via chat, screenshots, sandbox tools, notifications, or MCP servers. CAPTCHA challenges, payment steps, account recovery, registration flows, and WebViews fall outside its scope, triggering an immediate handoff to manual user control.
What it helps with
- complete SMS login flows inside Android applications
- verify sign-in status on-device with local OCR
- keep sensitive one-time codes and credentials outside model context
- hand over control to the user when facing CAPTCHAs or risk checks
Example prompts for the agent
- Log into the Android app with package
com.example.appvia SMS - Sign in to
com.service.clientusing my saved device profile
How to install phone_sms_login
Manually: put the files in place
.claude/commands/phone_sms_login.mdHow to use
Paste the text at the start of a chat or into project instructions
Questions about phone_sms_login
How to install phone_sms_login in Claude Code?
Save the prompt file to .claude/commands/phone_sms_login.md.
What does phone_sms_login do?
It coordinates automated SMS login in Android apps using local trusted profiles without exposing credentials to the model.
What is required to run phone_sms_login?
You need a pre-configured, authorized local profile in device Settings and the exact Android package name of the target app.
Source text
phone_sms_login.md · Apache-2.0
Automatically log into an app only when the user explicitly asked for that login. Give its exact Android package. The host selects a device-local trusted profile containing the signed app identity, account, sender/service, native field/button mappings and logged-in account evidence. These private settings never enter model arguments/results. The user configures and authorizes the profile once in Settings; there is no per-login confirmation or manual parameter entry. The host fills the configured account, listens before requesting one new SMS, strictly matches service and account, fills its code, clicks the final login button once (unless the app already submitted automatically), and verifies the registered logged-in account on-device. Only logged_in means success. It requires matching account evidence on the landing page, no remaining code/login controls or visible code, and local OCR confirmation. Missing permissions, profiles, trustworthy identity, native controls or success evidence require a truthful failure/unverified report and manual takeover, never a fabricated success. After verified success native text observations resume with transient code redaction, so continue the user's authorized task. Phone images/previews remain local for this run. An unverified flow keeps its privacy protection. Do not obtain or resend codes through SMS apps, notifications, screenshots, shell, sandbox or MCP; do not ask for a code in chat. Payment, account recovery, registration, CAPTCHA and risk checks are outside this tool's scope. Unsupported profiles, WebViews, split fields, copied/work profiles and unattended/child/remote tasks stay manual. Disabling or editing/deleting a profile revokes its current attempt.
© wangzan101 · Apache-2.0 · wangzan101/Mika