[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 於 7 天前認領。 未關閉bug
難度 2/5 1-3 小時 新手友好度 70/100
CommandCodeAI/desktop#125 · 1 則留言 · 已指派 1 人 ·
-
[Feedback]: add copy block under a code block可能已有人在做 @aliarain 於 12 天前認領。 未關閉enhancement
難度 2/5 1-3 小時 新手友好度 68/100
CommandCodeAI/desktop#94 · 已指派 1 人 ·
-
[Feedback]: Add Expand & Collapse for changes可能已有人在做 @aliarain 於 12 天前認領。 未關閉enhancement
難度 2/5 1-3 小時 新手友好度 68/100
CommandCodeAI/desktop#66 · 1 則留言 · 2 個 reaction · 已指派 1 人 ·
-
bug
難度 3/5 半天 新手友好度 65/100
CommandCodeAI/desktop#136 ·
-
bug
難度 3/5 1-2 天 新手友好度 48/100
CommandCodeAI/desktop#135 ·
查看 CommandCodeAI/desktop 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 76/100
維護者通常 1 天內回覆
-
area:kubernetes area:site priority:high source:automated type:content-request
難度 2/5 1-3 小時 新手友好度 80/100
stephrobert/blog-roadmap#58 ·
-
enhancement severity:low
難度 2/5 1-3 小時 新手友好度 79/100
維護者通常 1 天內回覆
-
難度 1/5 1 小時以內 新手友好度 90/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 70/100
nushell/nushell#19176 · 2 則留言 ·
維護者通常 1 天內回覆