OXYGENHUB

Attachments on issues: screenshots and any file, over the API, in oh and on the web issue #350 closed: completed andymccall opened this · 1 comment

andymccall

Andy, 2026-10-30: I often file issues with oh through Claude Code, pasting a screenshot into the chat. The screenshot should go onto the issue and show on its page.

Today an issue is text only: no attachments over the API, on the web or in oh.

What it needs:

  • API: attach an image to an issue or a comment (POST …/issues/N/attachments, or on create), stored by the hub and referenced from the body as Markdown (![screenshot](…)), so it renders inline on the page and in the apps.
  • oh: oh issue create … --attach FILE (repeatable), and the same on oh issue comment. Claude Code saves a pasted image to a local file, so an agent can pass that path straight through.
  • Web: paste or drag an image into the issue and comment editors.
  • Limits and safety: images only (PNG, JPEG, GIF, WebP), the type checked from the bytes rather than the name, a size cap, served with nosniff from a content-addressed path, readable only by those who can read the repository (private repositories stay private). Consider stripping location metadata from photos.
  • Proposals and drops could reuse the same attachments later.

andymccall set labels feature ·

andymccall

Andy, 2026-10-30: not only screenshots. Any file should attach: binaries, spreadsheets, logs, archives and so on. Images show inline; other files show as download links with name, size and type. Same limits apply (a size cap, content-type checks, served as downloads with nosniff, private repositories stay private).

andymccall edited ·

closed by change 1c52d940b4a0 ·