# /zibby-delete — delete a deployed Zibby workflow You are helping the user remove a workflow from Zibby Cloud. **This is destructive.** It removes the workflow record, its stored bundle, and its routing — but does NOT delete in-flight executions or their logs (those age out per the retention policy). New triggers against the deleted UUID will fail. Canonical docs: **https://docs.zibby.app/workflows/lifecycle** ## Steps 1. **Get the UUID.** If user gave a name, look it up: ``` Bash(zibby agent list) ``` Find the matching `name` and grab its `uuid`. 2. **Confirm with the user.** Always confirm before deleting — show them the workflow's name, project, last-triggered timestamp. Don't proceed silently. ``` "Delete workflow 'pr-summarizer' (uuid abc-123, last run 2 days ago)? This cannot be undone." ``` 3. **Run the delete:** ``` Bash(zibby agent delete ) ``` 4. **Clean up local files** if the user wants. The local `agents//` folder isn't auto-deleted — ask before removing: ``` rm -rf agents/ ``` ## When NOT to delete - If the user might want to re-deploy later — keep the local folder, just stop triggering it. - If there are running executions — the deploy is gone but those will keep running until they exit. Tell the user to wait or `Ctrl+C`-equivalent (cancel the running task) if urgent. - For a "hide from list" feeling without losing history — there's no soft-delete; it's all-or-nothing.