›_ Codex Issues
Codex Issues / #22629

Feature request: Support Trae IDE as an editor target in Codex Desktop

Open 💬 2 comments Opened May 14, 2026 by fmnisme

Feature request

Please add Trae / Trae CN as a supported editor target in the Codex Desktop app's "Open in editor" picker.

Motivation

Trae is a VS Code fork, and on macOS it exposes a VS Code-compatible CLI. Codex Desktop already supports editor targets such as VS Code, Sublime Text, Zed, Finder, Terminal, iTerm2, Xcode, GoLand, and RustRover. Adding Trae would let users open files and file locations from Codex Desktop directly in Trae.

Local environment

  • Codex Desktop: macOS app
  • macOS: macOS 15.6.1, Apple Silicon
  • Trae app path: /Applications/Trae CN.app
  • Trae bundle ID: cn.trae.app
  • Trae CLI paths:
  • /Applications/Trae CN.app/Contents/Resources/app/bin/trae-cn
  • /Applications/Trae CN.app/Contents/Resources/app/bin/code

Compatibility notes

The Trae CLI appears to support VS Code-style arguments, including:

trae-cn --goto <file:line[:character]>

I verified that launching Trae with a file location through --goto works locally.

Expected behavior

Codex Desktop should show "Trae" or "Trae CN" in the editor target picker. When selected, opening a file from Codex should run the Trae CLI with VS Code-compatible --goto arguments.

Suggested implementation

This could likely reuse the existing VS Code editor target implementation, with Trae-specific detection paths on macOS:

/Applications/Trae CN.app/Contents/Resources/app/bin/trae-cn
/Applications/Trae CN.app/Contents/Resources/app/bin/code

Optional additional target:

/Applications/TRAE SOLO CN.app/Contents/Resources/app/bin/trae-solo-cn

Related issue

There is an existing TRAE-related issue for the IDE extension:
https://github.com/openai/codex/issues/15780

This request is different: it is about Codex Desktop supporting Trae as an external editor target.

View original on GitHub ↗

2 Comments

jiangyuan · 3 months ago

Additional data point from another user.

I am seeing the same need in Codex Desktop. On my machine the current values are:

  • Codex Desktop: 26.513.31313
  • macOS app: /Applications/Codex.app
  • Trae app: /Applications/Trae CN.app
  • Trae version: 3.3.57
  • Bundle ID: cn.trae.app
  • URL scheme: trae-cn
  • CLI on PATH: /usr/local/bin/trae
  • CLI symlink target: /Applications/Trae CN.app/Contents/Resources/app/bin/marscode

The CLI supports the VS Code-compatible open semantics Codex already uses for editor targets:

trae --goto <file:line[:character]>
trae --reuse-window <path>

From inspecting the local Codex Desktop bundle, the Open in picker appears to use a fixed built-in target list plus persisted preferences under open-in-target-preferences. Since Trae is not in the built-in target list, users cannot add it through configuration today. A built-in Trae / Trae CN target, or a custom editor target config, would cover this use case.

CedricXing · 2 months ago

Here is a local workaround I verified for Codex Desktop on macOS.

Codex Desktop does not currently allow arbitrary custom editor targets. The open-in-target-preferences value is validated against a fixed built-in target list, so setting global = "trae" does not work today.

However, Trae’s CLI is compatible with the VS Code-style arguments Codex already uses. I worked around this by reusing the built-in vscodeInsiders target and pointing its expected CLI path to Trae:

mkdir -p "$HOME/Applications/Code - Insiders.app/Contents/Resources/app/bin"
ln -sfn /usr/local/bin/trae \
  "$HOME/Applications/Code - Insiders.app/Contents/Resources/app/bin/code"

Then set Codex Desktop’s default open target to vscodeInsiders:

[desktop.open-in-target-preferences]
global = "vscodeInsiders"

After restarting Codex Desktop, file opens go through the VS Code Insiders target, but the actual executable is Trae. This works because Codex sends VS Code-compatible arguments such as:

code --goto /path/to/file:line:column

and Trae accepts the same form:

trae --goto /path/to/file:line:column

This is only a workaround. The picker still shows VS Code Insiders rather than Trae, and it depends on Codex Desktop’s current hardcoded detection paths. A proper fix would still be to add a first-class Trae / Trae CN editor target in Codex Desktop.