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

[Phase 4] Add --timeout flag to cmd_destroy #247

New Issue
Open
opened 2026-04-08 06:34:36 +02:00 by shoko · 0 comments
shoko commented 2026-04-08 06:34:36 +02:00
Owner
Copy Link

Problem

Timeout handling for sessions is currently done inside the queue-daemon. We need a CLI way to destroy timed-out sessions.

Solution

Add --timeout flag to kugetsu destroy:

  • kugetsu destroy --timeout --force - destroy ALL currently timed-out sessions
  • No issue_ref required when using --timeout

Implementation:

  1. Create internal _get_timeout_tasks() function
  2. When --timeout is set, find all queue items with state==notified where notified_at + TASK_TIMEOUT_HOURS < now
  3. For each timed-out item:
    • Kill pid if exists
    • Stop opencode session if exists
    • Remove worktree
    • Delete session file
    • Update queue item to "error"
  4. --force skips confirmation (always yes for automated --timeout)

Status

BLOCKED - Depends on Phase 1 (help restructure needed to document --timeout flag)

Files

  • skills/kugetsu/scripts/kugetsu-session.sh

Related Issues

Parent: #235
Blocked by: #236 (Phase 1)

## Problem Timeout handling for sessions is currently done inside the queue-daemon. We need a CLI way to destroy timed-out sessions. ## Solution Add --timeout flag to `kugetsu destroy`: - `kugetsu destroy --timeout --force` - destroy ALL currently timed-out sessions - No issue_ref required when using --timeout Implementation: 1. Create internal _get_timeout_tasks() function 2. When --timeout is set, find all queue items with state==notified where notified_at + TASK_TIMEOUT_HOURS < now 3. For each timed-out item: - Kill pid if exists - Stop opencode session if exists - Remove worktree - Delete session file - Update queue item to "error" 4. --force skips confirmation (always yes for automated --timeout) ## Status **BLOCKED** - Depends on Phase 1 (help restructure needed to document --timeout flag) ## Files - skills/kugetsu/scripts/kugetsu-session.sh ## Related Issues Parent: #235 Blocked by: #236 (Phase 1)
shoko added the blocked label 2026-04-08 06:38:29 +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 blocked
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#247
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?