Skip to content

fix: pass state file path instead of inlining content to avoid Linux E2BIG #4258

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
marcusquinn merged 1 commit into from
Mar 12, 2026
Merged

fix: pass state file path instead of inlining content to avoid Linux E2BIG #4258

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 8 additions & 6 deletions .agents/scripts/pulse-wrapper.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1291,16 +1291,18 @@ run_pulse() {
start_epoch=$(date +%s)
echo "[pulse-wrapper] Starting pulse at $(date -u +%Y-%m-%dT%H:%M:%SZ)" >>"$WRAPPER_LOGFILE"

# Build the prompt: /pulse + pre-fetched state
# Build the prompt: /pulse + reference to pre-fetched state file.
# The state is NOT inlined into the prompt — on Linux, execve() enforces
# MAX_ARG_STRLEN (128KB per argument) and the state routinely exceeds this,
# causing "Argument list too long" on every pulse invocation. The agent
# reads the file via its Read tool instead. See: #4257
local prompt="/pulse"
if [[ -f "$STATE_FILE" ]]; then
local state_content
state_content=$(cat "$STATE_FILE")
prompt="/pulse

--- PRE-FETCHED STATE (from pulse-wrapper.sh) ---
${state_content}
--- END PRE-FETCHED STATE ---"
Pre-fetched state file: ${STATE_FILE}
Read this file before proceeding — it contains the current repo/PR/issue state
gathered by pulse-wrapper.sh BEFORE this session started."
fi

# Run the provider-aware headless wrapper in background.
Expand Down
Loading