Repository navigation
Replies: 3 comments
|
+1 for this, being able to comment on a region of an image available with t3code would be great |
0 replies
|
Need it |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
Problem / use case
When reviewing images or screenshots an agent shares in chat, I often want to point directly at an issue and explain what needs changing.
Currently, I have to take another screenshot, annotate it in an external tool such as Windows Snipping Tool, and paste it back into T3 Code. This interrupts the feedback workflow when the image is already available in the gallery.
Sometimes I need to explain changes across several images, so annotating one image should add it to a draft, not immediately send a message.
Proposed solution
Add a Draw / Annotate button to the image gallery, alongside the close button. In annotation mode, show basic drawing controls and an optional comment field below the image.
Provide an Add to message button that adds the annotated copy and its comment to the current chat draft without sending it.
Suggested workflow
Each image should remain clearly paired with its own comment so the agent knows which instructions apply to which image.
Example and mockup description
The proposed layout has:
For example, on a screenshot of a settings panel, an accompanying comment could say:
The user could then annotate a second screenshot and add it to the same draft before sending both together.
Smallest useful scope
Dedicated arrow, rectangle, and text-label tools could be added later.
Why this helps
This keeps visual feedback inside the conversation. Users can show exactly where a change is needed, explain it alongside the image, and collect feedback across several screenshots before asking the agent to act.
It also avoids re-capturing images, losing detail, or accidentally including unrelated surrounding UI.
Related request
#1429 proposed overlapping functionality and was closed as not planned.
I'd like to ask whether this focused gallery-to-agent feedback workflow could be reconsidered: annotate images already displayed in T3 Code, associate comments with them, and collect them into a message draft. The main purpose is to make visual instructions to the agent easier.
All reactions