[Feedback]: Persist pasted chat images to disk so the agent can read them as files
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 45/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 领域
- desktop
调研方向
Start by locating the chat composer’s paste or attachment handling; the issue does not name a source file, test, or entry point. Done means pasted images are stored in a predictable per-session location, that path is surfaced to the session, and the agent can later read or process the image during the same conversation.
由索引模型根据 Issue 内容生成。
描述
What problem are you trying to solve?
When an image is pasted into the chat composer, it reaches the model as vision input but is never written to disk. The agent's own tools (read_file, shell, etc.) therefore have no path to it, so within the same session the agent cannot reference, embed, move, or post-process the image. If the user says "add this image to this file/note", the agent has nothing to read, and after the fact the paste is unrecoverable.
I confirmed the paste is not persisted anywhere: ~/Library/Application Support/Command Code/ (app-state.json, Local Storage, Session Storage, blob_storage, thread-index.db*) and the OS temp dir contain no trace of it — the only stored image is the 128x128 account avatar. No clipboard temp file is created for it either.
What would improve it?
Write pasted/attached images to a predictable on-disk location at paste time (e.g. a per-session scratch/temp directory), and surface that path to the session so the agent's tools can read it — either as an attachment API/tool or by injecting the path into the user message. Keeping the files for the life of the session would let an image be referenced later in the same conversation.
What do you do today?
Take a macOS screenshot (saved to ~/Pictures/Screenshots/) and tell the agent to read that file path instead of pasting into the composer.
- 主要语言
- Shell
- 星标
- 89
- 派生
- 7
- 平均合并
- 2 小时 46 分钟
- 30 天内合并 PR
- 1
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
CommandCodeAI/desktop 的其他 Issue
-
[UI Bug][macOS] Sidebar toggle is vertically misaligned with window controls可能已有人在做 @aliarain 于 6 天前认领。 未关闭bug
难度 2/5 1-3 小时 新手友好度 70/100
CommandCodeAI/desktop#125 · 1 条评论 · 已指派 1 人 ·
-
[Feedback]: add copy block under a code block可能已有人在做 @aliarain 于 11 天前认领。 未关闭enhancement
难度 2/5 1-3 小时 新手友好度 68/100
CommandCodeAI/desktop#94 · 已指派 1 人 ·
-
[Feedback]: Add Expand & Collapse for changes可能已有人在做 @aliarain 于 11 天前认领。 未关闭enhancement
难度 2/5 1-3 小时 新手友好度 68/100
CommandCodeAI/desktop#66 · 1 条评论 · 2 个 reaction · 已指派 1 人 ·
-
bug
难度 3/5 1-2 天 新手友好度 48/100
CommandCodeAI/desktop#135 ·
-
bug
难度 4/5 3-5 天 新手友好度 55/100
CommandCodeAI/desktop#133 ·
查看 CommandCodeAI/desktop 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
area/tests theme/ci-dx
难度 2/5 1-3 小时 新手友好度 85/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 74/100
FluidNumerics/fluid-walk-blocker#172 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
quickemu-project/quickemu#1960 ·
-
bug customer-reported
难度 2/5 1-3 小时 新手友好度 82/100
MagnaCapax/PMSS#1011 ·
维护者通常 5 天内回复