Repository navigation
Opencode Desktop command not found errors #15758
Description
Description
Opencode is repeatedly unable to find installed commands on my mac such as npm, bun, ripgrep, etc.
My system is using fnm to manage node versions, but bun is just installed via their script and also does not work. This is not the case within my terminal.
Plugins
None
OpenCode version
1.2.15
Steps to reproduce
- Install opencode desktop on mac
- Open it
- Ask it to run a node / npm / bun command of some kind
Interestingly, this can be fixed by running the app from the terminal with open -a opencode.app. I have no idea why. I learned this from here.
Other interesting side effects of this include MCPs just not loading unless the app is opened via that open command.
On my system I am using zsh + oh my zsh. Nothing fancy beyond that.
Happy to provide any additional info needed!
Screenshot and/or share link
Repro:
https://opncd.ai/share/tob6mAWK
https://fs.liam.so/s/SCR-20260302-lcw.png
Others running into the same issue:
https://discord.com/channels/1391832426048651334/1435327295953961133/1475174917258477722
https://discord.com/channels/1391832426048651334/1391832428024430645/1423597769850884136
Operating System
Macos Tahoe 26.2
Terminal
Ghostty
Activity
github-actions commentedon Mar 2, 2026
This issue might be a duplicate of existing issues. Please check:
bunxcannot be resolved for local MCP server (Executable not found in $PATH) #15565: Same root cause - macOS Desktop app does not inherit the shell's $PATH, causing executables likebun,bunx,npm, etc. to not be found, including MCP servers failing to load.Lermatroid commentedon Mar 2, 2026
Not sure if its related, but I am also running into the issue outlined here where opencode desktop is constantly asking for permission to random things like other apps' data, apple music, photos, etc.
#14982
nexxeln commentedon Mar 3, 2026
This is a known issue and is being actively worked on. It will be fixed in the coming releases
Lermatroid commentedon Mar 4, 2026
Great to hear, still seems to be happening after updating to
v1.2.16.Chathula commentedon Apr 21, 2026
Still same issue.
mdaffailhami commentedon May 9, 2026
Having this issue too today
github-actions commentedon Jul 9, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.