openclaw / openclaw/openclaw-windows-node

Make links clickable in Windows Companion chat

Open
#1,429 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

clawsweeper:needs-product-decision clawsweeper:needs-security-review clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster P2
Dominant language
C#
Stars
2.1k
Forks
295
Avg merge
1d 6h
Merged PRs (30d)
99

Description

Problem URLs and Markdown links displayed in Windows Companion chat are rendered as text rather than clickable links. Users must manually copy and paste URLs into a browser, which makes documentation, issue references, tool output, and assistant responses harder to use. ## Expected behavior - Plain URLs such as https://example.com are detected and rendered as clickable links. - Markdown links such as [Example](https://example.com) are rendered with clickable link text. - Activating a link opens it using the user's default browser. - Link text remains selectable and supports normal keyboard navigation and accessibility behavior. - Unsupported or malformed URI schemes are not launched. ## Acceptance criteria - Links are clickable in assistant and user messages. - Links remain clickable in bulleted lists, tables, and other supported Markdown content. - Mouse, keyboard, and screen-reader activation are supported. - Tests cover plain URLs, Markdown links, malformed links, and unsafe URI schemes.

Screenshot

The authorization URL is rendered as plain text and cannot be activated directly from chat. The one-time code has been redacted.

Windows Companion chat showing a non-clickable authorization link

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the Windows Companion chat message-rendering entry point and locate the existing Markdown rendering and message tests. Trace how assistant and user messages handle URLs, then verify completion with coverage for plain and Markdown links, supported content such as lists and tables, keyboard and screen-reader activation, malformed links, and unsafe URI schemes.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
desktop
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
62/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.