A Cline user answered a pending clarifying question with both typed text and an attached screenshot. The agent proceeded as if it had received both. It had only received the text.
What the source says
cline/cline#14985, filed against Cline v4.1.23 (VS Code extension). The reporter (dakjdakd) gave five repro steps: start a task that triggers Cline's ask_question prompt, type a response and attach an image or file, submit, then inspect the recorded answer and the next model input — only the typed text shows up. An attachment-only answer, with no typed text at all, resolved as an empty string.
The reporter traced the cause to two coordinator functions: sdk-followup-coordinator.ts passed only the prompt string into the pending-question resolver, and sdk-interaction-coordinator.ts resolved the question with a text-only string and built a text-only feedback message. Both points discarded the images and files on the way through. The composer cleared the attachments from the VS Code UI after submission, and the transcript showed a fully-answered question — no error, no warning that anything had been dropped.
A Cline contributor (mkondratek) acknowledged the bug on October 12 and confirmed a fix was coming. The reporter's own PR (#14986), citing 231 passing VS Code tests, 152 passing Core tests, and a passing SDK typecheck, was merged and the issue closed as completed on October 13 — four days after it was filed.
What it doesn't establish
No data loss was reported. This is one reporter's issue with one contributor's acknowledgment and a merged fix from the same person who filed it — there's no independent third-party confirmation on record, though the fast close with a passing test suite is a reasonable signal the fix works as described.
Why it's still worth logging
The failure mode here isn't data loss, it's silent information loss: a user who points the agent at a screenshot or reference file for exactly the kind of decision that needs it gets a transcript that claims the question was fully answered. Nothing in the UI or the recorded response indicates the attachment never arrived. That's the pattern worth tracking even in a bug this narrow and this quickly fixed — an agent proceeding on information it believes is complete, with no signal to the user that it isn't.
Full record, severity scoring, and frontmatter: https://www.stupidllm.com/incident/STUPID-2026-0139/
Top comments (0)