macOS: allow arbitrary apps or custom commands for "Default open destination"
Open 💬 5 comments Opened Mar 21, 2026 by adityasrini
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
I want to use a custom wrapper app for IntelliJ IDEA LightEdit in the macOS app.
Right now, the "Default open destination" setting appears to offer a fixed set of supported apps such as VS Code, Finder, Terminal, IntelliJ IDEA, and WebStorm. It does not appear to use the normal macOS app picker or LaunchServices app list.
My use case:
- I want files opened from ChatGPT/Codex to go to IntelliJ LightEdit, which I can launch from the CLI with
idea -e. - I created a wrapper
.appbundle that shells out toidea -efor files and normalideafor directories. - I gave the wrapper a bundle ID and registered it with LaunchServices.
- The wrapper still does not appear in "Default open destination".
Expected behavior:
- Let users choose any installed
.appas the open destination.
A better version:
- Add a custom command option with a placeholder for the selected path, for example:
/path/to/idea -e {path}
Why this matters:
- Some editors support alternate open modes such as LightEdit.
- Some users want project folders and single files to open differently.
- A fixed allowlist blocks valid macOS app workflows even when the app bundle is installed and registered correctly.
Environment:
- macOS
26.3.1 (a) (25D771280a) - Codex
Version 26.318.11754 (1100) - Reproduced on March 21, 2026
Repro:
- Create and register a normal
.appwrapper on macOS. - Open ChatGPT/Codex macOS settings.
- Go to "Default open destination".
- Try to select the wrapper app.
Actual:
- The wrapper app does not appear.
Expected:
- The wrapper app appears, or the app exposes a custom command option.
5 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
This is not a duplicate of and is more of a super set of the linked #12988 issue. Additionally, the linked issue further links to other closed issues that don't have a clear resolution to this feature request.
Workaround: Use any app as Codex's "Default open destination" on macOS
Codex uses a hardcoded allowlist of known editors for its "Default open destination" dropdown. Custom
.appbundles don't appear even when properly registered with Launch Services. This workaround creates a tiny AppleScript app that masquerades as a recognized editor (e.g. TextMate) but routes every file to its real macOS default handler — so files open in whatever app macOS would normally use.This also works if you want files to always open in a specific app that is NOT already the default macOS handler (like Zed, Alacritty+Neovim, IntelliJ LightEdit, etc.) — just modify the AppleScript in the script below.
Install
Save this as
install.sh, runchmod +x install.sh, then./install.sh:Then open Codex → Settings → Default open destination → select TextMate.
Files will now route through the fake TextMate to their real default macOS handler.
Customization
Want files to open in a specific app instead? Change the
do shell script "open "line in the script:Already have TextMate installed? Change
APP,CFBundleName, andCFBundleIdentifierto a different editor from Codex's allowlist that you don't use:| Editor | App name | Bundle ID |
|--------------|---------------------|------------------------------|
| TextMate |
TextMate.app|com.macromates.TextMate|| BBEdit |
BBEdit.app|com.barebones.bbedit|| Sublime Text |
Sublime Text.app|com.sublimetext.4|Great workaround! Tested it locally and it works! Would still be a good idea to make this natively supported so devs don't have to resort to hacking Applications to tricking Codex to working.
Also, I assume you vibecoded this solution to my vibecoded issue 😄
How to pass a $LINE and $COLUMN there?