When should you use it?
- Small tasks need your context but never get done
- You rarely use your full subscription
- You review work as PRs
Not for: Work that cannot go through PRs; Repos with no tests
What do you need, and what do you get?
You need
- Goals file
- Task list sources
- Git and agent CLIs signed in
You get
- Small PRs ready for review
- Merge decisions that guide next picks
- Quota-aware schedule
How does it work, step by step?
- Write goalsList your goals in a file the bot reads.
- Connect tasksPoint it at your task lists.
- Run smallStart with a short deadline and small task size.
- ScheduleRun it on a timer that checks quota and time to reset.
- Review PRsMerge or close; your choices steer future tasks.
The prompt
Our own prompt, inspired by ariwilson on Hacker News and written to work in Claude Code and Custom agent. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Read {goals_file} and {task_list}. Pick one small task that moves a goal forward and can be done in about {minutes} minutes. Work on a new branch, open a PR describing what you did and what you did not do, and stop. Do not merge, deploy or touch secrets.
Inspired by ariwilson on Hacker News: Comment in Show HN: RemainderBot – spends leftover Claude/Codex quota on reviewable PRs. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Check your plan's terms for automated use.
- PRs pile up if you do not review them.
- Keep it away from secrets and production deploys.
Our take
The framing is what makes RemainderBot interesting: subscription capacity that would expire unused becomes a queue of small, optional pull requests. Using a PR as the unit of output keeps the founder in charge, since each result is a diff to merge or close, and those choices become feedback about what is actually useful. ariwilson's range of tasks, from meeting prep notes to prototypes, also shows that a repository can hold more than code; documents and briefs work fine as PRs. Before copying the idea, read your plan's terms on automated or scheduled use, since consumer subscriptions often differ from API access. Keep tasks small enough that each review takes a few minutes, otherwise the backlog of unreviewed PRs becomes its own chore. Point the bot only at repositories where a bad change is harmless until merged, and never at branches that deploy automatically. Writing the goals file is worthwhile even without the bot; a clear list of what you are trying to achieve improves every task you hand to any agent.
Where the time goes back: Unused subscription capacity turns into small finished tasks waiting for a yes.
FAQ
How much quota does it use?
Does it learn?
Source and credit
Inspired by ariwilson on Hacker News. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Comment in Show HN: RemainderBot – spends leftover Claude/Codex quota on reviewable PRs
- Creator
- ariwilson on Hacker News
- Published on
- Hacker News
- Original date
- Oct 13, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Custom agent
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends, bookings or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.