CLI process exited (signal SIGTERM)

General
1

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 :slight_smile:

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

2

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.