A Hacker News thread flagged last week describes one developer's attempt to have Claude locate and complete paid open-source bounties. The post earned 32 points and drew 16 comments focused on automation limits and payout realism.
The Experiment Setup
The author built a lightweight scout script that pulled active bounties from Algora and fed task descriptions plus repository context into Claude 3.5 Sonnet. Claude was instructed to analyze requirements, propose a fix plan, and generate the code patch in one pass.
The workflow ran daily for two weeks. Each bounty received a structured prompt containing issue text, linked files, and success criteria pulled from the platform.
Results and Numbers
Claude identified 14 viable bounties above $150. It produced working patches for 6 of them. Two patches were merged and paid out, returning roughly $420 in total earnings after platform fees.
Manual scouting by the same developer over the prior month had surfaced only 9 bounties and yielded one successful payout of $180. The AI-assisted run increased bounty discovery rate by 55 % and doubled successful completions.
How to Try It
Clone the scout repository and set your Anthropic API key. Run the daily scan with this command:
python scout.py --min-bounty 100 --model claude-3-5-sonnet
Edit the system prompt in prompts/bounty.md to add your preferred languages and frameworks. Review generated patches before submitting to keep acceptance rates high.
Pros and Cons
- Pros: 3–4× faster triage than manual browsing; consistent patch structure; works well on well-scoped issues under 300 lines.
- Cons: Struggles with large refactors or undocumented APIs; occasional hallucinated dependencies; still requires human review for merge readiness.
Early HN comments noted the same pattern: Claude excels at narrow fixes but needs guardrails on scope.
Alternatives and Comparisons
| Tool | Discovery Speed | Patch Quality | Cost per Bounty | Best For |
|---|---|---|---|---|
| Claude 3.5 Sonnet | High | Good | $0.03–0.08 | Small scoped fixes |
| GPT-4o | Medium | Very Good | $0.05–0.12 | Complex reasoning tasks |
| Manual search | Low | High | $0 | Projects you already know |
Developers report GPT-4o produces slightly cleaner large diffs, while Claude remains the fastest at initial filtering.
Who Should Use This
Use the approach if you already maintain 2–3 open-source repositories and can review patches quickly. Skip it if you lack merge rights or target only high-value, multi-week bounties that exceed current model context windows.
Bottom Line / Verdict
Claude currently functions as a high-speed bounty filter that raises completion rate for small-to-medium issues, provided a human stays in the loop for final validation.
The same pattern will likely improve as context windows and tool-use reliability increase over the next two model generations.
Top comments (0)