Issues

go-broker install never pre-trusts Claude Code's global worktree root, so a fresh Session hits an interactive 'trust this folder' dialog under automated production

bug

#698

· pmark opened

on Sep 26, 2026

Automated launch path refuses forever on a different-Action resumable candidate, unlike arcadia go which clears it once the worktree is gone

bug

#697

· pmark opened

on Sep 26, 2026

Automated production tick never recovers from a dead-but-claimed worktree; spins in a tight retry loop instead of resuming

bug

#695

· pmark opened

on Sep 26, 2026

Cross-Project dependency resolution, ambiguous-id refusal, cross-Plan cycle detection at parse time, and tick-based escalation for a long-unresolved dependency.

#694

· pmark opened

on Sep 26, 2026

Soak ready-set admission with the fixture provider across several repositories at a raised concurrency limit, proving every limit engages and every invariant holds before any live concurrent proof.

#693

· pmark opened

on Sep 26, 2026

Admission stops starting new work in a repository once its count of unmerged candidates reaches the operator-configured review limit.

#692

· pmark opened

on Sep 26, 2026

A Session that stays stalled past a bounded window is ended, preserved and reconciled so its repository lease and host slot are freed, with repeated stalls escalated to the operator.

#691

· pmark opened

on Sep 26, 2026

Cap concurrent Sessions per provider account in the same admission transaction as the host slot, so concurrency never oversubscribes one account.

#690

· pmark opened

on Sep 26, 2026

An Action claim does not expire while its candidate is still unmerged, so neither arcadia go nor production can dispatch the same Action a second time.

#689

· pmark opened

on Sep 26, 2026

Measure the workspace database under concurrent writers so the concurrency limit rests on a tested number, not an assertion.

#688

· pmark opened

on Sep 26, 2026

Add a deterministic fixture coding-agent provider that sleeps, edits one file and exits, so concurrency limits can be exercised end to end at zero token cost.

#687

· pmark opened

on Sep 26, 2026

Every launch failure after an admission is issued releases that admission at once, so a failed launch never holds a concurrency slot until its receipt expires.

#686

· pmark opened

on Sep 26, 2026

Navigation Menu

All issues

go-broker install never pre-trusts Claude Code's global worktree root, so a fresh Session hits an interactive 'trust this folder' dialog under automated production

Automated launch path refuses forever on a different-Action resumable candidate, unlike arcadia go which clears it once the worktree is gone

Automated production tick never recovers from a dead-but-claimed worktree; spins in a tight retry loop instead of resuming

Cross-Project dependency resolution, ambiguous-id refusal, cross-Plan cycle detection at parse time, and tick-based escalation for a long-unresolved dependency.

Soak ready-set admission with the fixture provider across several repositories at a raised concurrency limit, proving every limit engages and every invariant holds before any live concurrent proof.

Admission stops starting new work in a repository once its count of unmerged candidates reaches the operator-configured review limit.

A Session that stays stalled past a bounded window is ended, preserved and reconciled so its repository lease and host slot are freed, with repeated stalls escalated to the operator.

Cap concurrent Sessions per provider account in the same admission transaction as the host slot, so concurrency never oversubscribes one account.

An Action claim does not expire while its candidate is still unmerged, so neither arcadia go nor production can dispatch the same Action a second time.

Measure the workspace database under concurrent writers so the concurrency limit rests on a tested number, not an assertion.

Add a deterministic fixture coding-agent provider that sleeps, edits one file and exits, so concurrency limits can be exercised end to end at zero token cost.

Every launch failure after an admission is issued releases that admission at once, so a failed launch never holds a concurrency slot until its receipt expires.

Search results