Cute! Cactus for me. Nice animations too - looks like there were multiple of us asking Claude to reverse engineer the system. I did a slightly deeper dive here if you're interested, plus you can see all the options available: https://variety.is/posts/claude-code-buddies/
(I didn't think to include a UUID checker though - nice touch)
Neat! That's a great write up, cool to see others looking into it.
I do wonder if they're going to do anything with the stats and shinies bit. Seems like the main piece of code for buddies that's going to handle hatching them tomorrow is still missing (comments mention a missing /buddy/index file), so maybe it'll use them there.
I've posted here before about Claude Code's easter eggs [1] and they're back with another one this year for April Fools: Tamagotchi-style "buddies" appearing as ASCII art companions, determined by your userId.
Thanks to the Claude Code source code leak I was able to reverse engineer how it all works. Due to their PRNG choice (Mulberry32) it's trivial to crack all 4.29 billion seeds in seconds.
Some findings:
- 1% legendary chance: 42,989,564 seeds out of 2^32 produce legendaries
- Stats & shiny appear to be dead code: rolled but never read anywhere. Pure bragging rights?
- Commons can't have hats, only uncommon+ rolls from the hat table
- "God" rolls exist: legendary + shiny + a maxed stat at 100.
No wonder they don't publish an availability percentage. If I was a business customer paying for GitHub I would be very upset with the availability lately.
Someone built an archive of Github statuses to show aggregate uptime, last month and this month Github's uptime is below 90%, not even one "nine" of availability: https://mrshu.github.io/github-statuses/
87% uptime for Github in February 2026. They've got to get it together.
Did gemini-2.5-flash-image get an upgrade as well? I just got the following, which is fascinating, and not something I've seen before:
> I'm sorry, but I cannot fulfill your request as it contains conflicting instructions. You asked me to include the self-carved markings on the character's right wrist and to show him clutching his electromancy focus, but you also explicitly stated, "Do NOT include any props, weapons, or objects in the character's hands - hands should be empty." This contradiction prevents me from generating the image as requested.
My prompts are automated (e.g. I'm not writing them) and definitely have contained conflicting instructions in the past.
A quick google search on that error doesn't reveal anything either
Most production software is wrappers around existing libraries. The relevant question is whether this wrapper adds operational or usability value, not whether it reimplements OCR. If there are architectural or reliability concerns, it’d be more useful to call those out directly.
reply