Repository navigation
[Bug]: Provider paths not detected when launching from finder / dock (MacOS) #2329
Closed as duplicate
Description
Before submitting
- I searched existing issues and did not find a duplicate.
- I included enough detail to reproduce or investigate the problem.
Area
apps/desktop
Steps to reproduce
- Download the application from releases
- Launch the application
- Open Provider Settings
- Providers are showing as not installed / in path
Expected behavior
All providers should be detected as they are in path and installed.
Actual behavior
The app fails to identify any providers, even when the direct path to the binaries are set. Attempted troubleshooting include switching to nightly, granting full disk access, removing .t3 directory.
Impact
Major degradation or frequent failure
Version or commit
0.0.21 (188df6d)
Environment
MacOS 26.1
Logs or stack traces
Screenshots, recordings, or supporting files
No response
Workaround
Launching the application from the terminal by executing the binary in the .app/MacOS directory restores functionality.
/Applications/T3 Code (Alpha).app/Contents/MacOS ❯ ./T3\ Code\ \(Alpha\)
Activity
juliusmarminge commentedon Jun 9, 2026
Duplicate of #317
Same root cause — apps launched from Finder/Dock get launchd's environment rather than your login shell's, so PATH and other env customizations are missing. Consolidating into #317. If launching from a terminal does NOT fix it for you, comment and we'll reopen.