›_ Codex Issues
Codex Issues / #19675

Codex Desktop: make “Open in target” dropdown customizable (add Obsidian, replace Finder with Path Finder)

Open 💬 4 comments Opened Apr 26, 2026 by ybennaoum
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What variant of Codex are you using?

Codex Desktop App Version 26.422.30944 (2080) (macOS)

What feature would you like to see?

I’d like the Open in target dropdown in Codex Desktop to be user-customizable.

Current behavior

The dropdown appears fixed to built-in targets (for example: VS Code, Cursor, Zed, Antigravity, Finder, Terminal, Warp).
I cannot add Obsidian, and I cannot replace/hide Finder in favor of Path Finder.

Requested behavior

Please allow users to:

  1. Add custom app targets by app path (example: /Applications/Obsidian.app)
  2. Disable/hide built-in targets (example: hide Finder)
  3. Reorder dropdown targets
  4. Keep global default + per-path overrides

Why this matters

Different workflows need different tools:

  • coding -> VS Code/Cursor
  • notes/knowledge base -> Obsidian
  • file management -> Path Finder

A fixed target list blocks practical workflows and forces workarounds.

In-app feedback correlation

Feedback ID: 019dc9f7-eff4-7040-869a-8001c10c5d3f

Additional information

Related but not identical request: https://github.com/openai/codex/issues/18294

This request is specifically about making the desktop Open in target dropdown configurable (custom targets + hide/replace built-ins), not only general Obsidian integration.

View original on GitHub ↗

4 Comments

github-actions[bot] contributor · 4 months ago

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

  • #18859
  • #18825

Powered by Codex Action

blackappleD · 3 months ago

+1 for this, especially for document/Markdown opening workflows.

A common Codex Desktop workflow is generating or navigating .md notes, specs, meeting notes, and docs that are better opened in Obsidian than in a code editor. It would be very helpful if the "Open in target" / document-opening flow could support Obsidian as a first-class or configurable target.

Desired behavior:

  • Allow Obsidian to be selected as an open target for Markdown/document links.
  • Support custom app paths/commands across platforms, including Windows Obsidian installs, not only macOS .app bundles.
  • Ideally support Obsidian URI-style opening as well, for example obsidian://open?..., so files inside a vault can open in the right context.

This would make Codex much smoother for knowledge-base and documentation workflows where the repository or project includes an Obsidian vault.

mneuschaefer · 2 months ago

+1 for this request.

My concrete use case is opening Codex Desktop file links in Obsidian for Markdown-heavy workspaces / vaults.

Local observation: desktop.open-in-target-preferences already supports global and perPath, but the target value appears limited to built-in targets. Obsidian is installed on macOS as /Applications/Obsidian.app with bundle ID md.obsidian, but there is no way to add it as a custom target.

The current workaround is using systemDefault and changing the global macOS Markdown file association to Obsidian, but that is too broad and does not allow a per-project Codex preference.

A custom target by app path, bundle ID, command template, or URI template like obsidian://open?path={encoded_absolute_path} would solve this well.

AndersMad · 2 months ago

+1 for adding custom URI template like my-custom-env://path={encoded_absolute_path};line={line_number} - also making it easy to open e.g. vs.net in current/preferred environment at line number (or range/multiple)

I bet many already has such own URI handler app for stack traces etc.

And minor: also opt. out of an "open with".