Bug: Claudia's Terminal Environment Fails to Find Commands in User PATH - macOS

[ragusa-it]

The integrated terminal within the Claudia application (v1.0.41) is unable to find and execute command-line tools that are available in my standard user shell environment. This results in command not found errors when the AI attempts to run common development tools like pnpm.

This issue appears to be specific to the Claudia wrapper, as Claude Code can successfully execute these commands when used by itself (open claude in Terminal while in project directory). The problem suggests that Claudia's shell session is not correctly inheriting the PATH variable from my user shell configuration (e.g., .zshrc or .bash_profile).

Steps to Reproduce

Open a project in the Claudia desktop application.

Start a new code session.

Ask the AI to perform a task that requires a command-line tool installed in a non-standard path (e.g., via Homebrew or a node version manager). For example, "Use pnpm to add the node-cron dependency."

Observe the terminal output.

Expected Behavior

Claudia's terminal should access the same PATH environment variable as my native terminal. It should successfully find and execute the pnpm command, and any other command-line tools I have installed.

Actual Behavior

The command fails with a command not found error. The AI attempts to run the command, but the shell session within Claudia cannot locate the pnpm executable.

As seen in the screenshot below, the initial command failed, and a follow-up diagnostic command (which pnpm) also failed to find the executable.

Screenshot

Environment

Application: Claudia Code v1.0.41

Operating System: macOS 26.0 Beta (25A5306g) - Tahoe

Shell: zsh

[ragusa-it]

I feel stupid - it just by default picked the wrong claude code installation, apparently I had more than one somehow.

[WeZZard]

I also came to this issue. I just copied the claude as a claude-code in the enclosing folder of $(which claude) and the things get to work.

[davidmoshal]

I have this issue, it does run claude, but cannot find pnpm, npm, yarn, etc, so presumably it's not running the zsh shell which sets the path.

this doesn't work for me (and why would claude-code make any difference?):

I also came to this issue. I just copied the claude as a claude-code in the enclosing folder of $(which claude) and the things get to work.

if I ask for the PATH in a session, I get:

echo $PATH
/usr/bin:/bin:/usr/sbin:/sbin

So it's definitely not working.

I feel this could be an important project, but right now I do question whether it's ready for prime time

[davidmoshal]

OK so I solved it, in the same way that @ragusa-it did, by selecting my system claude code, not the bundled one.

However, it really should be better documented, because it's not obvious that the default is a bundled version of claude code (and btw, why would you bundle claude code?).

So in my mind this is documentation bug.

[dlpuzhangyue]

OK so I solved it, in the same way that @ragusa-it did, by selecting my system claude code, not the bundled one.我用同样的方法解决了这个问题，我选择了我的系统代码，而不是捆绑的代码。

However, it really should be better documented, because it's not obvious that the default is a bundled version of claude code (and btw, why would you bundle claude code?).然而，它确实应该有更好的文档，因为默认是claude代码的捆绑版本并不明显（顺便说一句，为什么要捆绑claude代码？）

So in my mind this is documentation bug.在我看来，这是文档错误。

So my friend. How did you solve it finally? I encountered the same problem