Screenshot the bug and let the agent fix it
Take a screenshot of a bug in Borago Board's desktop app, circle it, attach it to a task with a short description, and let the agent fix it.
A picture of a bug often says more than a paragraph. Borago Board can take a screenshot from inside the task form, open it in a small paint editor so you can circle what is wrong, and attach it to the task. The agent then opens the image during the run and looks at it. This tutorial walks one bug from screenshot to a fixed task in the desktop app.
You will build
One task with an annotated screenshot attached and a description of what right looks like. One run that fixes the bug and says what it changed.
You need
- The desktop app, with a project whose app you can open and see the bug in, such as a web page served from the project's container.
- A provider whose models accept images, which the hosted providers do. The last section explains a self-hosted model.
Screenshots also work on the cloud board in a desktop browser, where the browser shows its own picker. They do not work on the plain http board on your local network or in a phone's browser.
Steps
1. Show the bug on screen
Open the page or window that shows the problem, so it is visible when you take the picture. For example, a login page whose button text runs off the edge of the button.
2. Start a new task
Press Add task in the Planning column. Give it a title such as Login button text overflows.
3. Take the screenshot
Under Attachments in the form, press the icon button whose tooltip reads Take a screenshot and annotate it. On Windows, on macOS and on Linux under X11, a chooser headed Capture what? lists your screens and windows by title. Pick the window that shows the bug.
What happens. On macOS the first screenshot raises the system's Screen Recording prompt once. If it was refused, the app shows Screen recording is off with Open System Settings, where you switch Borago Board on. On a Linux Wayland session there is no chooser of the app's own. The desktop portal's dialog asks which window or screen to share, every time, and cancelling it simply takes no picture. On Windows and X11 nothing asks. The app adds no permission dialog of its own.
4. Crop to the broken part
The picture opens in the paint editor with the Crop tool selected. Drag a box around the area that matters and press Enter.
What happens. A smaller picture keeps the agent's attention on the problem.
5. Circle it and point at it
Choose the tool whose tooltip reads Oval and drag an oval around the broken part. Choose Arrow and drag from where the tail should start to where the point should land. Optionally choose Text, click beside the arrow, type a few words and press Enter. Pick a colour that stands out from the page. Press Attach.
What happens. The picture is flat once attached. Shapes cannot be edited after they are drawn, but undo takes them back before you attach.
6. Write what is wrong and what right looks like
The thumbnail appears under Attachments. Hover it and press Reference in description, which puts the file's name in the text. Then write the rest of the description, for example:
The Sign in button on the login page is broken, see the circled area in the
attached screenshot. The label runs past the right edge of the button and
is cut off at narrow widths.
Right looks like: the whole label fits inside the button at every width
from 320px up, the button grows or the text wraps, and nothing else on the
page moves. Add a test that fails without the fix if the project has UI
tests.Press Add task.
What happens. The description carries the meaning and the picture shows the place. Write it so it still makes sense without the image.
7. Run it
Drag the card to To Do. The queue starts it, and the card moves to In Progress.
What happens. At the start of the run every attachment is copied into the project's container as a read-only file, and the prompt lists it with its path. An attachment is material to look at, never a file to run. With Claude, OpenAI, Gemini and Grok, viewing an image returns the picture itself, so the model sees your circle and arrow. A very large image cannot be viewed that way, and the agent shrinks it first.
8. Read the summary
When the card reaches Done, open it. The run leaves a comment with its summary of what it changed, and Context Summary holds its notes for later runs. If it could not reproduce the problem, it says so there, or asks a question on the task.
Check it worked
Open the page again at a narrow width. The label fits. If the project has tests, the new test is in the run's summary.
On a self-hosted model
Many small local models cannot see images. When a self-hosted model is known to lack vision, or the server refuses an image during the run, the agent works without the picture. It uses the description, and asks a question when the task truly depends on seeing it. That is why step 6 matters. See Using a local AI model.
Where to go next
- Attachments, screenshots, paint and camera covers files, drawing from scratch and photos.
- Writing tasks the agent can do says more about describing the outcome.
Related: Attachments, screenshots, paint and camera, Writing tasks the agent can do, When the agent asks a question or needs you, How a run works