[Bug]: Native account-switch confirmation layout breaks in German; switching workflow is hard to follow
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- authentication, frontend
Research direction
Start at the local dashboard URL http://localhost:10100/#codex-set and inspect the native main-login management panel's confirmation state with German text, dark theme, and 110% zoom. Reproduce the narrow wrapping and overflow, then trace the existing switch workflow. Done means readable responsive content and contained actions, clear close-confirm-reopen guidance, actionable blocked-state retry behavior, and refreshed active-profile status after success.
Written by the indexing model from the issue text.
Description
Client or integration
OpenCodex dashboard
Area
Dashboard / Authentication and account pool
Summary
In v2.75.0, the native Codex main-login switch confirmation has a broken layout. The confirmation is difficult to read and use, and the account-switching workflow needs clearer guidance through closing Codex, confirming the switch, and reopening it.
Reproduction
- Open the local dashboard at
http://localhost:10100/#codex-set. - Use German language and the dark theme. Chrome browser zoom is 110%.
- Under Codex settings → Multi-Auth, open the native main-login management panel.
- With two saved native profiles, click the action to switch to the inactive profile.
- Inspect the confirmation panel before checking the acknowledgement or confirming.
Observed in a supplied screenshot on a large desktop window. Reproduction at other zoom levels/languages has not been tested.
Actual behavior
- The heading “Native Anmeldung zu [profile] wechseln” wraps into an extremely narrow column, often one character per line.
- The effective
CODEX_HOMEpath also wraps almost one character per line. - The explanatory text and acknowledgement occupy cramped columns alongside the heading/path rather than a readable stacked layout.
- The confirm button extends beyond the right edge of the highlighted confirmation panel.
- The result is an excessively tall confirmation panel even though the surrounding page has ample horizontal space.
The screenshot shows the unchecked acknowledgement and the open confirmation panel. This report does not establish a backend credential-switch failure.
Expected behavior
- Show the target profile, explanation, effective home, acknowledgement, and actions in a readable responsive layout.
- Keep both action buttons within the panel; wrap or stack them when needed.
- Support German text, long home paths, and 110% browser zoom without character-by-character wrapping.
- Keep the native-login action visually distinct from selecting a pool account for the next request.
Account-switching usability
The current confirmation tells the user to close native Codex first and says a restart may be needed. Please make the existing safety requirement a clear sequence: close Codex → confirm the native profile switch in the dashboard → show the result and whether to reopen/restart Codex.
If a running client prevents switching, show an actionable blocked state and let the user retry after closing it. After success, refresh the native active-profile/main-login display so the user can verify the switch. Preserve the process checks and credential protections.
Version
ocx --version: opencodex 2.75.0 (also visible in the dashboard).
Operating system
macOS 26.6.2; Google Chrome; German dashboard; dark theme; browser zoom 110%.
Provider and model
OpenAI native Codex login profiles. No model-specific request is involved.
Logs or error output
No backend error was observed or collected. The evidence is the rendered confirmation UI.
Screenshots and supporting files
The reporter supplied a screenshot showing the layout defects described above. The original contains personal account labels, a local home path, and unrelated browser tabs, so it is omitted from this public report.
Additional context
Related completed native-profile dashboard work: #3417. This report concerns the shipped confirmation layout and the usability of that workflow.
Checks
- I searched existing issues and the related native-profile workflow report.
- I removed secrets, tokens, account details, request credentials, and personal data.
- Dominant language
- TypeScript
- Stars
- 16.9k
- Forks
- 1.3k
- Avg merge
- 7h 38m
- Merged PRs (30d)
- 659
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
-
[Bug]: Business Premium seat plan self_serve_business_prolite is counted at baseline capacity weight 1 instead of 5Possibly taken A pull request linked to this issue is open or already merged. Openaccount-pool bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
lidge-jun/opencodex#7440 · 2 comments ·
Maintainers usually reply within 1 day
-
[Docs]: translate the #7395 OpenGateway and Mistral provider-guide sectionsPossibly taken @MannXo claimed this 1 day ago. Opendocumentation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
lidge-jun/opencodex#7405 · 3 comments ·
Maintainers usually reply within 1 day
-
bug cli
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
lidge-jun/opencodex#7403 · 2 comments ·
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
-
enhancement proxy
Difficulty 4/5 1-2 days Newbie friendliness 55/100
lidge-jun/opencodex#7443 · 3 comments ·
Maintainers usually reply within 1 day
All issues in lidge-jun/opencodex
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
mobile-next/mobile-mcp#526 ·
Maintainers usually reply within 1 day
-
e2e-failure ready-to-code
Difficulty 1/5 Under an hour Newbie friendliness 73/100
redhat-developer/rhdh-plugin-export-overlays#4470 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
anthropics/anthropic-sdk-typescript#1273 ·
Maintainers usually reply within 10 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
CopilotKit/OpenBot#815 ·
Maintainers usually reply within 1 day