Per-repo allow_concurrent override for same-repo multi-agent work #883

Closed
opened 2026-10-27 13:38:08 +00:00 by sam · 0 comments
Owner

Concurrent agents on the same repo are blocked by default (worktree conflict). PRD sec.9 open question 5 proposes a per-repo config override (allow_concurrent = true) for repos where parallel work is safe (different base branches, different packages). Deferred to Phase 2 in the PRD; depends on the daemon supporting concurrent task dispatch at all.

Acceptance Criteria

Repos with allow_concurrent = true in repos config can have multiple agents working simultaneously without worktree collisions; repos without it keep current serialized behavior.


Imported from beads archie-core-1786637499018-350-0fc03bf9 · GitHub #371 · type feature · priority P2 · created 2026-08-08 · closed 2026-08-08

Concurrent agents on the same repo are blocked by default (worktree conflict). PRD sec.9 open question 5 proposes a per-repo config override (allow_concurrent = true) for repos where parallel work is safe (different base branches, different packages). Deferred to Phase 2 in the PRD; depends on the daemon supporting concurrent task dispatch at all. ### Acceptance Criteria Repos with allow_concurrent = true in [[repos]] config can have multiple agents working simultaneously without worktree collisions; repos without it keep current serialized behavior. --- _Imported from beads `archie-core-1786637499018-350-0fc03bf9` · GitHub #371 · type feature · priority P2 · created 2026-08-08 · closed 2026-08-08_
sam added the mediumfeature labels 2026-10-27 13:38:08 +00:00
sam self-assigned this 2026-10-27 13:38:08 +00:00
sam closed this issue 2026-10-27 13:38:08 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#883