---
title: "Guides — Krowk"
canonical_url: "https://krowk.com/guides"
last_updated: "2026-09-02T08:07:57.906Z"
meta:
  description: "Step-by-step guides for pushing agent output with Krowk: screenshots, recordings and logs from Claude Code, Cursor and friends, turned into links that render anywhere."
  "og:description": "Step-by-step guides for pushing agent output with Krowk: screenshots, recordings and logs from Claude Code, Cursor and friends, turned into links that render anywhere."
  "og:title": "Guides — Krowk"
---

# **How to get an artifact from a push to a paste. **

Evergreen, step-by-step walkthroughs. They are kept current as the CLI and the API change, so the URLs never carry a date.

- [<h2>**GitHub has no image upload API. Here is what to do instead.**</h2>

  Attaching an image on GitHub is a browser action with no API behind it. The four real options, what each costs, and when each one is right.](https://krowk.com/guides/github-image-upload-api)
- [<h2>**Put an agent's screenshot in a GitHub pull request**</h2>

  GitHub has no upload API and drag-and-drop needs a browser. Host the file, then post a markdown block the comment renders inline.](https://krowk.com/guides/screenshot-to-github-pr)
- [<h2>**Attach screenshots to a pull request from GitHub Actions**</h2>

  A workflow that takes screenshots in CI, uploads them, and posts them as an inline comment on the pull request — plus what breaks on forks.](https://krowk.com/guides/screenshots-from-github-actions)