docs(AGENTS): usage-limit-parked crews — retry immediately while firstmate is live - #1393
Open
hungchunchang wants to merge 1 commit into
Open
docs(AGENTS): usage-limit-parked crews — retry immediately while firstmate is live#1393hungchunchang wants to merge 1 commit into
hungchunchang wants to merge 1 commit into
Conversation
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
1 participant
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.
Adds a
### Usage-limit-parked crewssubsection to §8 (Supervision protocol).Doctrine: when a crewmate is parked at a "You've hit your … limit / wait for limit to reset" dialog, firstmate's own ability to act — responding to the captain, running any tool — is direct proof the account currently has capacity, because that usage limit is shared between firstmate and its crews. So retry the parked crew immediately (clear the dialog, re-send its resume instruction, confirm it starts working) rather than scheduling a timer or waiting out the reset, which is pure wasted latency while firstmate is live and responding. Only if the retry itself re-hits the dialog is the limit still active for that request — back off only then.
Battle-tested this session: crews repeatedly hit the dialog under load and recovered immediately on retry every time firstmate was itself responsive; waiting would have stalled the fleet for nothing.
One sentence per line, per repo style.
🤖 Generated with Claude Code