From aa4ec8c7795deee1d09ddd6e2bfa7b858395cdb6 Mon Sep 17 00:00:00 2001 From: Timmy Date: Thu, 26 Mar 2026 11:09:25 +0000 Subject: [PATCH] storkit: create 401_bug_whatsapp_and_slack_missing_start_command_handler --- ...01_bug_whatsapp_and_slack_missing_start_command_handler.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/.storkit/work/1_backlog/401_bug_whatsapp_and_slack_missing_start_command_handler.md b/.storkit/work/1_backlog/401_bug_whatsapp_and_slack_missing_start_command_handler.md index 8984dd75..2c6c2d69 100644 --- a/.storkit/work/1_backlog/401_bug_whatsapp_and_slack_missing_start_command_handler.md +++ b/.storkit/work/1_backlog/401_bug_whatsapp_and_slack_missing_start_command_handler.md @@ -8,6 +8,10 @@ name: "WhatsApp and Slack missing start command handler" The start 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 start handler in the same way. + ## How to Reproduce 1. Configure bot with transport = "whatsapp" or "slack"\n2. Send "start " to the bot\n3. Check server logs