Feedbackers

Tracking since Apr 24, 2026.

Changelog

• May 1, 2026
  description

  Feedbackers is a Chrome extension that turns any webpage into a feedback surface — select a screen or an element, and post it straight to GitHub Discussions with a screenshot attached. No more downloading screenshots, opening issues, pasting images, and copying URLs by hand.
  
  ■ What it does
  
  • Select the whole screen or any element on any webpage to create a feedback item
  • Automatically attaches a screenshot, element metadata (tag, position, text), and the page URL
  • Posts directly to GitHub Discussions from the browser side panel
  • Browses existing discussions and pins them on the page so you can see where each one was filed
  • Replies to discussions from the side panel
  • Configures a target repository per site (per domain)
  
  ■ Why install it
  
  1. Feedback in 5 seconds, not 5 minutes
     Replaces the "capture screenshot → save file → open issue → paste image → copy URL" dance with a single click.
  
  2. Context is preserved automatically
     Every post carries the page URL and the selected element, so teammates reading the thread later know exactly what you were looking at.
  
  3. Your discussions stay in GitHub
     Feedback lives as regular GitHub Discussions — reuse your existing search, notifications, labels, and permissions. No extra SaaS subscription.
  
  4. See past feedback on the page itself
     Existing discussions can be pinned directly on the page, so it's obvious which parts of a screen have already been discussed.
  
  5. Privacy-respecting by design
     Authentication uses GitHub's official OAuth 2.0 web flow with PKCE. Access and refresh tokens are stored only in your browser's local storage. Feedback is sent only to the GitHub repository you configure — no third-party servers in between.
  
  ■ Who it's for
  
  • Design + engineering teams that want fast, lossless UI feedback loops
  • QA engineers reviewing staging environments who need to say "this looks off" with full context
  • Product managers and designers who want a feedback tool non-technical stakeholders can use
  • Any project that wants feedback consolidated on GitHub instead of scattered across chat, docs, and tickets
  
  ■ Requirements
  
  • A GitHub account
  • Access to a GitHub repository with Discussions enabled
  
  ■ Supported languages
  
  English / Japanese

  Feedbackers is a Chrome extension that turns any webpage into a feedback surface — select a screen or an element, and post it straight to GitHub Discussions with a screenshot attached. No more downloading screenshots, opening issues, pasting images, and copying URLs by hand.
  
  ■ What it does
  
  • Select the whole screen or any element on any webpage to create a feedback item
  • Automatically attaches a screenshot, element metadata (tag, position, text), and the page URL
  • Posts directly to GitHub Discussions from the browser side panel
  • Browses existing discussions and pins them on the page so you can see where each one was filed
  • Replies to discussions from the side panel
  • Configures a target repository per site (per domain)
  • Local Mode: on-device per-page notes that work without GitHub sign-in
  • Copy Local Mode notes as Markdown in one click — use them with an AI Agent, share with your team, or keep them for yourself. Never sent to GitHub
  
  ■ Why install it
  
  1. Feedback in 5 seconds, not 5 minutes
     Replaces the "capture screenshot → save file → open issue → paste image → copy URL" dance with a single click.
  
  2. Context is preserved automatically
     Every post carries the page URL and the selected element, so teammates reading the thread later know exactly what you were looking at.
  
  3. Your discussions stay in GitHub
     Feedback lives as regular GitHub Discussions — reuse your existing search, notifications, labels, and permissions. No extra SaaS subscription.
  
  4. See past feedback on the page itself
     Existing discussions can be pinned directly on the page, so it's obvious which parts of a screen have already been discussed.
  
  5. Privacy-respecting by design
     Authentication uses GitHub's official OAuth 2.0 web flow with PKCE. Access and refresh tokens are stored only in your browser's local storage. Feedback is sent only to the GitHub repository you configure — no third-party servers in between.
  
  ■ Who it's for
  
  • Design + engineering teams that want fast, lossless UI feedback loops
  • QA engineers reviewing staging environments who need to say "this looks off" with full context
  • Product managers and designers who want a feedback tool non-technical stakeholders can use
  • Any project that wants feedback consolidated on GitHub instead of scattered across chat, docs, and tickets
  
  ■ Requirements
  
  • A GitHub account
  • Access to a GitHub repository with Discussions enabled
  
  ■ Supported languages
  
  English / Japanese
  
  ■ Documentation
  
  A user guide and admin setup instructions are published as a public Gist in both English and Japanese.
  
  https://gist.github.com/dameleon/b9d49d28290ff92c503025c1e761e829

• May 1, 2026
  short_description

  Select screens or elements on any website and post feedback to GitHub Discussions. Gather your team's voice and drive improvements.

  Capture feedback on any site — post to GitHub Discussions or keep per-page notes on your device. Drive improvements.

Permissions & access

Permissions

storageactiveTabtabsscriptingcontextMenussidePanelidentity

Host access

<all_urls>

Screenshots