Skip to content

fix: use fallback text instead of retry for empty GeneratingRunResult#574

Merged
FL4TLiN3 merged 1 commit intomainfrom
fix/empty-run-result-fallback
Feb 18, 2026
Merged

fix: use fallback text instead of retry for empty GeneratingRunResult#574
FL4TLiN3 merged 1 commit intomainfrom
fix/empty-run-result-fallback

Conversation

@FL4TLiN3
Copy link
Contributor

Summary

  • Replace retry approach (fix: retry when LLM generates empty text in GeneratingRunResult #572) with a simple fallback in GeneratingRunResult
  • When LLM generates no visible text (e.g., only reasoning/thinking with extended thinking), fall back to "OK" since the task is already complete (attemptCompletion succeeded, no remaining todos)
  • Avoids expensive extra LLM calls and retry events that break assertNoRetry in E2E delegation chain tests

Test plan

  • Updated test: falls back to 'OK' when LLM generates empty text
  • All 1098 unit tests pass
  • Typecheck passes

🤖 Generated with Claude Code

Replace the retry approach with a simple fallback. When the LLM
generates no visible text in GeneratingRunResult (e.g., only
reasoning/thinking with extended thinking), fall back to "OK" since
the task is already complete (attemptCompletion succeeded). This avoids
expensive extra LLM calls and retry events that break assertNoRetry
in E2E delegation chain tests.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@FL4TLiN3 FL4TLiN3 merged commit 38bd6cf into main Feb 18, 2026
11 checks passed
@FL4TLiN3 FL4TLiN3 deleted the fix/empty-run-result-fallback branch February 25, 2026 13:35
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