github / github/copilot-cli

Mission Control dashboard links 404: /copilot/tasks/<uuid> path doesn't exist; sessions actually live at /agents/tasks/<uuid>

Abierto
#4,775 3 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

triage
Lenguaje dominante
Shell
Estrellas
11.2k
Forks
1.9k
Merge medio
14 h 16 min
PR fusionados (30 d)
6

Descripción

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
  1. Open https://github.com/copilot -> "Created by me" (or any session list).

  2. Click the first remote session in the list.

  3. Observe: browser shows a 404 / page-not-found for the task.

  4. In a terminal on the same account, run:

    copilot --resume=05db5cb6-fea4-43ee-8914-4460ca096ca3

  5. 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.

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Línea de trabajo

Comienza con la lista de sesiones "Created by me" de Mission Control y el punto de entrada --resume de la CLI; después, sigue cómo se compone la URL de cada sesión y compárala con el endpoint documentado /agents/tasks/. Se considera terminado cuando al hacer clic en una sesión del dashboard se abre la tarea correspondiente en lugar de devolver 404, mientras el flujo existente de reanudación de la CLI sigue funcionando.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
github, shell
Área
frontend, web-dev
Tipo de issue
Error
Dificultad
3/5
Tiempo estimado
1-2 días
Estado de actividad
Activo
Claridad
Bastante claro
Aptitud para principiantes
65/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.