Fix agent replies targeting thread root instead of mention post #5
+13
−11
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.
The agent was replying to the root post of conversation threads instead of the specific post where it was mentioned, breaking conversation threading.
Changes
GrokService.analyzeAndDecide(): AddedmentionPostIdparameter to accept the ID of the post containing the mentiongrok.ts: Changed fromthread.root_post.idtomentionPostIdwhen callingparseGrokResponse()mentionPostIdfor both reply and analyze actionsagent.tsandexamples.tsto passmention.post.idas third argumentExample
The
action.target_post_idnow correctly references the mention post, ensuringxClient.postReply()creates proper reply chains.💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.