A LITTLE HELP, WHEN YOU NEED IT
Make yourself
at home.
For help, email luka@picktek.com. Include your macOS, Launcher and Codex versions and what you expected to happen. Do not send account tokens, auth.json, private conversations or your profile folder.
Get started
- Install the official Codex desktop app from OpenAI in Applications. Its filename can vary; Launcher identifies the signed app.
- Open Codex Launcher and choose Start fresh or Bring my Codex.
- Choose your library through the native folder dialog. The default is ~/Developer/codex-launcher. Named profiles live at its root; launcher support files live in _codex_launcher.
- On first Open in the App Store edition, allow the preselected Application Scripts folder. Launcher sets up its profile helper automatically. No scripts or terminal commands are required.
- Sign in inside each fresh Codex window. Use Open, Focus and Close on its Launcher card.
Bring my Codex
Choose the existing Codex home, usually ~/.codex. Launcher copies saved conversations and settings, snapshots SQLite databases and verifies the copy. For worktrees that refer to Git metadata elsewhere, a native prompt asks for that specific folder. Supported worktrees become independent repositories; their uncommitted files are retained.
Every original stays in place. This is a snapshot of saved data during the copy, not ongoing synchronization. Work still running may save later changes that are not included. Desktop browser storage and OS permissions start fresh. File-based sign-in is copied when available, but a fresh sign-in may still be required. Keychain-only credentials are not exported.
External project folders and external symbolic links keep their original targets, so those files remain shared. Queued work and schedules do not run in the copy. Submodules, linked Git metadata and shared object stores are not automatically migrated. If verification fails, Launcher keeps the source and recovery copy and explains the error.
Common questions
Why is a profile asking me to sign in?
Fresh profiles start with empty desktop storage. Migration cannot promise reusable sign-in for every credential backend. Sign in in that profile’s Codex window, then choose Profiles → Refresh Accounts in Launcher.
Why can’t Launcher focus or close an instance?
Launcher checks the PID, process start time and exact profile identity. It refuses ambiguous or stale matches. Use Open to recover a known profile; close an unrecognized instance from that Codex window.
What does rename change?
Rename changes the profile’s display name. Its folder stays in place so saved absolute paths remain valid. Reveal Folder opens its existing folder in Finder.
How do updates work?
Launcher quietly checks OpenAI’s public Codex release feed. “Up to date” means the installed build is at least as new as that public release. The App Store edition opens OpenAI’s website for installation or updates. Launcher itself updates through the App Store when available.
Why don’t I see Dock labels?
Dock overlays are available only in the local edition with Accessibility permission. They are not included in the App Store edition.
Can I change the library or appearance?
Open Settings with ⌘,. Close managed profiles before switching libraries. Switching does not move the old library. Choose Light, Dark or System; animations follow your Mac’s Reduce Motion setting. Use ⌘N to add a profile, ⌘R to refresh accounts and ⌘1–9 to open profiles.
What if a future Codex update changes profile support?
The desktop storage override is undocumented. Compatibility can change with an OpenAI release. Keep your original data and contact support if a profile fails after an update. Launcher does not modify the official app.