claude-code - 💡(How to fix) Fix /ultrareview: counter decremented despite crashed run with no findings [1 comments, 2 participants]

{"error":"Review crashed before producing findings. See session logs for details."}

• Output: error JSON above, no findings, no partial results
• Surface the crash reason to the user (the current error message points at "session logs" the user cannot access).

TL;DR

The most likely fix is to refund the free-run counter when the remote agent crashes before producing findings, and consider implementing an upper bound on scope size to prevent similar crashes.

Guidance

• Verify the scope size and complexity of the review by checking the number of files changed and lines inserted/deleted, as reported by the CLI.
• Test smaller scope sizes (e.g., HEAD~30) to see if the review completes successfully and does not decrement the free-run counter.
• If possible, investigate the session logs (although currently inaccessible to the user) to determine the root cause of the crash.
• Consider reporting the issue to the development team to implement a refund mechanism for crashed reviews and improve error handling.

Example

No code snippet is provided as the issue is related to the behavior of the /ultrareview command and the remote agent.

Notes

The suggested fix and workaround are based on the information provided in the issue and may not be comprehensive. The development team's input is necessary to implement a permanent solution.

Recommendation

Apply workaround: use smaller scope sizes (e.g., HEAD~30) to avoid crashes and prevent decrementing the free-run counter until a permanent fix is implemented. This approach allows users to continue using the /ultrareview command while minimizing the impact of the issue.