Overview
GitHub
Docs
Put screenshots, recordings, and other artifacts on GitHub PRs, issues, and code reviews with one command.
What it does #
Agents produce screenshots, recordings, test reports, and logs 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, every artifact appears in one tidy comment that updates automatically on each revision.
With the uploads CLI you can:
- Attach screenshots, video, and other files to a GitHub PR, issue, or code review — kept in one managed comment.
- Capture and annotate a screenshot of a page in one step.
- Get a stable public URL for any accepted file — images, clips, PDFs, logs, JSON, zips — on the branch you're already on.
- Collect media into a gallery behind one link, or share a live link to the files on a repo or pull request.
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 artifacts to pull requests for staging and before/after pairing.
Already have a PR open? Use uploads attach instead — see the walkthrough →.
Explore the docs #
Attach to pull requests →
Post files to a PR or issue, stage them before it opens, and get a URL for any file.
Capture & annotate →
Screenshot a page in one step and mark what changed with boxes, labels, and redactions.
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. Covers experimental AI labels.
MCP server →
Connect any MCP client to the hosted server. Authentication, scopes, and every tool's parameters.
REST API →
Call api.uploads.sh directly. Auth, pagination, errors, and every endpoint.
Galleries →
Ordered sets of media behind one public link, linkable to a PR or issue.
Live links →
A newest-first page of the files on a GitHub repo, or one pull request, behind one public link.
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.
uploads docs / MCPsearch_docs.