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

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)

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.

Commencez par la liste des sessions « Created by me » de Mission Control et le point d’entrée --resume de la CLI, puis suivez la manière dont l’URL de chaque session est construite et comparez-la avec l’endpoint documenté /agents/tasks/. Le travail est terminé lorsqu’un clic sur une session du dashboard ouvre la tâche correspondante au lieu de renvoyer 404, tandis que le flux CLI resume existant reste fonctionnel.