“Both sessions execute the same step. The losing session does not detect that it lost the claim — it had already started before the winning session's claim was persisted.”

— rileywhite, on GitHub · Issue #1052

Quote · github.com

From “bug: pool work-claim race: concurrent sessions execute the same bead”, found 2026-10-14.

Take

An atomic claim isn't enough on its own. A worker must check that it won before it starts. Closed in June 2026.

Tools it’s about