Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Bug]: cursor:// and vscode:// links in chat do nothing when clicked

Open Beginner friendly
  • Is something wrong?
#16,822 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
desktop, developer-experience

Research direction

Find the external-app URI allowlist introduced in #15722 (search for schemes like linear:, slack:, notion:, obsidian: in apps/desktop) — that is the gate blocking chat links. Check how the click handler decides to shell out to the OS and whether cursor:, vscode:, zed: are missing or filtered elsewhere; also look at where markdown links in chat messages are rendered and opened. Done means cursor://file/...:186 and vscode://file/... links in a chat message launch the editor at the right line (verify manually, plus any existing tests covering the allowlist or link-click behavior), or a documented rationale for keeping them blocked.

Written by the indexing model from the issue text.

Description

bug via-triage
Before submitting
  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.
Area

apps/desktop

Steps to reproduce
  1. On macOS with Cursor installed, have an agent reply with a markdown link such as
    [file.md line 186](cursor://file/Users/me/repo/file.md:186).
  2. Click the link in the chat message.
Expected behavior

Cursor opens file.md at line 186, as it does when the same link is clicked in a browser or a terminal.

Actual behavior

Nothing happens: no app opens and no error is shown. The link is styled as a normal link. A vscode://file/... link behaves the same.

open "cursor://file/...:186" from a shell opens Cursor at the right line, so the OS handler works.

Related: #15722 adds an external-app allowlist (linear:, slack:, notion:, obsidian:) for the same root cause. This asks to add editor schemes (cursor:, vscode:, possibly zed:), or to document why they stay blocked. #16251 is the same symptom in the preview browser.

Impact

Minor bug or occasional failure

Version or commit

T3 Code (Nightly) 0.0.46-nightly.20261005.2702

Environment

macOS 26.7.1, desktop app, Claude Code provider

Logs or stack traces
_No response_
Screenshots, recordings, or supporting files

No response

Workaround

Use a plain absolute-path link, e.g. [file.md line 186](/Users/me/repo/file.md:186). It renders as a file chip, but it opens in T3's side panel, not in the editor at the line.

Dominant language
TypeScript
Stars
24.8k
Forks
6.4k
Avg merge
8h 34m
Merged PRs (30d)
243

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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.

More from pingdotgg/t3code

All issues in pingdotgg/t3code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.