You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
arena: same-uid candidates can read other runs' scratch #209
From PR #201 verification: arena's text can delete a finished run's directory and candidate worktrees, but a run cut off before the delete (recorded Claude headless turn end and Grok 2400 s cap, evals/promises/results/2026-10-08-sync-df58112.md:143,145) leaves its folder, and concurrent runs share a uid. Text cannot isolate same-uid candidates; this needs a sandbox per candidate (or per run) from the harness. Track here; revisit with #204.
Accepted follow-up disposition: defer enforced candidate isolation as a new architecture proposal. Fresh run directories and completed-run cleanup are already instructed, but they do not provide concurrent same-user secrecy. This issue stays open for discussion of the isolation boundary and portability/maintenance costs; no sandbox implementation is being added.
Activity
fix(arena): name where outputs go and clean up candidate worktrees
fix(arena): name where outputs go and clean up candidate worktrees
fix(arena): name where outputs go and clean up candidate worktrees
mdsmithaustin commentedon Oct 16, 2026
Accepted follow-up disposition: defer enforced candidate isolation as a new architecture proposal. Fresh run directories and completed-run cleanup are already instructed, but they do not provide concurrent same-user secrecy. This issue stays open for discussion of the isolation boundary and portability/maintenance costs; no sandbox implementation is being added.