OpenClaw merged a Slack delivery fix in PR #128341, keeping private argument-menu replies inside the original thread when Slack does not provide an action responder.
The bug affected a specific but visible workflow. A Slack user could click a native argument-menu button in a message thread. If Slack's normal response URL path was unavailable, OpenClaw fell back to Slack's Web API for a private ephemeral response. That fallback could lose the parent thread timestamp and place the response at the top level of the channel instead.
For busy Slack workspaces, that is more than a cosmetic annoyance. Thread locality is part of how command errors, menu choices, and multi-part replies stay understandable. A private fallback that jumps out of the thread can make it look like the agent responded in the wrong place or detached the action from its context.
What Changed
The Slack action owner now preserves the authoritative parent-thread timestamp from the action container or message before calling Slack's native ephemeral-message API.
The PR keeps the change deliberately small:
- response-URL delivery remains unchanged when Slack provides it;
- top-level replies still behave as top-level replies;
- authorization and workspace validation do not change;
- generic slash-command fallback behavior remains intact;
- unthreaded actions are still handled normally.
The private action type was also narrowed to Slack's upstream Block Kit action contract, reducing local ambiguity around the action shape.
Why It Matters
Slack integrations have a hard job: they need to behave like native Slack participants, not just send messages somewhere. Preserving thread context is a big part of that feeling.
PR #128341 improves the failure and fallback path rather than the ideal path. That is where integration quality usually shows. When Slack omits an action responder, users still get private argument-menu errors and successful multi-part command replies in the place where they clicked.
For OpenClaw operators, this means fewer confusing top-level channel replies and less manual reconstruction of which menu action produced which response.
Validation
The PR reports pre-fix regressions showing real registered Slack argument-menu delivery missing thread_ts for both container-provided and message-provided parent timestamps. The existing top-level case already passed and remains covered.
After the fix, 201 owner and sibling tests passed across native slash commands, block interactions, reply delivery, and action threading. The coverage includes container-over-message precedence, message-only parent context, absent top-level context, invalid buttons, six successful threaded Web API responses, response-URL limits, workspace validation, and existing authorization behavior.
The changed surface is tiny: three production lines plus 36 test lines, with Slack package-boundary generation, typed owner lint, formatting, max-lines, assertion-safety, conflict-marker checks, and a full-branch code review reported clean.
Bottom Line
OpenClaw's Slack menu fallback now keeps private replies in the same thread as the original action. That makes Slack command workflows easier to follow when the platform forces OpenClaw onto the Web API fallback path.