macOS app: 'Open config.toml' button in Settings is unresponsive
Resolved 💬 6 comments Opened Feb 5, 2026 by malpern Closed Feb 24, 2026
💡 Likely answer: A maintainer (etraut-openai, contributor)
responded on this thread — see the highlighted reply below.
Summary
The Settings → Configuration → Open config.toml button is unresponsive in the Codex macOS app.
Steps to Reproduce
- Open Codex app
- Go to Settings → Configuration
- Click "Open config.toml"
Expected
The config file opens in the default editor (or a file-open dialog appears).\n\n## Actual\nNothing happens—no file opens, no error, no visual feedback.
Environment
- Codex macOS app\n- macOS version: unknown
- Codex app version/build: unknown
Notes
- Config exists at ~/.codex/config.toml
- App restart does not change behavior
6 Comments
I'm not sure what process you used to file the bug report, but I needed to reformat it so it's readable. It had embedded
\ncharacters rather than real end-of-line characters.I'm not able to repro the problem as reported. I'm guessing that it's related to the "Default open designation" that you have selected. Confirm that you've selected a valid editor.
I'm here because I have the same issue. No problems with accessing any settings I've tried except the button to open the config.toml file does nothing. I've tried it many times since installing Codex.
@brobm, do you have a "Default open destination" editor selected in the "General" panel?
<img width="717" height="159" alt="Image" src="https://github.com/user-attachments/assets/b14762d2-42a7-41f1-ab68-5c056e516fe8" />
The only options I see are _Terminal_ and _Finder_ (_Terminal_ is currently selected). I switched to _finder_, and that shows me the file in the Finder. Which I see as success!
Note I'm a beginner at this stuff, and I now realize I kept adding stuck Terminal windows opened behind Codex each time I clicked this button.
Ah yes, that explains it. Most developers have an IDE or editor installed on their system — for example, VS Code or Cursor.