← Changelog
October 24, 2026

Mark the spot on a screenshot

Draw a box or a freehand line where your agent's work needs to change and say why. Marks stay with that exact screenshot, take replies, work on approvals too, and come back to your next agent session through MCP.
When your coding agent sends back a screenshot of what it built, you can now draw on the exact place that needs to change and say what's wrong there. Each mark and its note are saved with that screenshot, and the next agent session gets them back through AIMake's MCP server.

Why it matters

A change request used to be a paragraph: "the button on the left, under the card fields, the label is cut off." The agent had to work out where you meant. Now you point at it. Each mark is numbered and has its own note, so one review can cover several problems without them blurring together, and the agent can fix them one by one.
Marks belong to the exact screenshot you reviewed. When the agent sends a revised capture, your old marks don't move onto the new image; they stay in the review history with the version they were drawn on.

How to use it

1.
Open a screenshot that's waiting for your review.
2.
Choose Request changes or Leave feedback. Marking turns on. You can also press Mark on the image.
3.
Pick Box to drag a rectangle, or Pen to draw freely: circle something, underline it, point an arrow at it.
4.
Write what's wrong in each mark's note. Before you save, drag a mark to move it, pull its corner to resize it, or remove it with ×.
5.
Add an overall note if you like. It's optional once a mark has a note.
6.
Save. The marks stay on the screenshot under Changes requested.
While you're marking, dragging draws instead of panning. Pinch, Ctrl-scroll and the + and − keys still zoom, so you can zoom in to mark something small. Press Esc or Done marking to go back to panning.

Talk about one mark

Every saved mark has its own Reply. You and your teammates can reply from the review screen, and your agent can reply through MCP, for example to say what it changed for that mark. Replies show under the mark, labelled with who wrote them, and never change the review's decision.
Each mark keeps its own thread. Agent replies are labelled as coming from the agent.

Notes on an approval

Sometimes the work is good enough to ship and you still have a nit. Choose Approve with feedback and draw on the screenshot. The screenshot is approved, and your marks travel with it as optional suggestions that don't hold anything up.
Approved, with a suggestion for later.

On your phone

Marking works in phone browsers and in the AIMake app. Saved marks show on the screenshot, and you can draw boxes and lines, then move and resize them before you save.
Box and Pen on a phone.

What your agent receives

When your agent calls prepare_work or get_win, each review in evidence_review includes its marks, their replies and the address of the screenshot they were drawn on. For example:
"marks": [ { "number": 1, "x": 0.11, "y": 0.76, "width": 0.13, "height": 0.09, "note": "Button label is cut off. Show the full \"Pay $29.00\" text.", "replies": [{ "agent_client": "Claude Code", "content": "Widened the button." }] }, { "number": 2, "x": 0.75, "y": 0.47, "width": 0.17, "height": 0.01, "path": [[0.75, 0.47], [0.80, 0.475], [0.86, 0.47], [0.92, 0.476]], "note": "Underline the total, not the price." } ], "image_url": "https://…/the-reviewed-screenshot.png"
Positions are fractions of the screenshot's width and height from its top-left corner, so they hold at any size. A freehand mark also carries its path; its box is the line's bounds. The agent can open the image, look at each mark, fix that spot, reply with reply_to_mark, and send a new capture for your review.

Good to know

•
Once saved, marks are part of your review and don't change. To revise them, use Change my review.
•
Up to 20 marks per review; a freehand line keeps up to 400 points.
•
In the AIMake app the screenshot doesn't zoom yet, so tiny details are easier to mark in a browser.