Skip to main content
← Back to list
01Issue
BugShippedSwamp ClubPublicTeam
Assigneeskeeb

Relationships

#1139 Lab: URLs inside list items aren't clickable (linkified) in rendered issue bodies/summaries

Opened by magistr · 7/14/2026· Shipped 8/14/2026

Description

In the Lab web UI (swamp-club.com/lab), a bare URL rendered inside a list item is shown as plain, non-clickable text — even though the same URL in a normal paragraph is linkified and clickable. So the markdown renderer's autolinking is inconsistent: it fires in paragraphs but not inside bulleted / numbered lists. To follow a URL that happens to sit in a list you have to select-copy-paste it into the address bar.

This is visible both in the issue detail view and in the summary text shown in the Lab issue list.

Prior art — the project has already fixed this class of "text that should be a link isn't" piecemeal:

  • #1053 "Make PR links in Labs details clickable" (feature, shipped)
  • #659 "Can't click on repository from swamp extension search" (bug, shipped)

URLs inside list items in issue bodies/summaries are still not linkified.

Steps to reproduce

Create/view an issue whose body contains a bare URL in a paragraph and the same URL as a list item, e.g.:

Here is a link in prose: https://example.com/foo

- Here is a link in a list: https://example.com/bar
- Second item: https://example.com/baz

Open the rendered issue (or its summary in the list view) on swamp-club.com/lab.

Expected

Both the paragraph URL and the list-item URLs auto-linkify into clickable anchors (and [text](url) markdown links inside list items likewise render as anchors), consistent with how paragraph URLs already render — and with the clickable treatment #1053 gave PR links.

Actual

The paragraph URL is clickable; the URLs inside the list items are plain, non-clickable text.

Environment

  • Surface: swamp-club.com Lab web UI — issue detail view and issue-list summary text
  • Scope: bare URLs (and markdown links) that appear inside bulleted/numbered list items
02Bog Flow
✓OPEN✓TRIAGED✓IN PROGRESS✓SHIPPED+ 1 MOREASSIGNED+ 5 MOREREVIEW+ 3 MOREPR_MERGED+ 1 MORECONTRIBUTOR_NOTIFIED

Shipped

8/14/2026, 7:44:52 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
keeb assigned keeb8/14/2026, 6:16:28 PM
Editable. Press Enter to edit.

keeb commented 8/14/2026, 7:45:39 PM

Shipped in PR #1077 — with a correction to the diagnosis, so this doesn't read as a silent scope change.

The bug as filed does not reproduce. Bare URLs inside list items DO linkify in Lab issue bodies and comments today. Driving the real render pipeline over eleven list shapes — tight, loose, nested, ordered, wrapped continuation, list-after-paragraph, task list, trailing punctuation, angle autolink, bare www, markdown link — autolinks every one. A scan of 111 live issues (#1050-#1160) found five carrying a bare URL on a raw list line and zero genuine misses: the four that look broken are URLs inside backticks, which correctly stay code examples rather than becoming links.

The second surface you named is also gone. Since #922 (2026-07-03, eleven days before you filed) the Lab issue list is body-free and shows only titles, so there is no summary text there to linkify.

But you were seeing something real, on a surface with different rules. Lab renders text two ways: issue bodies and comments are markdown (autolinked, sanitised), while lifecycle entries — the plan steps, potential challenges, reasoning and resolution notes that agents post — are structured data rendered as plain text with no markdown pass at all. Those render as bulleted and numbered lists in the issue detail view, and every URL in them was unclickable. Your exact words, wrong mechanism.

That is what this PR fixes: URLs in lifecycle payload text are now links. The markdown behaviour you compared against is pinned by a regression test so it cannot quietly become broken later — asserted in both directions, since a URL inside backticks must keep NOT linking or every command example in the Lab turns into a link.

The two-surfaces distinction is now written into the repo's guide, because you won't be the last person to attribute this to the markdown renderer. Thanks for the report and for the prior art you dug up with it.

keeb commented 8/14/2026, 7:46:07 PM

Thanks @magistr for reporting this! The fix has been merged and a release is on its way. We appreciate your contribution to swamp.

Sign in to post a ripple.