**[Gap / feature request] Desktop app can't list or steer GitHub-hosted cloud...

**[Gap / feature request] Desktop app can't list or steer GitHub-hosted cloud-agent sessions**

**Environment:** GitHub Copilot desktop app **v1.1.0**, Linux (Ubuntu); bundled Copilot CLI 1.0.73.

**Summary:** Cloud-agent (coding agent / Actions-hosted) sessions started from GitHub Mobile or github.com are steerable on web, mobile, and via the Copilot extension in IDEs — but the **standalone desktop app can't surface or steer them.** It's the only Copilot client that can't continue a cloud-agent session, forcing a switch to VS Code or the browser.

**Repro:**

1. Start a cloud-agent session from GitHub Mobile / github.com on a repo.

2. In the desktop app: ＋ → "Resume remote session…".

3. The cloud-agent session does **not** appear in the list.

**Observed (from `~/.copilot/logs/github-app.*.log`):**

- The app's `list_remote_sessions` returns only **CLI remote-mode** (locally-originated, mirrored) sessions. The Actions-hosted cloud-agent task IDs never appear in any `list_remote_sessions` response — so `resume_remote_session` has nothing to attach to.

- Separately (not this ask): CLI-mirror resume hits `session.permissions.setAllowAll` 30s timeout when `cli_remote_control_enabled=false`; and in-app `create_cloud_workspace` → `session.create` returns `usage not allowed by billing` on personal repos. Both distinct from *steering existing* sessions.

**Ask:** Give the desktop app **list + open + steer** for the user's GitHub-hosted cloud-agent sessions (parity with web/mobile/IDE): list (repo, title, status) → open transcript → send follow-ups.

**Acceptance:** sessions from web/mobile appear in the app; user can open + follow-up; status updates; works wherever it's steerable on github.com without VS Code; decoupled from the in-app create billing gate.

**Impact:** Removes forced multi-tool workflow; makes the desktop app a true single hub — notably for mobile-start → desk-continue flows.

---
| Field | Value |
| --- | --- |
| App version | 1.1.0 |
| OS | Ubuntu 24.4.0 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Day 3 (Week 1) |

Start from the desktop app's /chat flow and inspect the list_remote_sessions and resume_remote_session behavior, using the referenced ~/.copilot/logs/github-app.*.log output as context. Done means web- or mobile-created GitHub-hosted sessions appear with repository, title, and status, can open their transcript, accept follow-ups, and receive status updates without depending on the in-app creation billing path.

索引モデルが issue の本文から書いたものです。