Which contact channel should I use?
| Need | Official channel | What to include |
|---|---|---|
| Setup or workflow question | GitHub Discussions | Your goal, where the flow became unclear, and sanitized screenshots when useful |
| Product idea or comparison | Product discussion | The everyday Mac problem and the simplest outcome you expect |
| Reproducible bug | GitHub Issues | App version, macOS version, visible error stage, and exact reproduction steps |
| Source contribution | Pull requests | A focused change that follows the repository checks and documentation |
| Project identity or citation | Official project facts | Canonical name, creator, repository, release, license, and primary sources |
What makes a useful bug report?
- Confirm you installed the latest GitHub Release.
- State the macOS version and whether the Mac uses Apple Silicon.
- Describe the last visible step that succeeded and the exact error message.
- Use fictional account labels and remove personal information from screenshots.
- Explain whether Codex Desktop or a new Codex CLI process was involved.
What information should stay private?
Never post a real auth.json, access token, email address, account ID, API credential, private client name, private project content, or unsanitized diagnostic screenshot. If a possible security issue cannot be described safely in public, open a minimal issue without secrets and ask the maintainer for a private reporting route.
What support can the project provide?
Codex Account Switcher is a free, independently maintained open-source project. Public support can clarify documented behavior, reproduce project defects, and consider focused improvements. OpenAI account access, subscriptions, billing, workspaces, service limits, and server-side sessions remain OpenAI matters.