Overview
Docs
Put screenshots and other media on GitHub PRs, issues, and code reviews with one command.
What it does #
Agents take screenshots long before a pull request exists, and GitHub's own attachments only work inside GitHub. Uploads hosts each file at a stable public URL the moment it's captured. When the pull request opens, all screenshots appear in one tidy comment that updates automatically on each revision.
With the uploads CLI you can:
- Attach screenshots and video to a GitHub PR, issue, or code review — kept in one managed comment.
- Get a stable public URL for any image or clip, on the branch you're already on.
- Collect media into a gallery behind one link.
Install & sign in #
Install the CLI globally:
Then run uploads login to approve sign-in in your browser — GitHub or a magic link. You'll need a workspace first: create your own with a linked GitHub account, or get invited by an admin. It's a one-time step per machine.
npx. And uploads doctor checks your setup anytime.Your first upload #
One command, on the branch you're already on — no pull request required:
That uploads the file and prints a public URL. With no PR yet, it stages the file to post automatically when the PR opens — keep running put as you work. See Attach & share for staging and before/after pairing.
Already have a PR open? Use uploads attach instead — see the walkthrough →.
Explore the docs #
Attach & share →
Post files to a PR or issue, get a URL for any accepted file, capture a screenshot, and annotate it.
GitHub App →
Recommended. Comments post as the uploads-sh bot and staged screenshots promote themselves when the PR opens.
Set up your agent →
Install the agent skills and the MCP server so your agent uploads on its own.
Galleries →
Ordered sets of media behind one public link at /g/<id>, linkable to a PR or issue.
Reference →
List, delete, and check usage, plus the things worth knowing before you rely on it.
Plans & limits →
Storage and file-size caps per plan, and how they compare with GitHub's.