# AI Assistant Codex on Linux **URL:** \ **Category:** General\ **Created:** [October 28, 2025, 9:52am UTC](https://forum.pinegrow.com/t/ai-assistant-codex-on-linux/11183 "2025-10-28T09:52:05Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![NoProblemForMe](https://avatars.discourse-cdn.com/v4/letter/n/3d9bf3/32.png) [@NoProblemForMe](https://forum.pinegrow.com/u/NoProblemForMe)\ **Post date:** [October 28, 2025, 9:52am UTC](https://forum.pinegrow.com/t/ai-assistant-codex-on-linux/11183/1 "2025-10-28T09:52:05Z")
Hi, I did not receive any response from the pinegrow support, so I try it here. I managed to get a success message when pressing the **“Test setup”** button — so the Codex CLI connection seems to work. ![image](https://canada1.discourse-cdn.com/flex036/uploads/pinegrow/original/2X/8/8b1a5c256aa0cde6aabb01f23f22b2f2767da8be.png) However, as soon as I send an actual message in the Agent Chat, I get an error in the **AI Terminal**. Specifically, Pinegrow appears to pass the literal word **“proto”** to Codex instead of my real message. ### What I see The Terminal panel shows: ```auto ``` ![image](https://canada1.discourse-cdn.com/flex036/uploads/pinegrow/original/2X/e/e1f9554563d2462f040fdf988f727fd16a53abd2.png) 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: ### 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? ``` Thanks in advance. ---
**Author:** ![Blep](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/blep/32/6497_2.png) [@Blep](https://forum.pinegrow.com/u/Blep)\ **Post date:** [October 28, 2025, 10:37am UTC](https://forum.pinegrow.com/t/ai-assistant-codex-on-linux/11183/2 "2025-10-28T10:37:42Z")
Hi @NoProblemForMe 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: 1. 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. 2. 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. 3. PATH & permissions : Make sure Pinegrow can see the CLI binary. Launch Pinegrow from a terminal so it inherits your PATH (~/.npm-global/bin etc.). 4. 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. 5. “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. 6. 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. Hope that helps 🤞 🧲 🍀 ---
**Author:** ![NoProblemForMe](https://avatars.discourse-cdn.com/v4/letter/n/3d9bf3/32.png) [@NoProblemForMe](https://forum.pinegrow.com/u/NoProblemForMe)\ **Post date:** [October 29, 2025, 8:43am UTC](https://forum.pinegrow.com/t/ai-assistant-codex-on-linux/11183/3 "2025-10-29T08:43:04Z")
Hi @Blep, 1. Version 8.6 no longer starts. A window opens briefly, but then closes again. I can open version 8.5 without any problems. 2. I tested it. CLI runs outside of Pinegrow. I also determined the path using which and entered it in Pinegrow. 3. Started ./PinegrowLibrary from the terminal: ![grafik](https://canada1.discourse-cdn.com/flex036/uploads/pinegrow/original/2X/0/0bd23065cf163aa91cb1439f3e5e9c618ebb2d7f.png) 4. see screenshot 5. Where do I see the full command Pinegrow is trying to execute? 6. I’m on a Linux Mint with Ubuntu 24.04.3 (Noble Numbat) ![grafik](https://canada1.discourse-cdn.com/flex036/uploads/pinegrow/original/2X/b/b2722bc2277ef823a8b974306118b996d9437f7d.png) ---
**Author:** ![Blep](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/blep/32/6497_2.png) [@Blep](https://forum.pinegrow.com/u/Blep)\ **Post date:** [October 29, 2025, 9:00am UTC](https://forum.pinegrow.com/t/ai-assistant-codex-on-linux/11183/4 "2025-10-29T09:00:15Z")
Thanks for the extra details and screenshots. 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: ```auto /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: 1. Stay on version 8.5, since 8.6 currently doesn’t start for you anyway. 2. In the Codex settings, try adding --no-color --tty=false to Extra arguments (it sometimes helps suppress the TTY check). 3. 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. Hope that helps 🤞🍀🎱 * * * ---
**Author:** ![NoProblemForMe](https://avatars.discourse-cdn.com/v4/letter/n/3d9bf3/32.png) [@NoProblemForMe](https://forum.pinegrow.com/u/NoProblemForMe)\ **Post date:** [October 29, 2025, 10:31am UTC](https://forum.pinegrow.com/t/ai-assistant-codex-on-linux/11183/5 "2025-10-29T10:31:27Z")
@Blep thank you for your help! 🙏 ---
**Author:** ![matjaz](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/matjaz/32/5_2.png) [@matjaz](https://forum.pinegrow.com/u/matjaz)\ **Post date:** [October 30, 2025, 9:41am UTC](https://forum.pinegrow.com/t/ai-assistant-codex-on-linux/11183/6 "2025-10-30T09:41:09Z")
Codex recently removed the `proto` mode used by Pinegrow to communicate with it. Pinegrow 8.6 solves this by using the new `exec` json mode (although proto was much more interactive and exposed). 8.6 should also run ok on Linux now (you will need to download and install the Linux package again). ---
**Author:** ![NoProblemForMe](https://avatars.discourse-cdn.com/v4/letter/n/3d9bf3/32.png) [@NoProblemForMe](https://forum.pinegrow.com/u/NoProblemForMe)\ **Post date:** [October 30, 2025, 5:00pm UTC](https://forum.pinegrow.com/t/ai-assistant-codex-on-linux/11183/7 "2025-10-30T17:00:48Z")
It’s working now. Thank you @matjaz and @Blep !