anomalyco / anomalyco/opencode
Question tool: allow attaching screenshots/images to answers (paste or + button)
@Brendonovich is already working on this.
Since Sep 16, 2026.
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- PR merge metrics
- PR metrics pending
Description
Feature hasn't been suggested before.
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
The problem
The question tool's answer path is text-only: the user can pick options or type a string. When the question is inherently visual — "which of these two UI states?", "does this layout match what you see?", "which mock is right?" — the model must describe the visual in words, ask the question, and the user must answer in words, with no way to point at pixels. Meanwhile chat itself accepts image attachments fine, so the capability exists in the product but not at the moment of choice.
Concretely, when I ask "does this render correctly?" I can't attach "here, look" — I have to cancel the question, paste the screenshot into the composer, and re-ask. The question card becomes a dead end for the most common visual-debugging loop.
What I'd like to add
Two complementary affordances, either alone would already help:
- Paste into free-text — with the free-text/"Other…" field focused, paste an image from the clipboard. It attaches to the answer like a chat attachment.
- A "+" attachment button next to the free-text field — opens a file picker (or screenshot capture) and attaches the image to the answer.
Acceptance
- An image can be attached to a question answer (via paste or picker)
- The answer envelope carries the attachment(s) through
question.repliedso client implementations can forward them into the session - Questions without attachments behave exactly as today (purely additive)
Out of scope
- Rendering/annotating images inside the question card
- Non-image attachments
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.