Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Deep links do not work when the URI is handled by an agent window

未关闭
#1,087 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
42/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
活跃
技术栈
typescript, vscode

调研方向

从 package.json 开始,检查 activation event 和 extension kind 元数据。在列出的 VS Code、Cursor、Devin 和 VSCodium 场景中复现 deep-link 行为,并检查 Cursor fix 是否已经发布。完成的标准是记录受影响的版本,并将 workaround 放入 README 或 Coder deep-link documentation,除非元数据提供了可行的更改。

由索引模型根据 Issue 内容生成。

描述

bug upstream

Summary

coder:// / vscode://coder.coder-remote/open?... deep links silently do nothing when the editor routes the URI to an "agent window" (VS Code Agents window, Cursor Agents window / Glass). These windows run a restricted extension host that does not load third-party extensions, so the extension is never activated and its registered vscode.window.registerUriHandler callback is never invoked.

The renderer logs the URI as handled, so no error is surfaced. The link appears to do nothing.

Reproduction (as reported for Cursor)

  1. Install coder.coder-remote 1.15.2.
  2. Start Cursor 3.14.7 on Linux with a clean HOME and the default ~/.cursor/extensions directory.
  3. Open cursor://coder.coder-remote/open?workspace=test&url=https://coder.example.com.
  4. Repeat after initialization completes.

Observed: renderer.log records the URI as handled, but extension-host initialization does not include coder.coder-remote, and there is no activation or URI-handler entry. On the repeat attempt, Cursor invokes workbench.extensions.installExtension even though the extension is already installed.

Expected: the installed extension is loaded and its onUri handler is invoked.

Upstream reports

Why this matters

Deep links are the primary entry point from the Coder dashboard ("Open in VS Code" / "Open in Cursor"). If the user's active or only window is an agent window, the flow fails with no feedback.

Scope

Tracking. The root cause is in the editor, not in this extension, so the work here is likely limited to:

  1. Confirming which editors and versions are affected (VS Code stable/insiders, Cursor, Devin, VSCodium).
  2. Confirming whether the Cursor fix has shipped and in which version.
  3. Deciding whether to document the workaround in the README or in the Coder docs deep-link section.
  4. Investigating whether anything in package.json (for example an explicit onUri activation event, or extension kind metadata) changes whether the extension is loaded in these windows.
主要语言
TypeScript
星标
131
派生
48
平均合并
2 天 3 小时
30 天内合并 PR
16

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

coder/vscode-coder 的其他 Issue

查看 coder/vscode-coder 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。