Files
codex-oauth-plus-onboarding…/skill/codex-oauth-plus-onboarding/references/openai-phone-free-country-continuation-1083-2026-05-11.md
T

34 lines
2.4 KiB
Markdown

# Additional free-country phone runs — 1083 proxy, 2026-05-11
Context: after a successful ClawEmail signup/email verification for `chickliu.efxudmrg@claw.163.com`, OpenAI remained on `auth.openai.com/add-phone`. Browser was relaunched with the same OAuth Chrome profile but proxy changed to `socks5://192.168.2.8:1083` and CDP `9226`.
## Observations
- Relaunching the same verified-profile Chrome with a different proxy preserved the `add-phone` account state, but the country selector reset to `US`. Always re-run the country/dial-code gate after proxy/profile relaunch.
- Vietnam-only on 1083 produced 5 immediate reject/invalid outcomes; all 5sim activations were canceled.
- A free-country 20-actual-activation run on 1083 completed with no SMS success:
- 20 activations bought/submitted.
- 14 direct reject/invalid and canceled.
- 6 entered verification/wait state but received 0 SMS and were canceled.
- Country distribution: Argentina 4, Netherlands 2, Indonesia 2, Italy 2, Poland 2, Spain 2, England 2, Germany 3, Vietnam 1.
- Germany and Argentina frequently entered `phone-verification` with page text indicating WhatsApp delivery; under SMS-only policy, poll 5sim briefly, cancel on zero SMS, and navigate back to `/add-phone` before continuing.
- After many country/phone attempts, OpenAI may show `糟糕,出错了! Bad request`. Direct navigation back to `https://auth.openai.com/add-phone` restored the page in this run.
- Later continuation asked for another 20 actual activations. Early observations: Argentina repeatedly entered `phone-verification` but timed out with 0 SMS. Treat this as a low-yield country unless BOSS explicitly wants to keep testing it.
## Runner accounting rule
For long unrestricted runs, write JSONL logs and compute the final count from `activation_bought` lines across all chunk logs. If page errors or WhatsApp verification interrupt the run, top up only the missing number of **actual activation ids**; do not count `no free phones`, gate failures, CDP reconnects, or page recovery.
## Recovery pattern
After `sms_timeout_cancel` from a WhatsApp/SMS-wait page, explicitly do:
```text
Page.navigate https://auth.openai.com/add-phone
wait 5-8s
verify country controls exist
then select the next country before buying
```
Do not continue country-gate checks while still on `/phone-verification`; they will fail and waste scheduler slots.