Key loop-claude's session per slot, so two loops of one project run side by side #552
Reference in New Issue
Block a user
Delete Branch "item-372"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Each loop holds the lowest free slot of its project, a file locked under ~/.local/state/loop-claude//, and names its worker's session after it; slot 0 keeps today's name, so open chunks still resume. A reload hands the slot on, its lock kept across the exec. The archive and the route already follow the session's transcript. A commit in the config's folder now commits only its own file, and git's index.lock serializes two at once. Files item 386: project-record's copies are still shared per project.