Agent chat renders a GitHub URL as only the number

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

A raw GitHub URL in an agent reply is rendered as a chip with the GitHub icon and the number only, such as #123. The owner, the repository, and whether the link is a pull request or an issue are not visible.

That number is not enough when a thread mentions more than one repository:

  • The repository is gone, so #123 can belong to any repo in the thread.
  • The number alone does not say whether the link is a pull request or an issue.
  • Search misses them. The repository name and the words pull and issues are no longer visible, and search does not seem to find these formatted links.

A markdown link keeps the label that was written. This label is a better chip:

example/one#123 - Add the export

written as:

example/one#123 - Add the export

The repository and the title stay on screen. The raw URL should render like that, not as #123.

Steps to Reproduce

  1. Ask the agent to reply with two raw URLs, in different repositories, one pull and one issue:
    https://github.com/example/one/pull/123
    https://github.com/example/two/issues/456
  2. Read the rendered reply.
  3. Search the chat for example/one, for pull, and for issues.

Expected Behavior

The chip shows the repository and the title, as in example/one#123 - Add the export, and it is clear whether the link is a pull request or an issue. Search finds the repository and pull or issues. Copying the link still yields the full URL.

Operating System

MacOS

Version Information

Version: 3.21.18
VS Code Extension API: 1.128.0
Commit: c4730f7d93d787d9ab120af715999f0345ee5bc0
Date: 2026-09-22T02:04:34.641Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 42.10.0
Chromium: 148.0.7778.280
Node.js: 24.18.1
V8: 14.8.178.38-electron.0
xterm.js: 6.1.0-beta.291
OS: Darwin arm64 25.6.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the detailed report.

About chip #123: when an agent writes a raw GitHub pull request URL, the Agents Window shortens it to the PR number and shows the PR status icon. If you hover the chip, the popup card shows the repo and the PR title, and you can right click to copy the full URL. So the repo and link type are available, but for now only on hover, not inline. I passed your feedback to the team that when there are multiple repos in one thread, a bare number becomes ambiguous. I also noted that chat search doesn’t match the repo text and pull inside these shortened links.

Workaround: links with your own label are always kept as written. You can add a rule in Cursor Settings > Rules like:

When linking a GitHub pull request or issue, always write a markdown link labeled owner/repo#number - title.

Then the agent replies will show chips like example/one#123 - Add the export, and they will also be searchable.

About the issue link: on our side, URLs like /issues/<n> should keep the full link text instead of collapsing to just the number. Can you share a screenshot of how https://github.com/example/two/issues/456 rendered on your end? That will make it clearer what’s happening.