ShellError: Failed with exit code 128 #1469

Closed
opened 2026-02-16 17:31:07 -05:00 by yindo · 7 comments
Owner

Originally created by @lukaszciastko on GitHub (Aug 24, 2025).

Originally assigned to: @thdxr on GitHub.

Out of the sudden, the agent no longer works. Some massages get replies in the AI but I am getting the following error all the time:

ShellError: Failed with exit code 128

I am getting this error both in Ghostty and in the macOS Terminal - with every model I tried - either Sonic, OpenAI, Claude, or OpenRouter.

Originally created by @lukaszciastko on GitHub (Aug 24, 2025). Originally assigned to: @thdxr on GitHub. Out of the sudden, the agent no longer works. Some massages get replies in the AI but I am getting the following error all the time: ``` ShellError: Failed with exit code 128 ``` I am getting this error both in Ghostty and in the macOS Terminal - with every model I tried - either Sonic, OpenAI, Claude, or OpenRouter.
yindo closed this issue 2026-02-16 17:31:07 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Aug 24, 2025):

This issue might be a duplicate of existing issues. Please check:

  • #1521: Reports the exact same "ShellError: Failed with exit code 128" error when using filesystem access/tool use with multiple models on Ubuntu (though this was closed)
  • #1501: Also reported "ShellError: Failed with exit code" (exit code 1 instead of 128) with bash tool issues
  • #1058: Reports sudden stopping of opencode responses after updates, though with different symptoms

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Aug 24, 2025): This issue might be a duplicate of existing issues. Please check: - #1521: Reports the exact same "ShellError: Failed with exit code 128" error when using filesystem access/tool use with multiple models on Ubuntu (though this was closed) - #1501: Also reported "ShellError: Failed with exit code" (exit code 1 instead of 128) with bash tool issues - #1058: Reports sudden stopping of opencode responses after updates, though with different symptoms Feel free to ignore if none of these address your specific case.
Author
Owner

@rekram1-node commented on GitHub (Aug 24, 2025):

what files is it failing on? @lukaszciastko

@rekram1-node commented on GitHub (Aug 24, 2025): what files is it failing on? @lukaszciastko
Author
Owner

@PilotDevo commented on GitHub (Sep 2, 2025):

0.6.2 some repos fails.... logs:
ERROR 2025-09-02T15:57:11 +1ms service=tui message=ShellError: Failed with exit code 128 name=UnknownError Server error
not sure why there is a server error on every model...
I'm guessing it has to do with perms on this dir.
going to fix that and report back.
Good luck!

@PilotDevo commented on GitHub (Sep 2, 2025): 0.6.2 some repos fails.... logs: ERROR 2025-09-02T15:57:11 +1ms service=tui message=ShellError: Failed with exit code 128 name=UnknownError Server error not sure why there is a server error on every model... I'm guessing it has to do with perms on this dir. going to fix that and report back. Good luck!
Author
Owner

@rekram1-node commented on GitHub (Sep 2, 2025):

@PilotDevo what type files are you working w/

@rekram1-node commented on GitHub (Sep 2, 2025): @PilotDevo what type files are you working w/
Author
Owner

@PilotDevo commented on GitHub (Sep 2, 2025):

@PilotDevo what type files are you working w/

Im working with py and ts files mostly however the git repository in the backend subdirectory had a corrupted index,
which I've repaired by removing the corrupted index file and restoring the working directory from the HEAD commit. it was causing a hang up in the processing of the files... functionality fully restored across all models.

@PilotDevo commented on GitHub (Sep 2, 2025): > [@PilotDevo](https://github.com/PilotDevo) what type files are you working w/ Im working with py and ts files mostly however the git repository in the backend subdirectory had a corrupted index, which I've repaired by removing the corrupted index file and restoring the working directory from the HEAD commit. it was causing a hang up in the processing of the files... functionality fully restored across all models.
Author
Owner

@PilotDevo commented on GitHub (Sep 2, 2025):

a quick run of
git fsck
will return a check of corruptions.
Hope it helps!

@PilotDevo commented on GitHub (Sep 2, 2025): a quick run of `git fsck` will return a check of corruptions. Hope it helps!
Author
Owner

@rekram1-node commented on GitHub (Dec 27, 2025):

[automated] Closing due to 90+ days of inactivity. Feel free to reopen if you still need this!

@rekram1-node commented on GitHub (Dec 27, 2025): [automated] Closing due to 90+ days of inactivity. Feel free to reopen if you still need this!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#1469