[Bug]: IntelliJ IDEA not detected on macOS when the Toolbox app bundle has a version in its name #15933

Activity

1. juliusmarminge commented on Oct 5, 2026

   

   juliusmarminge

   on Oct 5, 2026

   Member

   More actions

   Note

   Grok responding on behalf of Julius.

   Triage

   Thanks @saibotma for the precise report, with line links and a working workaround. It matches the resolver on current main (37de6cbde65c).

   What I found

   • resolveEditorCommand in packages/shared/src/editor.ts only treats idea as the IntelliJ command (packages/contracts/src/editor.ts). On macOS it then tries exact paths: ~/Applications/<name>.app and /Applications/<name>.app for IntelliJ IDEA, IntelliJ IDEA CE, and IntelliJ IDEA Ultimate, plus ~/Library/Application Support/JetBrains/Toolbox/scripts/idea.
   • IntelliJ IDEA 2026.1.4.app matches none of those bundle names, because the macOS branch never lists the Applications directories. The Windows branch does, and accepts entry === name || entry.startsWith(${name} ), which is why WebStorm 2026.2 is covered there (and in apps/server/src/process/externalLauncher.test.ts). The darwin fixtures only use an exact WebStorm.app.
   • A Toolbox script named idea1 misses the same way: the PATH check only looks up idea, and the scripts fallback only checks that one filename. Toolbox generates a unique script name when more than one version is installed, so this layout is fairly common.
   • The two checks don't cover for each other, so an install with both a versioned bundle and a non-idea script isn't found at all. Renaming the script to idea works because it hits the scripts fallback.
   • The same exact-name construction is shared by the other JetBrains editors, including PyCharm and Rider. fix: intellij not being visible even though it's installed #1828 and fix: detect installed editors outside PATH #12439 are the earlier "installed but not on PATH" work; fix: detect installed editors outside PATH #12439 added these exact paths.

   Likely fix area

   The darwin branch of resolveEditorCommand. One option is to list ~/Applications and /Applications and accept <name>.app or <name> <version>.app with the same prefix rule Windows uses, still launching Contents/MacOS/<command>. That would cover the other JetBrains apps in the same pass. Separately, the Toolbox scripts lookup only checks the canonical command name on every platform, which could be handled here or in a follow-up. A darwin test next to the existing Windows WebStorm 2026.2 case would help lock in the behavior.

   A maintainer will decide on the fix direction.
2. juliusmarminge

   added

   bugSomething is broken or behaving incorrectly.Something is broken or behaving incorrectly.

   via-triageFiled through npx t3 triageFiled through npx t3 triage

   on Oct 5, 2026