Repository navigation
docs: autonomous orchestrators p3a — shift-brief usage caps - #524
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <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.
Phase 3a of the autonomous-orchestrators epic, tracked on PyAutoLabs/PyAutoBrain#555. Read with PyAutoLabs/PyAutoBrain/pull/556; merge this one first.
What changes
batches/AGENTS.md— the brief's optional usage capsmax-workers:(default 2) andmax-sessions:(default 6): what the watcher does at a cap, and that a non-number refuses the brief.batches/examples/shift_brief_example.mdcarries both caps (stillbrief --checkOK).Tier: judge — merge mode: human
/prm. Heart YELLOW reason set acknowledged by the human at ship.Witness
🤖 Generated with Claude Code