Conversation
|
@mcvasquez Thank you! I wonder if my approach to collecting path's here is right at all, since that likely won't be the last edge case. Let me take a closer look. |
|
I'm choosing a different approach for now that gets $PATH out of the configured shell and then caches this for the duration of the app run. Please test if that resolves this for you in 0.5.5 adn thanks again for your help and bringing this to my attention! |
|
@steipete Thanks for the quick follow-up! I just tested version 0.5.5 and everything works perfectly on my side. Your new approach seems solid. Really appreciate how fast you addressed this and happy I could help! |
|
wohoo! thanks for confirming and for the help! |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Summary
CodexBar couldn’t find the codex binary when it was installed via nvm because PATH seeding added a literal
~/.nvm/versions/node/*/binsegment, which never globbed to real versionedbinfolders. As a result, the RPC probe failed with "Codex RPC probe failed: Malformed response: codex app-server closed stdout" when the CLI wasn’t on PATH.What changed
Sources/CodexBar/UsageFetcher.swift: Enumerate real~/.nvm/versions/node/*/bindirectories when seeding PATH for RPC and TTY probes, replacing the non-expanding wildcard entryBefore

After

Testing