Support editor discovery in ~/Applications on macOS#2722
Conversation
- Resolve editors from user or system Applications on macOS when the CLI is missing - Add coverage for available-editor detection and launch path resolution
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit bbfbb23. Configure here.
ApprovabilityVerdict: Approved This PR adds a well-scoped, low-risk feature for macOS editor discovery in ~/Applications. The changes are self-contained, additive (existing behavior preserved as fallback), and thoroughly tested. You can customize Macroscope's approvability policy. Learn more. |
- Search /Applications even when HOME is unset - Export mac helper functions for direct test coverage
|
Whoops! Sorry about that.
|

What Changed
The IDE Open button now also checks
~/Applicationson macOS (not just/Applications) when looking for installed IDE apps.If the editor’s CLI command isn’t on
PATH, it can still show up as available if the.appbundle exists, and we launch it usingopen -a.I also added tests to cover:
~/Applicationsopen -awhen the CLI isn’t availableWhy
A lot of people install apps like Cursor / Zed into their user
~/Applicationsinstead of the global/Applications.Before this, the app could say “no installed editors found” (or only show editors installed in the global
/Applications) even though the IDE is clearly installed. This makes the Open button feel broken for normal setups.This keeps behavior predictable:
use CLI if it exists (best experience, supports --goto, etc.)
otherwise fall back to the macOS app bundle (still opens the right folder/file)
Checklist
Note
Medium Risk
Changes editor discovery and launch behavior on macOS by falling back from CLI commands to
.appbundle detection andopen -a, which could affect which editors are listed/used when multiple installs exist. Scope is limited to external launcher logic with added test coverage.Overview
Improves macOS editor integration by discovering
.appbundles in~/Applications(and/Applications) when an editor’s CLI command is missing, so editors can still appear as available.Updates
resolveEditorLaunchto fall back toopen -a <App.app>ondarwinand strips any:line:columnsuffix for app-bundle launches. Adds tests covering user-Applications discovery,HOME-missing behavior, and the new launch fallback path.Reviewed by Cursor Bugbot for commit 1954320. Bugbot is set up for automated code reviews on this repo. Configure here.
Note
Support editor discovery in ~/Applications on macOS
resolveMacApplicationDirectoriesandresolveMacEditorApplicationto locate.appbundles under~/Applicationsand/Applicationswhen no CLI is on PATH.resolveAvailableEditorsnow considers an editor available if its.appbundle exists, even without a CLI.resolveEditorLaunchinvokesopen -a <AppPath> <filePath>when a CLI is missing but the.appbundle is found.Macroscope summarized 1954320.