codex - 💡(How to fix) Fix Codex cannot complete public-agency/banking workflows with protected inputs and remote GUI instability

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
RAW_BUFFERClick to expand / collapse

I am reporting a product limitation/bug from a real operational workflow. Please do not treat this as a billing request; refund/billing will be submitted separately through OpenAI Help Center.

Use case:

  • Korean tax-filing workflow involving public-agency sites, HomeTax/Wetax, bank certificate issuance, mobile authentication, TTS checkpoints, and remote browser/computer-use operation.
  • Environment included WSL/Maincomp, Server3, mobile ADB, remote GUI access, and bank/government security programs.

Observed problems:

  1. Codex could not autonomously continue through protected PASS/CAPTCHA/security-text/security-keypad stages.
  2. Bank/government security programs disrupted remote-control/browser automation and made Server3/TeamViewer/GUI operation unstable.
  3. TTS progress notifications were unreliable: some updates were cut off or overlapped.
  4. Local automation could generate many evidence/readiness workpapers, but it could not complete the actual user-facing filing and bank-certificate collection objective.
  5. The agent needed a clearer built-in mechanism to detect protected-input blockers, preserve session state, ask for user help exactly once, and resume without losing the current government/bank session.

Expected behavior:

  • Codex should clearly advertise these limitations before users depend on it for urgent government/banking operations.
  • Codex should have a robust protected-input/session-preservation workflow for public-agency and bank sites.
  • TTS/notification hooks should be serialized and reliable.
  • Computer-use/browser-use should be robust against security-program interference or should surface a precise unsupported-environment warning early.

Actual behavior:

  • The workflow remained blocked by protected input, missing bank/lender source documents, and unresolved filing-readiness gates.
  • The system spent substantial time generating local artifacts and retrying bounded refreshes without completing the real-world filing objective.

No private account details, tax records, credentials, OTPs, resident-registration numbers, or bank/account identifiers are included in this public issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Codex cannot complete public-agency/banking workflows with protected inputs and remote GUI instability