Make open button configurable #7055

Yes please. I want Sublime Text in there.

#7109 adds an implementation and screenshots for configurable applications in the Open menu, including discovery on the connected environment. Keeping that prior work linked here as the two proposals are consolidated.

Opened #22289 for this. On macOS the server asks LaunchServices which apps are installed, by bundle id, so Open in lists only apps that are actually there, including ones without a CLI on PATH. It also adds Xcode, Sublime Text, Devin Desktop, Android Studio, Nova and BBEdit, terminals (Terminal, iTerm2, Ghostty, kitty, WezTerm, Warp) and git clients (GitHub Desktop, Fork, Sourcetree). Happy to split it into smaller PRs if that is easier to review.

Notepad++ please

+1, with Obsidian as the case. It has no CLI on PATH by default, so command-based detection never finds it, but it opens reliably through obsidian://open?path=<absolute path>.

I tried it as a built-in entry in a private fork, and two details came up that any configurable version would want to handle:

1. Obsidian only opens files inside a vault it knows. The vault list is in ~/Library/Application Support/obsidian/obsidian.json on macOS (~/.config/obsidian/obsidian.json on Linux), so a path outside every vault can fail with a clear message instead of silently opening the last note.
2. Obsidian cannot open a folder. The project-level "Open in" passes a folder, so opening a note inside it works better: <folder>.md, then README.md, index.md, or CLAUDE.md, falling back to the vault. The folder list then shows where you are.

A user-defined entry would cover most of this if it allows a URL template rather than only a command.

+1, being able to open worktrees directly in Warp would be huge. It already works when I prompt an agent to do it.

+1. My use case is Positron. It is a fork of VS Code, so it would need only one entry in EDITORS, which is close to the existing VSCodium entry. A configurable Open menu would also cover it.

Details that a built-in entry would need on macOS:

• Bundle id: co.posit.positron
• CLI: /Applications/Positron.app/Contents/Resources/app/bin/code. This is the VS Code CLI, so the goto launch style applies.
• URL scheme: positron, the same pattern as vscode and vscodium for remoteScheme

I'm happy to open a PR that adds Positron as one entry if a maintainer approves that scope. I'd also be happy for the configurable list to land.

+1, for Xcode. For iOS projects the folder holds an .xcodeproj / .xcworkspace, and the Open menu offers VS Code and Finder but not the editor the project is actually built in.

Xcode already ships a CLI, xed (/usr/bin/xed, resolved through xcode-select), so a built-in entry would be small:

• Detect: xed on PATH, or bundle id com.apple.dt.Xcode
• Open project: if the folder has a single .xcworkspace (else .xcodeproj, else Package.swift), open that file. Otherwise run xed <dir>.
• Open file at line: xed --line <n> <file> (add --project <workspace> so the file opens in the project's window)

#22289 included an Xcode entry along these lines before it was closed for the prior-approval requirement.