← Back to library

Unused subscription tokens become small PRs to review

ariwilson, founder of Bakeoff, built RemainderBot, which reads written goals and task lists and spends unused Claude and Codex subscription capacity on pull requests. On a schedule it weighs remaining quota against days until renewal and picks a task. It has opened 111 PRs, from meeting prep to prototypes, learning from which ones get merged.

  • OutcomeLet a scheduled bot check your remaining subscription quota before the weekly reset and use it to open small PRs toward the goals and to-dos you list.
  • SetupUnder an hour
  • LevelIntermediate
  • Creditariwilson on Hacker News
View original
Works with
Claude CodeCustom agent

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 23, 2026

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?

  1. Write goalsList your goals in a file the bot reads.
  2. Connect tasksPoint it at your task lists.
  3. Run smallStart with a short deadline and small task size.
  4. ScheduleRun it on a timer that checks quota and time to reset.
  5. 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)

Prompt3 variables
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?
Each run uses a small slice of the weekly allowance, per the author.
Does it learn?
Your review comments and merge choices steer which tasks it picks later.

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.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminWorkflow✓ AI dry run

Add a merge check for every way coding agents break code

Keep a running list of the specific ways coding agents have damaged your repository, from hollow tests and invented fake responses to deleted files and silenced type errors, and turn each one into an automated gate that blocks the merge, so the same mistake cannot slip through review twice.

Credit: u/alexmarquardt on r/ClaudeCode

An afternoon+
Operations & AdminRoutine✓ AI dry run

Draft a weekly recap post from your GitHub activity

Start Monday with a ready draft of what you shipped last week, plus a stats page, instead of trying to remember.

Credit: Yash Kumar Saini

An afternoon+
Operations & AdminPrompt✓ AI dry run

Give your agents one shared wiki that only one agent edits

Replace scattered agent memories with a single Markdown wiki in git: every agent reads a short daily brief from it, agents and scripts file sourced notes into an inbox instead of editing pages, one steward agent checks and merges those notes each morning, and private agent memory keeps only personal preferences.

Credit: Siim Tolk

An afternoon+
Operations & AdminWorkflow✓ AI dry run

Get agent-written browser tests that survive CI

Get a Playwright test written by Claude Code against your running app, reviewed twice, repeated to catch flakiness and committed beside its plain-English scenario.

Credit: Jakob Norlin

Under an hour