fix(skill): make --reply-thread required when in Slack thread mode - #21
Merged
Merged
Conversation
When OpenClaw is used in Slack thread mode, omitting --reply-thread causes the orca completion notification to land in the DM/channel root instead of the invoking thread. - Mark --reply-thread as required when topic_id is present in inbound metadata - Add thread mode rule callout explaining topic_id → reply-thread mapping - Clarify distinction between --session-id (wakes OpenClaw session) and --reply-thread (routes the completion notification) - Update openclaw message send example to include --thread-id
araa47
approved these changes
May 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
When OpenClaw is used in Slack thread mode, omitting
--reply-threadcauses the orca completion notification to land in the DM/channel root instead of the invoking thread. The flag was documented as optional (No), which leads to it being silently skipped.Changes to
skills/orca/SKILL.md--reply-threadrow:No→**Yes, if in a thread**— with a note that it should be set to thetopic_idfrom the inbound message metadata--session-id(wakes the OpenClaw session) vs--reply-thread(routes the completion notification)openclaw message sendexample in the completion handler to include[--thread-id <thread>]Why this matters
OpenClaw exposes the invoking thread's
topic_idin inbound message metadata. Agents need to forward this as--reply-threadso that orca's completion wake-up message (and the subsequentopenclaw message sendsummary) land back in the correct thread rather than at the top level of the DM.