Add detection for CLion
Resolved 💬 6 comments Opened Apr 22, 2026 by rnichollx Closed May 31, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What variant of Codex are you using?
MacOS App
What feature would you like to see?
Looks like most JetBrains IDEs are detected, but for some reason JetBrains CLion is not. Suggest detecting CLion for C++ as well.
Additional information
_No response_
6 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Example image where CLion does not show up:
<img width="802" height="719" alt="Image" src="https://github.com/user-attachments/assets/c53404bd-0c4f-4407-8742-2d878dc5c231" />
Looks like the application is in ~/Applications when installed via toolbox.
This feature request hasn't received enough upvotes, so I'm closing.
Doesn't look like this was "completed"
Still reproducible on macOS with Codex App 26.707.72221. CLion 2026.1.4 is installed by JetBrains Toolbox at
~/Applications/CLion.app(bundle IDcom.jetbrains.CLion). RustRover, PyCharm, and WebStorm from the same location appear in the Open in menu, but CLion does not.This issue does not appear to be completed in the current release. Please consider reopening it.
I found and verified a user-level workaround on macOS with Codex App
26.707.72221and CLion2026.1.4.The important detail is that the custom handler must be nested under
desktop. A top-level[custom_file_handlers.clion]table is parsed as a config layer but does not enter the app's effective desktop configuration.First, create a PNG icon (Chromium does not reliably render the CLion
.icnsdirectly):Then add this to
~/.codex/config.toml, replacing<username>with the macOS account name:Optionally, make it the default for a project by adding the entry to the existing per-path table:
Fully quit Codex with Cmd+Q and reopen it. CLion then appears in the Open in menu and can be selected normally.
I also verified through the app-server
config/readresponse that the handler appears atconfig.desktop.custom_file_handlers.clionand the per-project target resolves tocustom:clion.This is a useful workaround, but built-in CLion detection would still be preferable.