Repository navigation
feat(drivers): agent-desktop returns the images its calls write, and the macOS drivers say the computer's files stay on it - #504
Merged
earakely-scale merged 4 commits intoNov 5, 2026
Conversation
…both macOS drivers say the computer's files stay on it The agent runs apart from the computer, so it can't read a file a driver writes there: agent-desktop's screenshot output_path (seen on 5 Nov in MB-11, where Read of the path failed) and clipboard images. Each image file a call's answer names now comes back beside the answer, up to 8 MB in all; agent-desktop's and macos-harness's instructions add a line saying the other files stay on the computer. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ny image its answer names An answer can echo a path from the agent's own input; attaching every existing image it named would hand over files the call didn't write. Only files modified since the call started come back. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
…d, and names those it can't attach A call's answer now carries the files its screenshot commands saved, each one's data.path, a batch's included, instead of any recent image the answer names, so a path echoed from elsewhere (a clipboard, a find) never hands a file over. A saved screenshot that can't be read, or that is past the 8 MB an answer carries, is named in a line after the answer instead of failing it. The fake server answers as agent-desktop does, and the test covers a batch, a duplicate, a relative path, the cap and an unreadable file. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…s it A saved screenshot past what's left of the 8 MB an answer carries is now skipped from its size, without reading it. The test's unreadable screenshot is a folder instead of a write-only file, which root, as CI runs, can read. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
earakely-scale
deleted the
edgararakelyan/fd-5264-b9-a-drivers-file-outputs-reach-the-agent-agent-desktop-and
branch
November 5, 2026 18:49
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The agent runs apart from the computer, in its own container, so it can't read a file a driver writes on the computer. agent-desktop and macos-harness assume they share the agent's filesystem, which is how their vendors run them. With this PR, agent-desktop returns the images its calls write, and both drivers' instructions say the other files stay on the computer.
What's in it
agent-desktop returns the images its calls write (
drivers/envs/agent-desktop/driver.py)output_path, a batch's commands, and a clipboard image written to a file. The vendor's answer is unchanged; the images are added after it.Both drivers' instructions say what stays on the computer
--keepcopies included, comes back as an image, and that the files the harness names stay on the computer. Its driver already attached each screenshot a read names, so this only adds the sentence.Why
On 5 Nov, in four agent-desktop MB-11 trials (Sonnet 5.5), the agent saved a screenshot to
output_pathand then tried toReadit, which failed with "File does not exist". All four still passed, but took 33–54 turns. The vendor's own setup runs the agent where the files are, so returning what the tools wrote gives the agent the same reach. The alternative, a read-file tool for every computer, would add a tool no vendor ships and change every driver's tool surface.Tested
tst/unit/drivers/agent_desktop_driver_test.pyandmacos_harness_driver_test.pypass on an EC2 Mac (11 tests), and ruff is clean.output_pathcomes back as the image, while a trace export's HTML, and an image path the call never wrote, don't.Linear: FD-5264.
🤖 Generated with Claude Code
The PR appears safe to merge; the previous finding is fixed and no new actionable issues were found.Summary
Adds saved screenshots to agent-desktop answers and tells agents that other files remain on the computer.
Reviews (3) · Last reviewed commit: "fix(drivers): agent-desktop checks a scr..." · Reviewed by Greptile