Unable to run commands like ls (ENOENT: no such file or directory, posix_spawn '/bin/zsh') #5

fast-90 commented 2026年01月15日 10:28:49 +01:00

Using opencode.el, my LLM is unable to run commands like ls, which also makes it unable to see what is in the working directory/repo. I says the following:

The bash tool is unable to execute commands due to a shell access issue. The working directory is listed as ~/repos/kairos/ but I cannot access it to list files.

> What error do you get if you try ls?

I get ENOENT: no such file or directory, posix_spawn '/bin/zsh' when trying to run ls or any bash command. This indicates the system cannot find or access the shell (/bin/zsh) to execute commands.

I am running Emacs 31.0.50, MacOS, opencode 1.1.21.

Using opencode.el, my LLM is unable to run commands like `ls`, which also makes it unable to see what is in the working directory/repo. I says the following: > The bash tool is unable to execute commands due to a shell access issue. The working directory is listed as `~/repos/kairos/` but I cannot access it to list files. > > \> What error do you get if you try ls? > > I get `ENOENT: no such file or directory, posix_spawn '/bin/zsh'` when trying to run `ls` or any bash command. This indicates the system cannot find or access the shell (`/bin/zsh`) to execute commands. I am running Emacs 31.0.50, MacOS, opencode 1.1.21.

sczi commented 2026年01月15日 19:09:57 +01:00

I think this is caused by having an unexpanded ~ in the directory we send to opencode. On my machine default-directory always seems expanded, but it looks like in emacs it's allowed to have ~ in it. I added a couple calls to expand-file-name so we shouldn't send ~ anymore, in bac1921, does that fix it for you?

I think this is caused by having an unexpanded `~` in the directory we send to opencode. On my machine `default-directory` always seems expanded, but it looks like in emacs it's allowed to have `~` in it. I added a couple calls to `expand-file-name` so we shouldn't send `~` anymore, in bac1921, does that fix it for you?

fast-90 commented 2026年01月15日 21:59:43 +01:00

@sczi wrote in #5 (comment):

I think this is caused by having an unexpanded ~ in the directory we send to opencode. On my machine default-directory always seems expanded, but it looks like in emacs it's allowed to have ~ in it. I added a couple calls to expand-file-name so we shouldn't send ~ anymore, in bac1921, does that fix it for you?

Unfortunately not, I still have the same issue:

image

This is on the current main branch, which has the bac1921 commit.

@sczi wrote in https://codeberg.org/sczi/opencode.el/issues/5#issuecomment-9889328: > I think this is caused by having an unexpanded `~` in the directory we send to opencode. On my machine `default-directory` always seems expanded, but it looks like in emacs it's allowed to have `~` in it. I added a couple calls to `expand-file-name` so we shouldn't send `~` anymore, in [`bac1921`](/sczi/opencode.el/commit/bac1921), does that fix it for you? Unfortunately not, I still have the same issue:  This is on the current main branch, which has the `bac1921` commit.

sczi commented 2026年01月15日 22:45:51 +01:00

Can you check what is the value of default-directory in that session buffer? Maybe it is still ~/... and I missed somewhere I need to call expand-file-name. Though also if the session buffer was created before that latest commit, it would still have been created with ~, if it has ~ is it an old buffer or is it still created with ~ in default-directory after restarting emacs? Also I assume you already checked but in the TUI it is working, you don't have the same issue?

Can you check what is the value of `default-directory` in that session buffer? Maybe it is still `~/...` and I missed somewhere I need to call `expand-file-name`. Though also if the session buffer was created before that latest commit, it would still have been created with `~`, if it has `~` is it an old buffer or is it still created with `~` in `default-directory` after restarting emacs? Also I assume you already checked but in the TUI it is working, you don't have the same issue?

sczi commented 2026年01月16日 03:39:57 +01:00

in 337d54e I added a variable opencode-show-tool-output you can set to t to display the output of bash commands, maybe that will help to get the exact error message to debug it. It's not meant to be a permanent feature, eventually I'd like to make the tool outputs collapsed by default but you can click to show the full output. for now though opencode-show-tool-output can help with debugging

in 337d54e I added a variable `opencode-show-tool-output` you can set to t to display the output of bash commands, maybe that will help to get the exact error message to debug it. It's not meant to be a permanent feature, eventually I'd like to make the tool outputs collapsed by default but you can click to show the full output. for now though `opencode-show-tool-output` can help with debugging

fast-90 commented 2026年01月16日 11:01:50 +01:00

This works now after I pulled the main branch this morning, thanks!

This works now after I pulled the main branch this morning, thanks!