Rockachopa/Timmy-time-dashboard
1
0
Fork 2
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

[Bug] claude-loop.sh Workspace Collision Fix: Use UUIDs for Concurrent Worktree Checkouts #1427

New Issue
Closed
opened 2026-03-24 13:04:45 +00:00 by Timmy · 2 comments
Timmy commented 2026-03-24 13:04:45 +00:00
Owner
Copy Link

Context: Using claude-w${worker_id}-${issue_num} risks collisions under high throughput limits or ID mismatches.

Acceptance Criteria:

  • Leverage /usr/bin/uuidgen for completely detached and safe worktree naming.
  • Ensure cleanup tracks the UUIDs distinctly.
**Context:** Using `claude-w${worker_id}-${issue_num}` risks collisions under high throughput limits or ID mismatches. **Acceptance Criteria:** - Leverage `/usr/bin/uuidgen` for completely detached and safe worktree naming. - Ensure cleanup tracks the UUIDs distinctly.
hermes was assigned by Timmy 2026-03-24 13:26:54 +00:00
Timmy commented 2026-03-24 14:08:47 +00:00
Author
Owner
Copy Link

Investigation Results:

After examining the repository, the claude-loop.sh script referenced in this issue does not currently exist in the canonical repository. This suggests either:

  1. The script exists in a different location/branch
  2. The script needs to be created as part of fixing this issue
  3. The issue refers to a pattern that should be implemented in an existing script

Delegation to Kimi:
Since this requires locating or creating the claude-loop.sh script with proper UUID-based worktree naming, I'm delegating this to Kimi.

Implementation Requirements:

  • Use /usr/bin/uuidgen for worktree naming instead of claude-w${worker_id}-${issue_num}
  • Ensure cleanup tracks UUIDs properly
  • Look for existing loop scripts or create claude-loop.sh if needed
  • Test with concurrent worktree operations to verify collision prevention

Files to investigate:

  • Check if claude-loop.sh exists in other branches/locations
  • Review scripts/agent_workspace.sh for similar patterns
  • Look at kimi-loop.sh or other agent loops for reference patterns
**Investigation Results:** After examining the repository, the `claude-loop.sh` script referenced in this issue does not currently exist in the canonical repository. This suggests either: 1. The script exists in a different location/branch 2. The script needs to be created as part of fixing this issue 3. The issue refers to a pattern that should be implemented in an existing script **Delegation to Kimi:** Since this requires locating or creating the claude-loop.sh script with proper UUID-based worktree naming, I'm delegating this to Kimi. **Implementation Requirements:** - Use `/usr/bin/uuidgen` for worktree naming instead of `claude-w${worker_id}-${issue_num}` - Ensure cleanup tracks UUIDs properly - Look for existing loop scripts or create claude-loop.sh if needed - Test with concurrent worktree operations to verify collision prevention **Files to investigate:** - Check if claude-loop.sh exists in other branches/locations - Review `scripts/agent_workspace.sh` for similar patterns - Look at kimi-loop.sh or other agent loops for reference patterns
hermes was unassigned by Timmy 2026-03-24 14:08:47 +00:00
kimi was assigned by Timmy 2026-03-24 14:08:47 +00:00
Timmy commented 2026-03-24 18:25:46 +00:00
Author
Owner
Copy Link

Fixed in ~/.hermes/bin/claude-loop.sh.

Change: Replaced claude-w${worker_id}-${issue_num} worktree naming with UUID-based naming: claude-${issue_num}-${UUID}.

This prevents workspace collisions when workers are recycled or multiple workers pick up issues from different repos with the same issue number. Uses /usr/bin/uuidgen with Python uuid.uuid4() fallback.

Note: This file is infra (not tracked in the dashboard repo), so no PR needed — applied directly.

Fixed in `~/.hermes/bin/claude-loop.sh`. **Change:** Replaced `claude-w${worker_id}-${issue_num}` worktree naming with UUID-based naming: `claude-${issue_num}-${UUID}`. This prevents workspace collisions when workers are recycled or multiple workers pick up issues from different repos with the same issue number. Uses `/usr/bin/uuidgen` with Python `uuid.uuid4()` fallback. Note: This file is infra (not tracked in the dashboard repo), so no PR needed — applied directly.
Timmy closed this issue 2026-03-24 18:25:47 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
Workshop: Timmy as Presence (Epic #222)
 actionable
Has a concrete code/config task extracted
 assigned-claude
Issue currently assigned to Claude agent — do not assign to another agent
 assigned-gemini
Issue currently assigned to Gemini agent — do not assign to another agent
 assigned-groq
assigned-kimi
Issue currently assigned to Kimi agent — do not assign to another agent
 assigned-manus
Issue currently assigned to Manus agent — do not assign to another agent
 claude-ready
consolidation
Part of a consolidation epic
 deprioritized
Keep open but not blocking P0 work
 deprioritized
Keep open but not blocking P0 work
 duplicate
Duplicate of another issue
 gemini-review
Auto-generated by Gemini, needs relevance review
 groq-ready
harness
Core product: agent framework, heartbeat, inference, memory
 heartbeat
Harness: Agent heartbeat loop
 inference
Harness: Inference and model routing
 infrastructure
Supporting stage: dashboard, CI/CD, deployment, DNS
 kimi-ready
Scoped and ready for Kimi to pick up
 memory-session
Harness: Memory and session crystallization
 morrowind
Harness: Morrowind embodiment
 needs-design
Needs architectural design before implementation
 needs-extraction
Philosophy with unextracted engineering work
 p0-critical
Priority 0: Must fix now
 p1-important
Priority 1: Important, next sprint
 p2-backlog
Priority 2: Backlog, do when time permits
 philosophy
Philosophical foundation — informs architecture decisions
 rejected-direction
Closed: rejected or superseded direction
 seed:know-purpose
Three Seeds: KNOW YOUR PURPOSE
 seed:serve-real
Three Seeds: SERVE THE REAL
 seed:tell-truth
Three Seeds: TELL THE TRUTH
 sovereignty
Harness: Sovereignty stack
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok kimi manus perplexity Rockachopa
No Assignees kimi
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#1427
Delete Branch "%!s()"

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?