[Fix] Discord follow-ups show raw prompt wrappers in the task transcript#561
Merged
mrubens merged 1 commit intoJul 18, 2026
Merged
Conversation
Contributor
Author
mrubens
marked this pull request as ready for review
July 18, 2026 19:46
mrubens
requested review from
brunobergher,
daniel-lxs and
mrubens
as code owners
July 18, 2026 19:46
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.
Related issue
Internal follow-up from Discord/transcript display.
Why this PR exists
What changed
Discord follow-up prompts include structural wrappers (
replying_to,discord_turn_policy,thread_context,communication_message). The task transcript was showing that raw markup instead of only the user's words.normalizeTranscriptUserTextnow strips those Slack-parity prefixes the same way it already handles barecommunication_messageand Slack turns, so the UI shows just the user message body.How it was tested
packages/types/src/__tests__/acp.test.tsfor Discord prefixes (with and withoutthread_context), policy-only prefixes, and HTML-escaped wrapperspnpm --filter @roomote/types exec vitest run src/__tests__/acp.test.ts(77 tests passed)Checklist
[Fix],[Feat],[Improve],[Refactor],[Docs], or[Chore]followed by a user-facing descriptionpnpm lintandpnpm check-typespass locallypnpm changeset