From f5024b2648b1e51b619071801d6fa4a991d0706a Mon Sep 17 00:00:00 2001 From: dave Date: Wed, 25 Mar 2026 15:34:54 +0000 Subject: [PATCH] storkit: done 394_story_whatsapp_and_slack_permission_prompt_forwarding --- ..._and_slack_permission_prompt_forwarding.md | 23 +++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 .storkit/work/5_done/394_story_whatsapp_and_slack_permission_prompt_forwarding.md diff --git a/.storkit/work/5_done/394_story_whatsapp_and_slack_permission_prompt_forwarding.md b/.storkit/work/5_done/394_story_whatsapp_and_slack_permission_prompt_forwarding.md new file mode 100644 index 00000000..7fac8bd7 --- /dev/null +++ b/.storkit/work/5_done/394_story_whatsapp_and_slack_permission_prompt_forwarding.md @@ -0,0 +1,23 @@ +--- +name: "WhatsApp and Slack permission prompt forwarding" +--- + +# Story 394: WhatsApp and Slack permission prompt forwarding + +## User Story + +As a WhatsApp or Slack user, I want permission requests from Claude Code to be forwarded to my chat so I can approve or deny them, rather than having them silently fail. + +## Acceptance Criteria + +- [ ] Permission requests are sent as messages to the WhatsApp sender with tool name and input details +- [ ] User can reply yes/y/approve or no/n/deny to approve or deny the permission +- [ ] Permission requests time out and auto-deny (fail-closed) if not answered within the configured timeout +- [ ] Slack receives the same permission forwarding treatment +- [ ] Reuses the existing permission channel infrastructure (perm_rx, PermissionForward, PermissionDecision) +- [ ] Matrix permission handling is completely unaffected +- [ ] handle_llm_message uses a tokio::select! loop (like Matrix bot.rs) to listen for both LLM output and permission requests concurrently + +## Out of Scope + +- TBD