____ _ ____ _ _ ___
/ ___(_)_ _____| __ ) __ _ ___| | __ / \ |_ _|
| | _| \ \ / / _ \ _ \ / _` |/ __| |/ // _ \ | |
| |_| | |\ V / __/ |_) | (_| | (__| </ ___ \ | |
\____|_| \_/ \___|____/ \__,_|\___|_|\_\_/ \_\___|
Donate your unused Claude quota to open source.
Many Claude Max and Pro subscribers don't use their full quota before it resets. GiveBackAI lets you turn that idle capacity into real contributions to open-source projects and nonprofits — by pasting a single prompt into Claude Code.
The system is fully serverless. There is no GiveBackAI backend collecting your data. Your Claude session runs against a hosted instructions file, browses a public list of opted-in partner repos, picks an open issue you approve, and opens a pull request — all under your own GitHub account.
→ orzelig.github.io/givebackai — paste the prompt and start contributing.
You Claude Code GitHub
│ │ │
│ paste 3-line prompt │ │
├────────────────────►│ │
│ │ fetch run.md │
│ ├────────────────────►│
│ │◄────────────────────┤
│ │ find ready issues │
│ ├────────────────────►│
│ │◄────────────────────┤
│ here are 3 tasks │ │
│◄────────────────────┤ │
│ pick one │ │
├────────────────────►│ │
│ │ fork → commit → PR │
│ ├────────────────────►│
▼ ▼ ▼
That's the whole loop. The PR opens under your GitHub handle, with a footer crediting you and linking back to GiveBackAI. There is no signup, no token to store, no central server.
- Go to orzelig.github.io/givebackai and copy the prompt.
- Paste it into Claude Code (CLI or
claude.ai/codein the browser). - Make sure
ghis authenticated (gh auth status) and you have time for one task (~30–45 min). - Follow along — Claude will confirm with you before any destructive action.
Full guide: docs-src/contributor-guide.md.
You GitHub
│ │
│ label "givebackai-ready" on issues │
├────────────────────────────────────────►│
│ │
│ open PR to partners.yaml │
├────────────────────────────────────────►│
│ │
│ comment "/givebackai-confirm" │
├────────────────────────────────────────►│
▼ ▼
The /givebackai-confirm comment must come from an account with admin or maintain permission on your repo — a GitHub Action verifies and auto-merges. An entry in partners.yaml is six lines:
- owner: your-org
repo: your-repo
label: givebackai-ready
category: oss # oss | nonprofit | research
contact: maintainer@example.com
description: One sentence about your project.Full guide: docs-src/partner-guide.md.
Everything is on GitHub. There is no application server.
- This repo hosts
run.md(the instructions Claude follows) andpartners.yaml(the source of truth for opted-in repos), both served atorzelig.github.io/givebackaivia GitHub Pages. - Tasks are GitHub issues in partner repos with the
givebackai-readylabel. - Soft-locking uses GitHub's native issue
assigneesfield. A daily GitHub Action sweeps assignments that have been held >24h with no linked PR. - The contributor dashboard at
orzelig.github.io/givebackai/u/<handle>is a static page that calls the GitHub Search API client-side.
See the plan for the full architectural reasoning.
You don't need to trust GiveBackAI with anything sensitive. The flow runs entirely on your machine, under your GitHub identity. The only data that leaves your session is GitHub API calls that your own gh is making. There is no GiveBackAI server. The run.md you fetch is a public file in this repo, and its hash is published alongside it at run.md.sha256 for byte-for-byte verification.
MIT.