The agent then tries to execute a
shell command named proto
and exits without processing my request.
Additional details
I’ve also tested this on Windows 11 using WSL2
with Ubuntu 24.04.3 LTS,
and I encounter exactly the same behavior there — so it doesn’t
seem to be specific to my Linux installation.
Environment
Pinegrow Web Editor: 8.5
(Linux, x86_64)
OpenAI Codex CLI: v0.47.0
Codex path: /home/antonio/.npm-global/bin/codex
Provider settings:
Codex CLI command: codex
Extra args: --full-auto --sandbox workspace-write --skip-git-repo-check -c approval_policy="never"
Web search: enabled
Network access: enabled
Question
Is there anything special to
consider when using Pinegrow
with Codex CLI on Linux or WSL?
Or could this be a bug in how the Agent chat input is forwarded to
the Codex CLI?
I’ve read your thread and tried to piece together what might be happening, though to be honest, it’s a bit of coffee-grounds reading, since I don’t have your exact setup to test these hypotheses.
Here are a few things you could check:
Pinegrow version : Codex CLI support was introduced officially in Pinegrow 8.6. If you’re still on 8.5, that alone could explain the issue. Try updating first.
CLI test outside Pinegrow. In a terminal, run codex --version or just codex to confirm it works and returns a prompt. Also check the exact path with which codex.
PATH & permissions : Make sure Pinegrow can see the CLI binary. Launch Pinegrow from a terminal so it inherits your PATH (~/.npm-global/bin etc.).
Try minimal arguments. In the AI Assistant settings, remove all extra args (e.g. --full-auto …) and test with just codex. If that works, add flags one by one to find which one breaks.
“proto” command issue. The Codex CLI documentation doesn’t mention any “proto” command, I can’t find it. That may be a mismatch between the CLI version and what Pinegrow expects. Capturing the exact command Pinegrow runs (from its console) could help narrow it down.
Environment sanity check. If you’re running under WSL2 or a non-glibc distro, maybe try on a standard Ubuntu setup, just to rule out environment quirks.
If nothing helps, I’d suggest posting the full command Pinegrow is trying to execute, plus your versions of Pinegrow, Codex CLI, and Linux. That info will make it much easier for others (and maybe the devs) to reproduce.
From what I see, the issue isn’t with your setup or Linux Mint at all. Pinegrow is launching Codex correctly, but it’s using the command:
/home/antonio/.npm-global/bin/codex proto ...
That proto part is the key. It’s an internal “protocol” mode that expects to run in a proper interactive terminal (TTY). Since Pinegrow executes it in a non-interactive shell, Codex immediately throws the “stdout is not a terminal” error, at least it’s my interpretation for this issue.
So your CLI install works fine, it’s Pinegrow’s integration that’s failing to talk to it.
A few things you could try while waiting for a fix:
Stay on version 8.5, since 8.6 currently doesn’t start for you anyway.
In the Codex settings, try adding --no-color --tty=false to Extra arguments (it sometimes helps suppress the TTY check).
If you’re curious, copy the full command from the error box and run it manually in your terminal, you’ll see exactly what Codex is expecting.
If that doesn’t change anything, I’d say it’s worth reporting as a bug in Pinegrow 8.6’s Codex integration, the rest of your setup looks perfectly fine to me.
