You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
acpx: apply_patch stuck in pending state after long conversations #22222
When using opencode via acpx in non-interactive (background) mode, after a session accumulates significant context (multiple rounds of continuation), apply_patch gets stuck in "pending" state indefinitely. The agent continues thinking and reading files but never actually writes anything.
Environment
opencode-ai: 1.4.3
acpx: 0.5.3
OS: Linux (container)
Model: gptloadopenai/glm (via ccload provider)
Mode: acpx non-interactive with --approve-all
Steps to Reproduce
Create an acpx session: acpx --approve-all opencode -s mysession "task"
Let the agent work for multiple rounds, accumulating context
Continue the session with acpx --approve-all opencode -s mysession "continue"
After 3-5 continuations, apply_patch starts showing "pending" but never completes
Agent keeps thinking and reading but never writes files
Expected Behavior
apply_patch should complete and write files regardless of session length.
Actual Behavior
apply_patch stays pending forever. Only workaround is to kill the session and create a new one.
These issues share the same core symptom (apply_patch/write operation hanging). If your issue is specifically triggered by long session context length (3-5 continuations) in acpx non-interactive mode, that may be a distinct reproduction path worth keeping open - but please confirm whether the workarounds from the above issues apply to your case.
Activity
github-actions commentedon Apr 13, 2026
This issue might be a duplicate of existing issues. Please check:
These issues share the same core symptom (apply_patch/write operation hanging). If your issue is specifically triggered by long session context length (3-5 continuations) in acpx non-interactive mode, that may be a distinct reproduction path worth keeping open - but please confirm whether the workarounds from the above issues apply to your case.
oldjs commentedon Apr 13, 2026
22222
github-actions commentedon Jul 3, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.