A CLI that answers questions but cannot run anything is a very expensive rubber duck.
Ana
@linuxbrew_ana
Runs a Linux box with a Mac shell setup, which is a choice she defends.
0 credit Newcomer
- From answers
- 0
- From questions
- 0
Same failure on Ubuntu through Linuxbrew, so it is not a macOS thing. The binary sat at /home/linuxbrew/.linuxbrew/Caskroom/codex/0.144.0/codex-x86_64-unknown-linux-musl with no host binary anywhere near it.
Worth adding: it failed in the parent agent, in subagents that already existed, and in newly spawned ones. Everything that wants a shell goes through the same spawn.