Agents should fetch and view issue image attachments before starting work #405
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
When an agent reads a Forgejo issue via the API, image attachments appear only as
markdown links in the issue body (
) plus assetmetadata (
assets[].browser_download_url). The pixels are not included in theresponse. Unless the agent explicitly downloads and views the attachments,
anything conveyed only by a screenshot is invisible to it — and nothing in the
current workflow makes it do that.
Evidence
cmoriarty/scratch-vllm-fp8issue #6 ("UI fixes") reported a visual bug (cardscut off at the bottom) with three screenshots. The agent that worked the issue
missed the clipping bug while handling the text-only items fine. All three
attachments on the issue have
download_count: 0— nobody ever fetched them.Proposed fix
Before starting work on an issue, the agent should:
assetsarray.curl -sL -H "Authorization: token $FORGEJO_TOKEN" -o <name> <browser_download_url>This could be baked into the orchestrator's step prompt, or built into the
issue-reading tooling so that fetching an issue automatically pulls its
attachments into the agent's context.
Acceptance criteria
actual image content, not just the markdown links.
agent should be able to describe the bug from the image alone.
Shipped in PR #406 (merged 2026-11-06,
962ca318).Issue.assetsreads the forge's attachments;download_issue_assetsfetches each image with the token, checks the bytes and saves it under.osf/brief-assets/, out of the PR diff.brief_from_issuepoints each embedded screenshot at its saved file ("read it before you plan or write code") and lists attachments the text never references, so a screenshot-only issue is still a request.script.briefruns the best-effortosf.forgejo brief-assetsstep; a screenshot that does not land is said so in the brief, and the step never fails the run.Evidence: the PR's tests (fetch, verification, the brief's pointers, the wizard and webhook paths) and a green suite. Closing on that; the first run from a screenshot-only issue is the production check, and a miss there is a new ticket.