[Feature Request] Add Flint as a Default file open destination in Codex App

Open 💬 0 comments Opened Jul 26, 2026 by shenghsi

What variant of Codex are you using?

Codex App (macOS desktop; Flint also supports Linux and Windows)

What feature would you like to see?

Please add Flint as a first-class option in the Codex App's Default file open destination picker.

Flint is a terminal-first fork of Zed built for developers who use CLI agents such as Codex, Claude Code, and Pi. It combines files, terminals, diffs, Git state, and persistent CLI-agent sessions in one workspace, so it is a natural destination for opening files and worktrees from Codex.

Expected behavior:

  • When Flint is installed, show Flint in Settings → Default file open destination and the relevant Open in menus.
  • Open folders/worktrees with flint <path>.
  • Preserve file locations when available using Flint's supported path:line:column syntax.
  • Detect the native installation on supported platforms.

Useful macOS integration details:

  • App path: /Applications/Flint.app
  • Bundle ID: dev.flint.Flint
  • Bundle executable: flint
  • Optional CLI installed by Flint: /usr/local/bin/flint

Additional information

Codex now supports custom file handlers through [desktop.custom_file_handlers.<id>] in config.toml (the general request in #10428 was closed as completed). That is a useful fallback, but a built-in Flint target would be discoverable, include the correct icon and detection behavior automatically, and avoid requiring every user to create and maintain local configuration.

Related general requests: #10428, #15373, and #27015.

Flint supports macOS, Linux, and Windows and provides a cross-platform CLI. Its CLI accepts files and folders directly and supports path:line:column for precise navigation.

View original on GitHub ↗