Add bulk transient-data cleanup messaging to the session list
- 主要语言
- 没有语言数据
- 星标
- 2.1k
- 派生
- 153
- PR 合并指标
- 30 天内没有已合并 PR
描述
## Problem
The Storage / Sessions list shows which sessions are consuming space, but cleanup still has to be requested one session at a time. When several sessions have accumulated transient data, reclaiming storage is unnecessarily repetitive.
## Proposed experience
Add multi-select support to the Storage / Sessions list and a bulk action that sends a cleanup message to every selected session.
Suggested flow:
1. Select multiple sessions.
2. Choose **Ask sessions to clean up transient data**.
3. Review or edit the message before sending.
4. Send the message to all selected sessions and show per-session delivery status.
The confirmation should make clear that each session performs its own cleanup rather than the list view deleting files directly.
## What “transient data” includes
Transient data means session-owned, safely regenerable artifacts that are not part of the user's intended work, for example:
- build outputs and generated artifacts
- dependency, compiler, test, and package-manager caches
- test results, coverage output, logs, traces, and crash dumps
- temporary downloads, extracted archives, scratch files, and stale lock/PID files
- stopped-process runtime data and other disposable files created by tools during the session
Cleanup must preserve tracked project files, uncommitted source changes, commits, user-authored artifacts, configuration, credentials, and anything whose ownership or disposability is uncertain.
## Sample prompt
> Inspect this session's workspace and storage usage, then clean up transient data that is safe to regenerate. This may include build output, generated artifacts, dependency/compiler/test caches, coverage and test results, logs, traces, crash dumps, temporary downloads, extracted archives, scratch files, stale lock/PID files, and runtime data from stopped processes. Preserve all tracked files, uncommitted source changes, commits, user-authored artifacts, configuration, credentials, and anything you cannot confidently identify as disposable. Do not use broad or destructive deletion commands. Report what you removed and how much space was reclaimed; if nothing can be safely removed, say so.
## Acceptance criteria
- Multiple sessions can be selected in the Storage / Sessions list.
- A bulk action opens an editable, prefilled cleanup message.
- Confirming sends the message to every selected session.
- The UI reports delivery success or failure for each session.
- A failure in one session does not prevent delivery to the others.
- The default prompt explicitly protects user work and discourages broad destructive deletion.
贡献指南
调研方向
从桌面应用的 Storage / Sessions 列表开始,跟踪现有的单会话清理请求流程。添加多选、可编辑的清理消息、每个会话的发送结果以及独立的失败处理;完成的标准是满足所有列出的验收标准,且不从列表视图中删除文件。
由索引模型根据 Issue 内容生成。
评估
- 领域
- desktop
- Issue 类型
- 功能
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 冷清
- 描述清晰度
- 基本清楚
- 新手友好度
- 55/100