Individual org bounty pages (e.g., /ZIO/bounties, /tscircuit/bounties) display bounties as "open" with "0 claims" when in reality
the linked GitHub issues have been closed, PRs have been merged, or multiple /claim commands have already been posted.

The main https://algora.io/bounties page appears to work correctly - this bug is specific to the per-org bounty listings.

Examples

tscircuit (/tscircuit/bounties)

Bounty	Algora Shows	GitHub Reality
Texture Support (pcb-viewer#419) - $150	0 claims, Open	Issue CLOSED on GitHub
Kicad courtyards (tscircuit#1081) - $75	0 claims, Open	10+ competing PRs, 3 already merged in kicad-component-converter (#192, #193, #194), multiple /claim comments posted
QFN32 (footprinter#386) - $25	0 claims, Open	Issue CLOSED on GitHub
Reference designators (tscircuit#939) - $50	0 claims, Open	Issue CLOSED on GitHub

ZIO (/ZIO/bounties)

Bounty	Algora Shows	GitHub Reality
ZScheduler (zio#9878) - $850	5 claims, Open	jdegoes explicitly wrote: /bounty $850 (maintainers only). External contributors told to stay away.
Fiber/Promise (zio#9877) - $750	5 claims, Open	jdegoes explicitly wrote: /bounty $750 (maintainers only)

deskflow (/deskflow/bounties)

Maintainers added a warning directly in the GitHub issue: "We are NOT accepting bounties on this PR. We tried removing the bounty on
Algora.io, but their app is buggy and errors when we try to delete the bounty."

Screenshots

The above image issue is open with a bounty but in github it says closed.

Impact

1. Contributors waste time - someone sees "0 claims" on a $150 bounty, starts working, only to discover the issue is already closed
   on GitHub
2. Claim counts are wrong - bounties with multiple /claim comments on GitHub show "0 claims" on Algora
3. Maintainers can't clean up - deskflow confirmed the delete bounty feature errors out
4. Misleading signal - "0 claims" is actively misleading when there are actually 10+ competing PRs

Root Causes

1. No sync between GitHub issue state and Algora bounty state - closing an issue on GitHub doesn't update the bounty on Algora
2. /claim commands on GitHub not reflected in claim counts - the "0 claims" badge is stale or not parsing GitHub comments
3. Delete bounty regression — the feature shipped in PR feat: in-app bounty edit & delete #159 (July 2025) but deskflow maintainers report it errors out

Suggested Fix

• Sync GitHub issue open/closed state → auto-close bounty when issue is closed
• Parse /claim and /attempt comments from GitHub → update claim count in real-time
• Fix the delete bounty feature regression (reported by deskflow maintainers)
• Show a visual indicator (badge/label) when the linked GitHub issue is closed

Related Issues

• A lot of projects are spamming bounties without paying or even answering #174 — "A lot of projects are spamming bounties without paying or even answering"
• Feature Request: Cancel Bounty #178 — "Feature Request: Cancel Bounty" — the current delete implementation appears broken
• Confusing/incorrect number of bounties per prog. language #173 — "Confusing/incorrect number of bounties per prog. language" - likely a downstream symptom of the same stale data
• UI Bug: “Edit Amount” and “Delete” buttons are visible to non-owners on Algora individual organization's bounty page #179 — "Edit Amount and Delete buttons visible to non-owners" - compounds the problem since non-owners see controls for stale bounties they can't even manage

---