From 61d63db84ce295cdf7141d1b08bbb37b8ebe6ac6 Mon Sep 17 00:00:00 2001 From: Timmy Date: Thu, 26 Mar 2026 11:09:27 +0000 Subject: [PATCH] storkit: create 403_bug_whatsapp_and_slack_missing_rmtree_command_handler --- ...3_bug_whatsapp_and_slack_missing_rmtree_command_handler.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/.storkit/work/1_backlog/403_bug_whatsapp_and_slack_missing_rmtree_command_handler.md b/.storkit/work/1_backlog/403_bug_whatsapp_and_slack_missing_rmtree_command_handler.md index 5a8e262a..ea9b845c 100644 --- a/.storkit/work/1_backlog/403_bug_whatsapp_and_slack_missing_rmtree_command_handler.md +++ b/.storkit/work/1_backlog/403_bug_whatsapp_and_slack_missing_rmtree_command_handler.md @@ -8,6 +8,10 @@ name: "WhatsApp and Slack missing rmtree command handler" The rmtree command has a fallback handler in chat/commands/mod.rs that returns None. Only Matrix has pre-dispatch handling for this command. On WhatsApp and Slack, the command falls through to the LLM path. +## Implementation Note + +Follow the existing code patterns used by commands that already work on WhatsApp and Slack (e.g. "rebuild", "status"). Study how those commands are dispatched and handled, and implement the rmtree handler in the same way. + ## How to Reproduce 1. Configure bot with transport = "whatsapp" or "slack"\n2. Send "rmtree " to the bot\n3. Check server logs