drop. for software teams
Coding agents now take screenshots, record test runs and write reports. drop. gives them, and your CI, somewhere to put those files and a link to share.
A UI change, from agent to merge
Screenshots appear where reviewers look for them and clean up after themselves.
-
10:12 · Claude Code
create_upload_link · before.png, after.pngThe agent takes screenshots of the change and uploads them straight to storage.
-
10:13 · Pull request
The PR description shows the change, not just the diff.
-
10:20 · CI
drop test-results/*.png -m --expires 14dVisual test results are posted as a PR comment with links.
-
14 days later · drop.
file.expired × 5The CI screenshots delete themselves. A webhook tells you if you want to know.
Pull requests that show the change
Add drop. to Claude Code, Cursor or another MCP client and ask the agent to include before and after screenshots in its pull requests. It uploads them through a one-time link, so a long screen recording never passes through the model, and writes the markdown for you.
Files from CI, with links in the log
The drop CLI has no dependencies and runs anywhere with Node 18.3 or newer. Use it to publish visual test results, coverage reports or build artefacts and print their links into the job log or a PR comment. Give the job a key that can only write files.
Systems without Node can use curl and the REST API, or SFTP.
acme.k7f2q9@in.drop.media
Bug reports by email
Give your support team the open address. Screenshots and logs customers send can be forwarded straight into the library, where developers and their agents can find them by name, instead of being pasted into a ticket by hand.
An API and webhooks for the rest
The REST API covers uploading, listing, sharing and deleting. Signed webhooks tell your services when files are created, shared, deleted or expire, however they arrived. Every API key carries only the abilities you give it.