Dashboard: Safari standalone web app (iOS home-screen web app) does not AutoFill or save the admin token
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- ios, typescript
- Domain
- authentication, frontend
Research direction
Start by reading gui/src/admin-token-dialog.ts and compare the existing form and submit behavior with the reported iOS standalone behavior. Reproduce the sign-in flow in Safari and in the home-screen web app; done means AutoFill is offered in standalone mode and Safari offers to save the credential after successful sign-in.
Written by the indexing model from the issue text.
Description
Client or integration
OpenCodex dashboard
Area
Dashboard
Summary
On iOS, the dashboard admin-token sign-in is never offered password AutoFill when the dashboard is installed as a standalone web app (Safari → Share → Add to Home Screen). Safari in the regular browser tab does offer AutoFill/Save for the same dialog; only the standalone home-screen web app does not. The admin token is long and random, so without AutoFill the only option is manual copy/paste on every sign-in.
The dialog already follows the standard shape (gui/src/admin-token-dialog.ts): a real <form method="post" action="..."> with a type="text" autocomplete="username" field and a type="password" name="password" autocomplete="current-password" field, plus a submit button. Submission is a normal submit event handler that calls preventDefault() and verifies the token via fetch. Despite that, the iOS standalone (WKWebView home-screen) context never shows the QuickType password suggestion bar for the field and never offers to save the credential, while the same page in Safari proper does.
Expected: the admin token field offers iOS password AutoFill (QuickType key / saved credentials) in the standalone web app, and Safari offers to save the credential after a successful sign-in.
Reproduction
- Serve the dashboard on a LAN/Tailscale URL (
ocx start). - In iOS Safari, open the dashboard and sign in with the admin token — AutoFill suggestions and the save-password prompt appear in the browser.
- In iOS Safari, use Share → Add to Home Screen, then launch the dashboard from the home-screen web app.
- Focus the admin token field: no password AutoFill suggestion bar appears, and after a successful sign-in Safari never offers to save the credential.
Version
2.48.0
Operating system
Server: Windows 11; client: iPhone, iOS (Safari standalone web app via Add to Home Screen)
Logs or error output
None — no server-side error; sign-in succeeds when the token is entered manually. The problem is purely that iOS standalone-mode Safari does not treat the field as a login credential field.
Screenshots and supporting files
Screenshot of the standalone web app sign-in showing the token field without any AutoFill suggestion bar (attached to the thread; can be re-attached on request).
Redacted configuration
Not provider/config specific — affects the dashboard sign-in dialog itself.
Checks
- I searched existing issues and documentation.
- I removed secrets, tokens, account details, request credentials, and personal data.
- Dominant language
- TypeScript
- Stars
- 16.9k
- Forks
- 1.3k
- Avg merge
- 7h 40m
- Merged PRs (30d)
- 668
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from lidge-jun/opencodex
-
account-pool bug provider
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
account-pool enhancement needs-design proxy
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
lidge-jun/opencodex#6737 · 1 comment ·
Maintainers usually reply within 1 day
-
account-pool bug tools
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Maintainers usually reply within 1 day
-
bug(vertex): API-key requests ignore project/location and fail for Gemini 4 ArgonPossibly taken A pull request linked to this issue is open or already merged. Openbug provider
Difficulty 3/5 1-2 days Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
provider provider-compatibility
Difficulty 4/5 3-5 days Newbie friendliness 45/100
lidge-jun/opencodex#7255 · 2 comments ·
Maintainers usually reply within 1 day
All issues in lidge-jun/opencodex
Similar issues
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 90/100
lingdojo/kana-dojo#32663 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
Admin: Title Separator field can't be cleared (input falls back to "|")Possibly taken @emdashbot claimed this today. Openbot:bug bot:in-review
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
emdash-cms/emdash#4236 · 3 comments ·
Maintainers usually reply within 1 day
-
PHP workflow streaming requests buffer the full SSE responsePossibly taken @Winoren claimed this today. Openreview: medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
langgenius/dify#44270 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
area:holodeck review-finding
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
hyperdrive-technology/holodeck#142 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
code-yeongyu/senpi#3573 ·
Maintainers usually reply within 1 day