Mission Control dashboard links 404: /copilot/tasks/<uuid> path doesn't exist; sessions actually live at /agents/tasks/<uuid>
还没有人认领这个 Issue。
- 主要语言
- Shell
- 星标
- 11.2k
- 派生
- 1.9k
- 平均合并
- 14 小时 16 分钟
- 30 天内合并 PR
- 6
描述
Describe the bug
The github.com Mission Control "Created by me" dashboard shows links to remote sessions that point to a non-existent URL path. Clicking the link returns a 404, but the session itself is alive and reachable from the CLI via copilot --resume=.
The dashboard renders each session as:
https://github.com/copilot/tasks/?q=is%3Aopen
but the actual cloud API is served at:
/agents/tasks/
The two paths are not equivalent. Web routing for /copilot/tasks/ returns 404 even though the task exists in the cloud backend.
Reproduction
-
Open https://github.com/copilot -> "Created by me" (or any session list).
-
Click the first remote session in the list.
-
Observe: browser shows a 404 / page-not-found for the task.
-
In a terminal on the same account, run:
copilot --resume=05db5cb6-fea4-43ee-8914-4460ca096ca3
-
Observe: CLI prints "Remote control connected" and joins the same session, MCP servers reload successfully.
API evidence (collected 2026-09-09)
| Endpoint | Auth | Status |
|---|---|---|
| GET /copilot/tasks/05db5cb6-fea4-43ee-8914-4460ca096ca3 | no | 404 |
| GET /agents/tasks/05db5cb6-fea4-43ee-8914-4460ca096ca3 | no | 400 (bad request) |
| GET /agents/tasks/05db5cb6-fea4-43ee-8914-4460ca096ca3 | yes | 200 |
| GET https://github.com/copilot/tasks/05db5cb6-... | n/a | 404 (web route) |
The CLI itself prints https://github.com/copilot/tasks/<uuid> after a successful resume, which suggests the URL template is generated client-side from a slug that omits the /agents/ prefix, instead of being derived from the actual API endpoint the CLI talks to.
Expected behavior
Clicking a session link in the Mission Control dashboard should land on a working detail page that resolves to the same task the CLI sees.
Affected version
- GitHub Copilot CLI: 1.0.84-3 (prerelease, 2026-09-09)
- Browser: latest Chrome on Windows
- github.com web app: current
Additional context
- The dashboard lists 320 active + 292 completed sessions on this account, with many entries under "No repository" -- likely accumulated test/orphan tasks from prior CLI versions and /remote experiments.
- The CLI's --resume\ works fine; only the web frontend's URL composition is broken.
- Possibly related to issue #2813 (URL format regression), but #2813 was fixed in v1.0.33 and the URL shape here is post-fix; this is a separate routing failure rather than a URL-shape failure.
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
从 Mission Control 的“Created by me”会话列表和 CLI 的 --resume 入口开始,然后追踪每个会话 URL 的组成方式,并将其与文档记录的 /agents/tasks/ endpoint 进行比较。完成的标准是:点击 dashboard 会话时能够打开对应的 task,而不是返回 404,同时现有的 CLI resume 流程仍然正常运行。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- github, shell
- 领域
- frontend, web-dev
- Issue 类型
- 缺陷
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 活跃度
- 活跃
- 描述清晰度
- 基本清楚
- 新手友好度
- 65/100