SShortSingh.
Back to feed

Fan-made checker shows how a Claude Code buddy pet is derived from account ID

0
·2 views

A community-built site called Claude Buddy Community Hub offers a checker for the /buddy pet in Claude Code, where the pet is derived deterministically from the user's account UUID. The result is produced by hashing the UUID with a salt and feeding it into a pseudo-random generator that sets species, rarity, eyes, hat and stats. The checker lets users choose between Node.js (FNV-1a) hashing, available now, and Bun (wyhash), listed as coming soon, since different hash functions yield different pets. Rarity tiers run from Common at 60% down to Legendary at 1%, and the site illustrates that a Legendary of one specific species with Shiny status is about 0.0006%. Mismatches are usually caused by using the wrong ID field from the config file or by a local salt change, and the site is not affiliated with the official project.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Handoff checklist for Unreal teams split across India and Europe or the US

Unreal Engine teams with members in India and in Europe or North America rely on the nightly build as their main point of coordination. The article recommends agreeing on a single build cut-off time, written in both local time zones, and reviewing it when daylight saving changes shift the gap. Builds should come from the CI machine with matching engine versions, and the build should be split into stages that each report results to a shared channel. Teams are also advised to post a short end-of-day summary and to use exclusive checkout for binary Unreal assets, which cannot be merged. Finally, it suggests regional sync proxies and resumable uploads to cope with slow or unstable home connections.

0
ProgrammingDEV Community ·

Keeping AI-Generated Report Images Consistent Through Upload Retries

The article argues that generated report images should live in private object storage, with generation and upload treated as separate queue states. Generated bytes are persisted before upload, so a throttled upload can be retried without re-rendering a different artifact. A 429 response is retried with bounded backoff, honoring Retry-After when present, and the object key is derived from the job ID so retries never create duplicates. The author notes that idempotent naming does not replace mutual exclusion, so the database or queue must serialize workers writing to the same key. The piece also recommends testing the retry policy with synthetic 429 injections in an environment eligible for persistent writes, and recording traces rather than fabricated results.

0
ProgrammingDEV Community ·

Control experiment exposes flaw in AI security reviewer benchmark

A developer's earlier test showed a security agent catching all ten reverted CVE fix commits, but a reader argued it might simply flag removed code guards. To check, the author ran the same agent on ten non-security control commits with comparable diff sizes. The controls were imperfectly matched, with several drawn from different years and some consisting mostly of documentation changes. The agent produced no comments on seven controls, commented on three, and all three of those comments were judged noise. The author also disclosed that one case required a third attempt after provider timeouts, rather than presenting the runs as perfectly clean.

0
ProgrammingDEV Community ·

Structured LLM output: Ask for typed Go or Rust structs, not prose

Parsing free-form LLM prose with regular expressions is fragile, since the model's phrasing shifts between runs and breaks string matching. The article proposes requesting a typed value instead, using a Go struct with fields such as severity and fix via an Ask method. The framework derives a JSON Schema from that type and sends it to the model as the required response format, then unmarshals the reply directly into the struct. Deriving the schema from the type keeps the instructions and the parsed type from drifting apart. In the Rust sibling framework, responses are additionally validated against the schema before deserialisation, so malformed output produces a distinct, specific error.