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

[CI/CD] Automate Cleanup of Stale Agent Worktrees via Cron #1410

New Issue
Closed
opened 2026-03-24 13:04:22 +00:00 by Timmy · 1 comment
Timmy commented 2026-03-24 13:04:22 +00:00
Owner
Copy Link

Context: timmy-loop.sh generates worktrees iteratively. A fatal unhandled exit leaves detached git folders on the host.

Acceptance Criteria:

  • Develop an automated script inside cron/ to sweep ~/worktrees for folders un-modified in the last 12 hours.
  • The script MUST trigger git worktree remove --force and prune references cleanly.
**Context:** `timmy-loop.sh` generates worktrees iteratively. A fatal unhandled exit leaves detached git folders on the host. **Acceptance Criteria:** - Develop an automated script inside `cron/` to sweep `~/worktrees` for folders un-modified in the last 12 hours. - The script MUST trigger `git worktree remove --force` and prune references cleanly.
Timmy commented 2026-03-24 13:11:38 +00:00
Author
Owner
Copy Link

Implementation Plan

Automate cleanup of stale agent worktrees via cron to prevent disk space issues.

Files to Create:

  1. scripts/cleanup-worktrees.sh - Main cleanup script
  2. scripts/install-cron.sh - Cron installation helper
  3. src/infrastructure/maintenance/ - Cleanup monitoring module

Implementation Steps:

  1. Identify Stale Worktrees: Check ~/worktrees/ for old directories
  2. Safety Checks: Verify no active processes using worktree
  3. Age-Based Cleanup: Remove worktrees older than 24 hours
  4. Size-Based Cleanup: Remove if disk usage > threshold
  5. Preserve Active Work: Skip worktrees with recent git activity
  6. Add Monitoring: Log cleanup actions and disk savings

Cleanup Logic:

# Find stale worktrees (>24h old, no recent git activity)
find ~/worktrees/ -type d -name 'kimi-*' -mtime +1 -exec test ! -f {}/fresh.lock \; -print

Safety Features:

  • Lock files prevent cleanup of active worktrees
  • Dry-run mode for testing
  • Size limits to prevent accidental cleanup
  • Backup of important data before deletion

Acceptance Criteria:

  • Cron job runs daily at 2 AM
  • Safely identifies and removes stale worktrees
  • Preserves worktrees with active git locks
  • Logs all cleanup actions with disk space saved
  • Configurable retention period (default 24h)
  • Emergency stop mechanism

Installation:

# Install via script
./scripts/install-cron.sh
# Or manually:  
crontab -e  # Add: 0 2 * * * ~/scripts/cleanup-worktrees.sh
## Implementation Plan Automate cleanup of stale agent worktrees via cron to prevent disk space issues. ### Files to Create: 1. `scripts/cleanup-worktrees.sh` - Main cleanup script 2. `scripts/install-cron.sh` - Cron installation helper 3. `src/infrastructure/maintenance/` - Cleanup monitoring module ### Implementation Steps: 1. **Identify Stale Worktrees**: Check `~/worktrees/` for old directories 2. **Safety Checks**: Verify no active processes using worktree 3. **Age-Based Cleanup**: Remove worktrees older than 24 hours 4. **Size-Based Cleanup**: Remove if disk usage > threshold 5. **Preserve Active Work**: Skip worktrees with recent git activity 6. **Add Monitoring**: Log cleanup actions and disk savings ### Cleanup Logic: ```bash # Find stale worktrees (>24h old, no recent git activity) find ~/worktrees/ -type d -name 'kimi-*' -mtime +1 -exec test ! -f {}/fresh.lock \; -print ``` ### Safety Features: - Lock files prevent cleanup of active worktrees - Dry-run mode for testing - Size limits to prevent accidental cleanup - Backup of important data before deletion ### Acceptance Criteria: - [ ] Cron job runs daily at 2 AM - [ ] Safely identifies and removes stale worktrees - [ ] Preserves worktrees with active git locks - [ ] Logs all cleanup actions with disk space saved - [ ] Configurable retention period (default 24h) - [ ] Emergency stop mechanism ### Installation: ```bash # Install via script ./scripts/install-cron.sh # Or manually: crontab -e # Add: 0 2 * * * ~/scripts/cleanup-worktrees.sh ```
kimi was assigned by Timmy 2026-03-24 13:11:39 +00:00
kimi was unassigned by Timmy 2026-03-24 19:32:22 +00:00
Timmy closed this issue 2026-03-24 21:54:11 +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
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#1410
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?