feat(agents): add max_agents_per_repo to allow multiple agents per repo#44
Open
PieterPel wants to merge 1 commit into
Open
feat(agents): add max_agents_per_repo to allow multiple agents per repo#44PieterPel wants to merge 1 commit into
PieterPel wants to merge 1 commit into
Conversation
Adds `agents.max_agents_per_repo` (default: 1, backward-compatible) so operators using git worktrees can run multiple agents on the same repo concurrently without hitting the hardcoded single-agent-per-project block. - Add `max_agents_per_repo: usize` to `AgentsConfig` (serde default = 1) - Add `State::project_agent_count()` to count running agents per project - Refactor `is_project_busy()` to delegate to `project_agent_count()` - Update `try_launch` and `auto_launch` to check count against config limit - Add tests for count behaviour, default value, and busy-state consistency
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.
Closes #43
Summary
agents.max_agents_per_repoconfig field (default:1, fully backward-compatible)State::project_agent_count()to count running agents per projectis_project_busy()to delegate toproject_agent_count()try_launchandauto_launchto enforce the configurable limitN/MAX agents activeper repoWhy
When
git.use_worktrees = true, each ticket gets an isolated worktree so there's no conflict between concurrent agents on the same repo. The previous hard booleanis_project_busy()made the 1-per-repo limit impossible to lift even when worktrees made it safe to do so.Usage
Test plan
cargo checkpassesproject_agent_count,max_agents_per_repodefault, andis_project_busyconsistency