fix(prompts): break rate-limit recovery feedback loop - #20
Merged
Conversation
When a worker hits a rate limit, the daemon escalates to the
orchestrator (e.g. OpenClaw). OpenClaw then sends a recovery message
like "The rate limit has cleared" into the worker's pane. On the next
poll cycle the daemon re-captures the pane, sees "rate limit" in the
recovery text, and escalates again — creating an infinite loop every
60s (ESCALATION_COOLDOWN).
Skip rate_limit complex-blocker matches when recovery language
("cleared", "resolved", "lifted") is also present in the pane output.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
🧪 Coverage Report
📄 Coverage by file
|
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
rate_limitcomplex-blocker matches when recovery language ("cleared", "resolved", "lifted") is also present in the pane output.Test plan
rate_limit_cleared_is_not_blocker,rate_limit_resolved_is_not_blockerdetects_rate_limittest still passes (real rate limits still detected)cargo fmt --check,cargo clippy -- -D warnings,cargo testall pass🤖 Generated with Claude Code