Skip to content

Keep only active VS Code worktrees during cleanup + bump v5.0.6#74

Merged
NagyVikt merged 1 commit intomainfrom
agent/gx/zeus-edixai-com-vscode-active-cleanup-v506
Apr 13, 2026
Merged

Keep only active VS Code worktrees during cleanup + bump v5.0.6#74
NagyVikt merged 1 commit intomainfrom
agent/gx/zeus-edixai-com-vscode-active-cleanup-v506

Conversation

@NagyVikt
Copy link
Copy Markdown
Collaborator

Summary\n- prune clean agent worktrees during cleanup so VS Code Source Control shows local branch plus active changed worktrees\n- keep unmerged branch refs while dropping clean worktree mounts\n- bump package version to 5.0.6 and add release notes\n\n## Verification\n- npm test\n- node --check bin/multiagent-safety.js\n- npm pack --dry-run

… cleanup

Users were seeing many stale sandbox branches in Source Control after work finished. Cleanup now forwards an active-only prune mode so clean agent worktrees are removed while dirty worktrees stay visible, and unmerged branch refs are preserved for safety.\n\nConstraint: Preserve unmerged branch refs while hiding stale clean worktrees from VS Code\nRejected: Delete all clean agent branches during cleanup | would risk dropping unmerged branch pointers\nConfidence: high\nScope-risk: moderate\nReversibility: clean\nDirective: Use --keep-clean-worktrees when operators intentionally need every clean worktree to stay mounted\nTested: npm test; node --check bin/multiagent-safety.js; npm pack --dry-run\nNot-tested: Live VS Code panel behavior against existing user workspace settings
@NagyVikt NagyVikt merged commit bb6950c into main Apr 13, 2026
12 checks passed
@NagyVikt NagyVikt deleted the agent/gx/zeus-edixai-com-vscode-active-cleanup-v506 branch April 13, 2026 19:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant