ariwilson
Especially since they're not like a regular server, loud and power hungry. They're the definition of quiet and power sipping. I have one do all my background coding work when I want to keep my laptop clear (being headless helps with me moving around too).
When I dug into it, I realized that the models shipped at different default effort levels. That seems confusing to users - I wonder why the labs do this. I was surprised to see that increasing the thinking level often didn’t improve correctness and almost always increased (non-test) diff size. I was less surprised that Fable at high and Opus at max did poorly.
Ask me any questions you have; happy to share specific differences I noticed between solutions. What effort level are you running at and why?
Familiarity breeds contempt.
It thinks a ton, ~24k output tokens a run vs ~3k for Sonnet. It missed a solution by thinking its way into a 10 min timeoout.
Something to look out for - if you're using pi, it doesn't have Argon in its catalog yet and reports cost at Kimi's rates, about a third of what OpenRouter actually bills.
As the founder of Bakeoff, I spend my time on customer development and engineering architecture & review. RemainderBot solves two problems for me and I suspect for many others out there:
* There are many small tasks that require a few minutes of my time and need my context, but I just don’t have the mental energy to prioritize them, do a context shift, perform a small amount of work, and finalize the results a dozen times a day.
* Some weeks I don’t get close to my Claude and Codex subscription limits. That’s a waste of what are very valuable Astra and Opus 5.5 tokens :)!
RemainderBot has consistently used my goals and task lists to identify non-obvious tasks that would move me forward. It has accomplished quite a bit - 111 PRs including customer call prep, a census of 31 GitHub orgs’ agent setup files, and standalone prototypes to demo to engineers I meet with.
You interact with it in whatever interface you use with GitHub PRs. It uses your comments and decisions on whether to merge PRs to guide which kinds of tasks and approaches it takes in the future.
RemainderBot runs either as a manual process on your machine or as a cronjob on a server. In tick (cronjob) mode, it checks how much subscription quota is left and how much time there is until the weekly reset before picking a task and creating a PR.
Here’s how you get started:
* Check that git, claude (or codex), and gh CLIs exist and are authenticated on your machine
* Clone the openremainderbot repo:
git clone https://github.com/arimwilson/openremainderbot.git remainderbot
cd remainderbot
cp -n GOALS.example.md GOALS.md
cp -n sources.example.toml sources.toml
Edit those two files with your personal goals and with sources for your task lists, respectively. Finally: python3 -m remainderbot snapshot
python3 -m remainderbot run --provider claude --deadline-minutes 20 --size small
These commands will pick a task, work on it in a new branch, and will cost you a few percent of your weekly quota. Please drop a comment on what it did for you and if it got anything wrong here or in https://github.com/arimwilson/openremainderbot/discussions/6 :).More details in the blog post - https://www.ariwilson.com/writing/openremainderbot
Hope you enjoy it!
Show HN: RemainderBot – spends leftover Claude/Codex quota on reviewable PRs
Show HN: RemainderBot - spends leftover Claude/Codex quota on reviewable PRs
Just compare how much better presented the Astra announcement was compared to this one: https://openai.com/index/gpt-6-astra/
"The end result is a memory-safe video decoder that runs 2.7x faster than the Rust port, with identical video output, bringing it closer to the optimized C++."
Close but no cigar!
* 5.5x faster
* 4x cheaper due to using fewer tokens
* 1/3 the turns: batched reads, one-script edits & tests in the same call