`tasks.list` returns a restored detached shell with an empty `description` and `command`
還沒有人認領這個 Issue。
評估
- 難度
- 3/5
- 預估耗時
- 1-2 天
- 新手友好度
- 57/100
- Issue 類型
- 缺陷
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- typescript
研究方向
Start at the implementation of session.rpc.tasks.list() and the TaskShellInfo type, then trace how detached shells are restored during client.resumeSession(...). Check how the task metadata and running process ID are persisted and recovered. Done means restored tasks retain their description, command, and PID when available, or the type makes missing values explicit; add or update tests for that behavior.
由索引模型根據 Issue 內容生成。
描述
After a session is resumed, session.rpc.tasks.list() can return a detached shell that was started before the resume with description: "" and command: "", and without pid. TaskShellInfo types description and command as required strings, so consumers can't tell that this information is missing.
What we saw
VS Code Insiders on macOS (arm64), October 18–19, 2026. VS Code main pins @github/copilot-sdk 1.0.23-preview.5.
-
The agent started a long-running detached shell with the
bashtool (mode: "async",detach: true,shellId: "component-explorer-server", with a description and a command). -
Days later, after VS Code restarted, the session was resumed with
client.resumeSession(...), then resumed again in the same client process after a model change. -
After the second resume,
tasks.list()returned this task, with astatusofrunningoridleand nopid:{ "type": "shell", "id": "component-explorer-server", "description": "", "command": "", "startedAt": "2026-10-16T16:44:19.681Z", "attachmentMode": "detached" }
VS Code only saw the shell after the second resume, and kept listing it this way for the next 8+ hours.
Expected
- A restored detached shell keeps the
descriptionandcommandit was started with, and itspidwhile the process is running. - If those can't be recovered,
TaskShellInfomarks them optional, so consumers know to handle missing values.
Impact
VS Code shows active background shells from tasks.list(). This one rendered as a row with no name, and because VS Code only offers Stop for a detached shell with a pid, it couldn't be stopped. VS Code is adding a fallback name in https://github.com/microsoft/vscode/pull/342588.
- 主要語言
- Java
- 星號
- 10.7k
- 分支
- 1.5k
- PR 合併指標
- 30 天內沒有已合併 PR
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
github/copilot-sdk 的其他 Issue
-
Rust: ElicitationRequest drops the tool call id from elicitation.requested可能重新可做 關聯的 PR 已關閉且未合併。 未關閉
難度 2/5 1-3 小時 新手友好度 78/100
github/copilot-sdk#2900 ·
-
難度 1/5 1 小時以內 新手友好度 84/100
github/copilot-sdk#2876 · 1 則留言 · 1 個 reaction ·
-
Python ModelLimits drops max_output_tokens from model metadata可能重新可做 關聯的 PR 已關閉且未合併。 未關閉bug
難度 2/5 1-3 小時 新手友好度 78/100
github/copilot-sdk#2798 · 1 則留言 ·
-
難度 2/5 1-3 小時 新手友好度 65/100
github/copilot-sdk#2759 ·
-
docs/AGENTS.md is repo authoring guidance, but everything in docs/ gets published可能重新可做 關聯的 PR 已關閉且未合併。 未關閉documentation
難度 1/5 1 小時以內 新手友好度 85/100
github/copilot-sdk#2758 ·
查看 github/copilot-sdk 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 72/100
aws/serverless-java-container#1729 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 75/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 75/100
ls1intum/thesis-management#1473 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 76/100
LunaDeerMC/Dominion#301 · 1 則留言 ·
-
[FEATURE] Expose external refresh, node-level translog and warmer stats可能已有人在做 關聯的 PR 仍在進行中或已合併。 未關閉untriaged
難度 2/5 1-3 小時 新手友好度 68/100
opensearch-project/opensearch-prometheus-exporter#680 ·
維護者通常 2 天內回覆