# CLI process exited (signal SIGTERM)

**URL:** <https://forum.pinegrow.com/t/cli-process-exited-signal-sigterm/11487>\
**Category:** Bug Reports\
**Created:** [March 25, 2026, 1:02pm UTC](https://forum.pinegrow.com/t/cli-process-exited-signal-sigterm/11487 "2026-03-25T13:02:59Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![red-rosefields](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/red-rosefields/32/5392_2.png) [@red-rosefields](https://forum.pinegrow.com/u/red-rosefields)\
**Post date:** [March 25, 2026, 1:02pm UTC](https://forum.pinegrow.com/t/cli-process-exited-signal-sigterm/11487/1 "2026-03-25T13:02:59Z")

</div>

I am working with Pg and **Anthropic Claude Code CLI.**  
When working with slightly longer prompts I am always getting a:  
`CLI process exited (signal SIGTERM)`  
`Command: /Users/carlosxxx/.local/bin/claude -p "Use the piped content as the full user prompt." --max-turns 20 --dangerously-skip-permissions --output-format stream-json --verbose --input-format text --append-system-prompt "You are Mr. Pine Cone, an elite full-stack web developer and visionary UI/UX designer embedded in the Pinegrow Web Editor. `

Asking Claude it says it may be due to 🙂

SIGTERM means the Claude CLI process was **terminated** — something killed it before it could finish. Here are the most likely causes:

**1. Timeout** Pinegrow’s integration probably has a maximum wait time for Claude to respond. If the process takes too long (e.g., a complex prompt, slow API response), it sends SIGTERM to kill it. This is the most common cause.

**2. Memory/Resource limits** The system or Pinegrow killed the process because it consumed too many resources.

**3. Pinegrow plugin killed it intentionally** The plugin may have a “cancel” or restart mechanism that fires prematurely — especially if a previous process was still running when a new prompt was triggered.

**4. macOS killing the process** On Mac, the OS can send SIGTERM to background processes under memory pressure.

Any ideas?  
Thanks

---

<div class="post-metadata">

**Author:** ![PeteSharp](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/petesharp/32/7134_2.png) [@PeteSharp](https://forum.pinegrow.com/u/PeteSharp)\
**Post date:** [March 26, 2026, 7:53pm UTC](https://forum.pinegrow.com/t/cli-process-exited-signal-sigterm/11487/2 "2026-03-26T19:53:26Z")

</div>

Have you tried running the same prompt directly in Terminal with Claude CLI? That should help determine whether it’s the CLI itself or Pinegrow’s integration causing the issue.

---

<div class="post-metadata">

**Author:** ![red-rosefields](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/red-rosefields/32/5392_2.png) [@red-rosefields](https://forum.pinegrow.com/u/red-rosefields)\
**Post date:** [March 27, 2026, 1:13pm UTC](https://forum.pinegrow.com/t/cli-process-exited-signal-sigterm/11487/3 "2026-03-27T13:13:31Z")

</div>

No error whatsoever by running the command directly on the Terminal.  
I made several tests. If I try a long prompt in Pinegrow, the systematically I get the CLI process exited (signal Sigterm)

Any idea? Anyone?  
Thanks