Skip to content

Use --force in /mob-remove for non-current mobs #33

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
blipinsk merged 1 commit into from
Apr 7, 2026
+8 −1
Merged

Use --force in /mob-remove for non-current mobs #33

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion internal/mob/init.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -94,7 +94,14 @@ Once the user confirms which agent they want, run ` + "`codemob queue change-age

Ask the user which mob they want to remove.

If they choose a DIFFERENT mob (not the one marked with ◀), run ` + "`codemob remove <name>`" + ` directly. No session confirmation needed since the current session stays alive.
If they choose a DIFFERENT mob (not the one marked with ◀):

This is a destructive operation. Before proceeding, warn the user:
"This will permanently delete mob '<name>'. Any unstaged, uncommitted, or unpushed changes in that workspace will be permanently lost. Are you sure?"

Only proceed after the user confirms. If they decline, cancel the operation.

Once confirmed, run ` + "`codemob remove --force <name>`" + ` using the Bash tool.

If they choose the CURRENT mob (marked with ◀):

Expand Down
Loading