Cursor cloud agents are mostly working properly, submitting Github PRs and reacting to update requests etc. However the one thing that is not working is the new feature where screenshots and videos are supposed to be posted on the PR. I can see the agent has taken screenshots and videos and they are being written to the magic /opt directory that I’m assuming the platform is watching in order to automatically post them, but they never appear on the PR.
I have the setting for what to post to PRs set to “Artifacts”, but it also did nothing when it was set to “Links”.
So the overall Github connection to the cloud agents is working fine, but the specific part that is supposed to do the screenshots and videos is not.
Steps to Reproduce
start a cursor remote agent with a request that produces screenshots or videos
Hey, thanks for the report. This is a known issue, and the team is tracking it. The Computer Use feature just launched, so there are still some rough edges with posting artifacts to PRs.
Could you share a link to one of the affected PRs and/or the cloud agent run? That’ll help the team investigate your specific case.
Also, just to confirm, are you running these cloud agents from a Teams/Pro account or Free? And is the repository public or private?
Hi all - posting artifact screenshots to GitHub is not yet supported. They’re currently only viewable within Cursor (IDE, web app, mobile). I’m hoping to build support for it soon.
seeing “Waiting for upload…” indefinitely sounds like a separate issue, will investigate
Seeing the same for our cloud agents. They will test the UI, say they are starting the screen recording, that processing completed but there isn’t a way to view the recording on Cursor web.
Here is an example from this morning:
bc-4a123a6c-9072-4dd6-a1b7-a6dcffb0f742
Let me know if there’s something we can adjust in the prompt to make it more likely.
Here is another example bc-4cf1ae8d-4e5a-4aca-9523-02f1d7d405ad, where it got closer by referencing a file though the tag didn’t render the actual video element.
<recording_ref src="/opt/cursor/artifacts/product_merge_request_full_workflow.mp4">Full workflow: tools index with pending request, creating a new merge request with product search, viewing details, approving and completing the merge</recording_ref>
@neals you’re seeing this issue in Web or in GitHub? can you share screenshots or more information? Feel free to DM. (this recording_ref does not look like a standard thing the agent should be using)
