From 0c94b425674fe3d81f3f80bfd71c946832b09b87 Mon Sep 17 00:00:00 2001 From: Bartek Lipinski Date: Tue, 7 Apr 2026 11:29:44 +0200 Subject: [PATCH] Use --force in /mob-remove slash command for non-current mobs The slash command was calling `codemob remove ` which triggers an interactive y/N confirmation prompt that agents can't handle cleanly. Now the slash command gets confirmation from the user first, warns about destructive consequences (unstaged/uncommitted/unpushed changes), then calls `codemob remove --force ` to skip the redundant CLI prompt. Closes #32 --- internal/mob/init.go | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/internal/mob/init.go b/internal/mob/init.go index dff155b..f0886ef 100644 --- a/internal/mob/init.go +++ b/internal/mob/init.go @@ -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 `" + ` 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 ''. 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 `" + ` using the Bash tool. If they choose the CURRENT mob (marked with ◀):