Add support for Kiro in "Open In" menu

Resolved 💬 3 comments Opened Feb 27, 2026 by tavlean Closed May 10, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the Codex App are you using (From “About Codex” dialog)?

26.226.940 (720)

What subscription do you have?

Plus

What platform is your computer?

Darwin 25.3.0 arm64 arm

What issue are you seeing?

Codex shows multiple installed IDE/terminal options in the Open in… dropdown, but it does not show Kiro (Amazon) even though Kiro is installed and usable on this machine.

What steps can reproduce the bug?

  • Install Kiro on macOS (app is present in /Applications/kiro.app)
  • Open Codex Desktop.
  • Open any workspace/thread.
  • Click the Open in… dropdown.
  • Observe that many IDEs/terminals are listed, but Kiro is not listed.

What is the expected behavior?

If Kiro is installed, it should appear in the Open in… dropdown like other detected IDEs/terminals.

Additional information

Kiro is a VS Code-based IDE (fork), so I’d expect it to be detected similarly to VS Code/Cursor/Windsurf.

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 6 months ago

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

  • #12472
  • #12933
  • #11190

Powered by Codex Action

rahulxsomething · 5 months ago

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 .app bundles 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, run chmod +x install.sh, then ./install.sh:

#!/bin/zsh
set -eo pipefail

APP="/Applications/TextMate.app"

# 1. Create the AppleScript
SCRIPT=$(mktemp /tmp/open-default-XXXXX.applescript)
cat > "$SCRIPT" << 'AS'
on open theFiles
  repeat with aFile in theFiles
    do shell script "open " & quoted form of POSIX path of aFile
  end repeat
end open
AS

# 2. Compile into an app bundle
osacompile -o "$APP" "$SCRIPT"
rm "$SCRIPT"

# 3. Write the Info.plist (must declare Editor role + droplet executable)
cat > "$APP/Contents/Info.plist" << 'PLIST'
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"
  "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
  <key>CFBundleName</key>
  <string>TextMate</string>
  <key>CFBundleIdentifier</key>
  <string>com.macromates.TextMate</string>
  <key>CFBundleVersion</key>
  <string>1.0</string>
  <key>CFBundleShortVersionString</key>
  <string>1.0</string>
  <key>CFBundlePackageType</key>
  <string>APPL</string>
  <key>CFBundleSignature</key>
  <string>????</string>
  <key>CFBundleExecutable</key>
  <string>droplet</string>
  <key>CFBundleIconFile</key>
  <string>droplet</string>
  <key>CFBundleDocumentTypes</key>
  <array>
    <dict>
      <key>CFBundleTypeName</key>
      <string>Plain Text</string>
      <key>CFBundleTypeRole</key>
      <string>Editor</string>
      <key>LSItemContentTypes</key>
      <array>
        <string>public.plain-text</string>
        <string>public.utf8-plain-text</string>
        <string>public.source-code</string>
        <string>public.script</string>
        <string>public.shell-script</string>
        <string>public.python-script</string>
        <string>public.ruby-script</string>
        <string>public.perl-script</string>
        <string>public.c-source</string>
        <string>public.c-header</string>
        <string>public.c-plus-plus-source</string>
        <string>public.objective-c-source</string>
        <string>public.swift-source</string>
        <string>public.assembly-source</string>
        <string>public.json</string>
        <string>public.xml</string>
        <string>public.yaml</string>
        <string>com.apple.property-list</string>
        <string>com.netscape.javascript-source</string>
        <string>public.css</string>
        <string>public.html</string>
      </array>
    </dict>
  </array>
  <key>NSAppleEventsUsageDescription</key>
  <string>This app routes files to their default macOS handler.</string>
  <key>LSUIElement</key>
  <true/>
</dict>
</plist>
PLIST

# 4. Register with Launch Services
/System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -f "$APP"

echo "Installed: $APP"

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:

-- Zed:
do shell script "/usr/local/bin/zed " & quoted form of POSIX path of aFile

-- Neovim via Alacritty:
do shell script "open -a Alacritty -- nvim " & quoted form of POSIX path of aFile

-- IntelliJ LightEdit:
do shell script "/usr/local/bin/idea -e " & quoted form of POSIX path of aFile

Already have TextMate installed? Change APP, CFBundleName, and CFBundleIdentifier to 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 |

etraut-openai contributor · 3 months ago

This feature request hasn't received enough upvotes, so I'm going to close it.