Skip to content

Fix tri-* CLI fallbacks: capture stderr instead of swallowing - #23

Merged
5uck1ess merged 1 commit into
mainfrom
fix/tri-review-reliability
Apr 5, 2026
Merged

Fix tri-* CLI fallbacks: capture stderr instead of swallowing#23
5uck1ess merged 1 commit into
mainfrom
fix/tri-review-reliability

Conversation

@5uck1ess

@5uck1ess 5uck1ess commented Apr 5, 2026

Copy link
Copy Markdown
Owner

Summary

Change 2>/dev/null to 2>&1 in all 5 tri-* commands for Codex and Gemini CLI fallbacks. Add post-dispatch empty-output validation to tri-review.

Problem

This session, both Codex (empty output) and Gemini (keychain error) produced zero-byte output files because stderr was discarded. The consolidation step silently dropped both agents with no explanation.

Fix

  • 2>&1 captures errors in the output file instead of discarding them
  • Post-dispatch validation checks for empty files and warns
  • Applied to: tri-review, tri-dispatch, tri-debug, tri-security, tri-test-gen

Test plan

  • CI passes (docs-only change)
  • Next tri-review invocation with a failing CLI shows the error instead of silent empty output

Change 2>/dev/null to 2>&1 across all 5 tri-* commands (review, dispatch,
debug, security, test-gen) for both Codex and Gemini CLI fallbacks.

This session both Codex and Gemini produced empty output because errors
were silently discarded. With 2>&1, errors appear in the output file
where the consolidation step can report them.

Also added post-dispatch validation to tri-review: check for empty output
files and warn instead of silently dropping agents.
@5uck1ess
5uck1ess merged commit 856ae7e into main Apr 5, 2026
2 checks passed
@5uck1ess
5uck1ess deleted the fix/tri-review-reliability branch April 5, 2026 23:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant