FlunesYour team's feedback,
as clean GitHub issues.
Give your PMs, QA, designers, and support one link to report bugs and ideas, no GitHub account needed. Flunes structures each report and drops it into your repo, ready to act on. You stay in GitHub. They stay out of your way.
- Free forever on 1 repo
- No credit card
- Your reporters never sign up
The checkout spinner on mobile Safari hangs indefinitely after the Pay CTA is tapped, blocking order completion.
After tapping Pay, the loading spinner appears and remains visible for over a minute without redirecting or showing an error.
Tapping Pay should redirect to the order confirmation page or display a recoverable error state.
- apps/checkout/mobile/payment-flow.ts
- apps/checkout/components/PayButton.tsx
- src/lib/stripe/confirm-handler.ts
Tapping Pay just shows a spinner forever...
GitHub isn't the problem. Getting feedback into it is.
The people who spot your bugs, your PMs, testers, designers, and support, don't live in GitHub and shouldn't have to. So their reports scatter across Slack, email, and calls, and a developer ends up retyping each one into a ticket by hand.
Flunes is the thin layer between them, not a place either side has to live.
A clean tunnel for reporters
Whoever's reporting stays in one simple form.
- One link, no account, no password, no install
- Describe it in plain words, drop a screenshot
- Follow status and reply by email, never chase you
You never leave GitHub
Developers stay in the tool they already work in.
- Structured, labeled issues appear in your repo
- Triage, assign, and close like any other issue
- Closing the issue tells the reporter it's fixed
The dashboard exists only to connect the two. Set it up once, then forget it's there.
Three steps. Then it runs itself.
- 01
Connect a repo, share a link
Sign in with GitHub, pick a repo, and share one feedback link. That's the whole setup, no SDK, no widget to embed.
- 02
They report, AI structures it
A teammate describes the bug or idea in a plain form. Flunes cleans it up, detects labels and priority, and grounds it in your repo.
- 03
A clean issue lands in GitHub
It's a normal GitHub issue, triage and close it where you already work. Closing it notifies the reporter automatically.
One messy message in. One clean issue out.
A collaborator describes what broke in plain words. Flunes structures it, labels it, points at the likely code, and files it in your repo, no triage inbox for you to babysit.
“Tapping Pay on my phone just shows a spinner. It never moves past it and I can't tell if I was charged.”
The checkout spinner on mobile Safari hangs indefinitely after the Pay CTA is tapped, blocking order completion.
After tapping Pay, the loading spinner appears and remains visible for over a minute without redirecting or showing an error.
Tapping Pay should redirect to the order confirmation page or display a recoverable error state.
Prevents order completion on mobile. Users cannot confirm whether payment was processed, increasing support load and cart abandonment risk.
1. Open Safari on iPhone 2. Add an item to the cart and proceed to checkout 3. Tap the Pay CTA 4. Observe the spinner never resolves
- apps/checkout/mobile/payment-flow.ts
- apps/checkout/components/PayButton.tsx
- src/lib/stripe/confirm-handler.ts
- Repo-aware AI points at the files most likely involved.
- Replies sync both ways, so reporters answer by email, no account.
- The original submission stays linked for when you need it.
Built to disappear into your workflow.
Repo-aware AI
Reads your README, languages, and file tree to point at the files most likely involved. It only reads your README, topics, and file paths, never your file contents.
Replies sync both ways
You comment in GitHub; reporters reply by email or status page. No account, and nothing falls through the cracks.
Nothing new to adopt
GitHub stays your single source of truth. Flunes only improves what enters it, there's no second tracker to learn.
Duplicate detectionPRO
Near-identical reports get flagged before they clutter your repo, with a similarity score you can act on.
Your brand on the form
Collaborators see your name and logo on a focused intake page, not a generic third-party widget.
Private by default
Each reporter gets their own link and history. Screenshots stay scoped to the submission they belong to.
Other tools collect feedback. Flunes routes it where you work.
Priced on repos and AI volume, never per reporter.
Priced on your repos and AI volume, never per reporter. Every plan includes unlimited collaborators.
- 1 repo
- 5 AI-structured submissions / mo
- 1 screenshot per submission
- Unlimited collaborators
- 2 repos
- 50 AI-structured submissions / mo
- Up to 5 screenshots
- Digest emails & Slack
- 5 repos
- 250 AI-structured submissions / mo
- Duplicate detection
- Custom fields & AI template
- Up to 25 screenshots
Questions, answered.
No. Collaborators submit through a unique link, no GitHub account, no password, no email verification. You sign in with GitHub; they never have to.
Give outside feedback a proper front door.
Connect one repo, share one link, and let GitHub start receiving clean issues automatically.
Free forever on 1 repo · No credit card required