shoko/kugetsu
1
0
Fork 0
Code Issues 17 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

Bug - delegate command causes file conflict with multiple tasks #126

New Issue
Closed
opened 2026-04-03 13:40:04 +02:00 by shoko · 0 comments
shoko commented 2026-04-03 13:40:04 +02:00
Owner
Copy Link

Bug Description

delegate command doesn't properly isolate tasks to their respective worktrees, causing file conflicts when multiple tasks exist.

Details

  • start creates the correct worktree for a new task
  • continue works correctly with multiple worktrees
  • delegate reuses an existing worktree instead of switching to the per-issue worktree
  • Result: File conflicts when delegating multiple tasks to different issues

Expected behavior

  • kugetsu delegate "work on #14" should use the worktree for issue #14
  • kugetsu delegate "work on #15" should use the worktree for issue #15
  • Each task should have isolated worktree

Root Cause (Research Needed)

  • Does delegate properly resolve issue ref to worktree?
  • Is the worktree path passed correctly to the forked session?
  • Is there a race condition between delegate and start?

Fix Approach

  1. Research how delegate currently resolves worktree for a task
  2. Compare with how start/continue successfully isolate worktrees
  3. Apply same worktree resolution logic to delegate
  4. Test with multiple concurrent tasks

Acceptance Criteria

  • delegate "work on #14" uses worktree for issue #14
  • delegate "work on #15" uses worktree for issue #15
  • No file conflicts when delegating multiple tasks
  • Existing single-task delegate behavior unchanged
## Bug Description `delegate` command doesn't properly isolate tasks to their respective worktrees, causing file conflicts when multiple tasks exist. ## Details - `start` creates the correct worktree for a new task - `continue` works correctly with multiple worktrees - `delegate` reuses an existing worktree instead of switching to the per-issue worktree - Result: File conflicts when delegating multiple tasks to different issues ## Expected behavior - `kugetsu delegate "work on #14"` should use the worktree for issue #14 - `kugetsu delegate "work on #15"` should use the worktree for issue #15 - Each task should have isolated worktree ## Root Cause (Research Needed) - Does delegate properly resolve issue ref to worktree? - Is the worktree path passed correctly to the forked session? - Is there a race condition between delegate and start? ## Fix Approach 1. Research how delegate currently resolves worktree for a task 2. Compare with how start/continue successfully isolate worktrees 3. Apply same worktree resolution logic to delegate 4. Test with multiple concurrent tasks ## Acceptance Criteria - [ ] `delegate "work on #14"` uses worktree for issue #14 - [ ] `delegate "work on #15"` uses worktree for issue #15 - [ ] No file conflicts when delegating multiple tasks - [ ] Existing single-task delegate behavior unchanged
shoko closed this issue 2026-04-05 09:06:03 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
0.2.x-only
Available only in 0.2.x, not backportable
 0.3.x-only
Available only in 0.3.x, not backportable
 backport
Backport compatible - can merge to 0.1.x
 blocked
Issue needs clarification/discussion before it can be worked on
 bug
Bug report
 critical
Critical - blocking parallel work
 feature
New feature
 foundation
Foundation work for 0.2.x
 high
High priority - workflow improvements
 meta
Meta issue tracking multiple issues
 need-review
PR needs review before merge
 parallelization
Issues related to parallelization
 ready
Issue is clear and ready to be implemented/delegated
 ready-to-merge
PR approved and ready to merge
 task-delegation
Issues related to task-delegation
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
shoko
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: shoko/kugetsu#126
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?