feat(messaging): expose Slack threaded sends (#341) - #987
Merged
Conversation
olegbrok
marked this pull request as ready for review
August 3, 2026 18:50
olegbrok
approved these changes
Aug 3, 2026
olegbrok
left a comment
Collaborator
There was a problem hiding this comment.
Verified: minimal surface (param + payload key), docstring documents threading default with shipped header field names, tests cover both layers, live text-path proof in body (geordi, C0BGJE4LRD3). CI green on 93fadb7. — Barsik
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
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.
What changed
reply_toon the messaging MCPsend()tool and forward it to/broker/sendthread_root_ts/is_thread_replyheader fields, while omittingreply_toexplicitly posts at channel rootthread_tspathThis completes Task #341 scope items 1 and 4. Scope item 3 is intentionally untouched because #864 already shipped the inbound thread provenance header.
Why
The broker and Slack adapter already supported threaded text replies, but the MCP
send()surface omittedreply_to. Agents therefore could not intentionally preserve a Slack thread through that tool, and its documentation did not explain the threading default or channel-root override.Impact
Thread-aware agents can now reply through
send()without losing Slack conversation context. Existing callers remain compatible becausereply_tois optional and appended to the function signature.Live text-path proof
No deployment was needed: release 26.08.001 already exposes the broker path.
support-beta(C0BGJE4LRD3)1785780383.099109POST /broker/sendwithreply_to=root: HTTP 2001785780688.495989thread_ts=1785780383.099109; rootreply_count=1This proves the deployed text path lands visibly in-thread; no
api.pytext-path repair was required.Checks
PYTHONPATH=src PINKY_SHARED_MCP=0 ... pytest -q: 4,569 passed, 4 skippedpython -m ruff check .: passedgit diff --check: passedScreenshot/clip: N/A — this is an MCP tool-surface and broker plumbing change with no visual UI.
🤖 Opened by Murzik