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_

View original on GitHub ↗

6 Comments

github-actions[bot] contributor · 2 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #18825

Powered by Codex Action

rnichollx · 2 months ago

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.

etraut-openai contributor · 1 month ago

This feature request hasn't received enough upvotes, so I'm closing.

rnichollx · 1 month ago

Doesn't look like this was "completed"

loloxwg · 4 days ago

Still reproducible on macOS with Codex App 26.707.72221. CLion 2026.1.4 is installed by JetBrains Toolbox at ~/Applications/CLion.app (bundle ID com.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.

loloxwg · 4 days ago

I found and verified a user-level workaround on macOS with Codex App 26.707.72221 and CLion 2026.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 .icns directly):

mkdir -p "$HOME/.codex/icons"
sips -s format png -z 64 64 \
  "$HOME/Applications/CLion.app/Contents/Resources/clion.icns" \
  --out "$HOME/.codex/icons/clion.png"

Then add this to ~/.codex/config.toml, replacing <username> with the macOS account name:

[desktop.custom_file_handlers.clion]
label = "CLion"
icon = "/Users/<username>/.codex/icons/clion.png"
command = "/Users/<username>/Applications/CLion.app/Contents/MacOS/clion"
args = []
input = "path"
supports_ssh = false

Optionally, make it the default for a project by adding the entry to the existing per-path table:

[desktop.open-in-target-preferences.perPath]
"/absolute/path/to/project" = "custom:clion"

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/read response that the handler appears at config.desktop.custom_file_handlers.clion and the per-project target resolves to custom:clion.

This is a useful workaround, but built-in CLion detection would still be preferable.