URL autolinking
Category: markdown
Turns a bare https://… URL in a plain text content block into a clickable link. In terminal clients this means emitting OSC 8 hyperlinks, not just underline/color.
Support by client
| Client | Status | Notes | Verified |
|---|---|---|---|
| supported | Bare URL rendered as clickable underlined hyperlink: 'Check https://doesitsupport.com for the matrix.' — the URL is styled as a link (underlined, distinct color). | 2026-07-05T15:55:58.367Z | |
| supported | Line 2: The bare URL "https://doesitsupport.com" is rendered underlined as a clickable hyperlink, not plain text, indicating autolinking is applied. | 2026-07-08T14:58:50.812Z | |
| supported | Bare https://doesitsupport.com rendered as tappable underlined link in reply. call id e1d964. Automated via Mirroir. | 2026-07-09T14:30:04.744Z | |
| unknown | — | ||
| partial | Tool was called and the model echoed the probe's call-id — but behavioral can't tell whether the client actually rendered the markdown variant (table/code/math/diagram/image/task/URL) vs. surfaced the source. Prefer vision-tier for a definitive answer. | 2026-07-08T19:31:36.602Z | |
| supported | Inline clickable link 'https://doesitsupport.com' with external-link icon visibly rendered in assistant message body; autolink parsing works. | 2026-07-05T14:52:48.307Z | |
| unknown | — | ||
| unknown | — | ||
| unknown | — | ||
| unknown | Client did not invoke the probe tool; can't infer rendering support. | 2026-07-02T17:50:40.262Z | |
| unknown | — | ||
| unknown | — | ||
| unknown | — | ||
| unknown | — | ||
| unknown | — | ||
| partial | Tool was called and the model echoed the probe's call-id — but behavioral can't tell whether the client actually rendered the markdown variant (table/code/math/diagram/image/task/URL) vs. surfaced the source. Prefer vision-tier for a definitive answer. | 2026-07-08T15:43:07.127Z | |
| unknown | — | ||
| unknown | — | ||
| partial | Tool was called and the model echoed the probe's call-id — but behavioral can't tell whether the client actually rendered the markdown variant (table/code/math/diagram/image/task/URL) vs. surfaced the source. Prefer vision-tier for a definitive answer. | 2026-07-04T14:45:19.312Z | |
| unknown | — | ||
| partial | Tool was called and the model echoed the probe's call-id — but behavioral can't tell whether the client actually rendered the markdown variant (table/code/math/diagram/image/task/URL) vs. surfaced the source. Prefer vision-tier for a definitive answer. | 2026-07-04T14:55:49.130Z | |
| unknown | — | ||
| unknown | — | ||
| unknown | — | ||
| unknown | — | ||
| unknown | — | ||
| unknown | — | ||
| unknown | — | ||
| unknown | — | ||
| unknown | — | ||
| partial | Tool was called and the model echoed the probe's call-id — but behavioral can't tell whether the client actually rendered the markdown variant (table/code/math/diagram/image/task/URL) vs. surfaced the source. Prefer vision-tier for a definitive answer. (tool_use event and debug log both missed; inferred toolCalled from call-id echo) | 2026-07-02T18:12:10.079Z | |
| unknown | — | ||
| unknown | — | ||
| unknown | Tool was called but the model did not echo the probe's call-id; can't infer rendering. Prefer vision-tier for a definitive answer. | 2026-07-04T14:54:25.777Z | |
| partial | Tool was called and the model echoed the probe's call-id — but behavioral can't tell whether the client actually rendered the markdown variant (table/code/math/diagram/image/task/URL) vs. surfaced the source. Prefer vision-tier for a definitive answer. | 2026-07-04T14:54:03.545Z | |
| unknown | — | ||
| unknown | — | ||
| unknown | — |