GitHub CLI Media

Use --attach on supported gh issue and gh pr commands for authorized GitHub media uploads instead of committing the file or hosting it elsewhere.

Pair it with agent-browser when visual browser evidence helps: capture local before-and-after screenshots or a recording, then attach them in the same issue, pull request, or comment write.

Guardrails

• Require gh v2.99.0 or newer and confirm the target command's help lists --attach. Otherwise, report the required managed upgrade instead of attempting an undocumented upload flow.
• Treat the upload as an external write. Drafting an issue, pull request, or comment does not authorize uploading its attachments.
• Confirm the account, repository, target item, and file contents immediately before the command. Uploads require WRITE, MAINTAIN, or ADMIN access.
• Use only on GitHub.com or GitHub Enterprise Cloud. GitHub Enterprise Server and GitHub App tokens are not supported.

Attach

--attach <path> works on gh issue create, gh issue edit, gh issue comment, gh pr create, gh pr edit, and gh pr comment. Repeat the flag for multiple files:

gh issue comment 12 --repo OWNER/REPO --body 'Reproduction:' \
  --attach '/tmp/agent-browser-before.png#Before the change' \
  --attach '/tmp/agent-browser-after.png#After the change'

• A matching local path in the Markdown body is rewritten to the uploaded URL in place and keeps its existing alt text. Otherwise, attachments are appended in flag order.
• For an image, quote <path>#<alt text> so the shell does not treat # as a comment. The filename is the fallback alt text. Videos do not accept alt text.
• Supported extensions are PNG, JPG/JPEG, GIF, WebP, SVG, MP4, MOV, and WebM. One invocation accepts at most 50 attachments.
• Images and GIFs are limited to 10 MB. Video is limited to 10 MB on Free plans and 100 MB on paid plans.

Uploads stop at the first failure. Earlier files may still be attached while the command exits nonzero, so re-read the user-visible body or comment before retrying. After success, verify that referenced local paths were replaced or unreferenced media was appended, and that it renders in the intended position.

Sources: GitHub announcement, GitHub CLI docs, and the official gh skill.