Render clickable web links across conversation messages - #671
Merged
Merged
Conversation
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
1 participant
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.
Bare GitHub URLs in agent completion messages remained plain text, and chat skipped Markdown rendering for URL-only messages. The shared Markdown utility now linkifies HTTP(S) text after safe rendering, excludes existing anchors and code, and keeps trailing sentence punctuation outside destinations. Named conversation participants use the same Markdown path as user turns. Labelled query strings are escaped once and inline code stays literal.
Validation: 292 chat tests; 16 Markdown/image tests; 14 Markdown/Messages/cartouche tests (overlapping Markdown suite); static lint and diff checks passed. The actual templates and Messages/chat modules passed isolated Playwright fixture checks at 1440px and 360px, including initial/history renders, exact reported GitHub destinations, unsafe schemes, code, participant layout and overflow. Browser evidence is retained in the task worktree at
.run/conversation-links-evidence/. Fixture APIs use in-memory state; this does not claim authenticated or public-server acceptance.Merge decision: ready on Tier 1 evidence. No deployment requested; no service, migration, database or configuration changes.
Native task: #V#task_agent_1ba75a21225543a88529cf1ef50ecee0