Codex Pets vs Claude Code Buddy: Complete Comparison (2026)

Codex Pets vs Claude Code Buddy is now a real question developers ask when picking an AI coding CLI. In May 2026, OpenAI rolled out Codex Pets — animated companions that float over your editor and surface what the Codex agent is doing in real time. A few months earlier, Anthropic quietly removed Claude Code Buddy in version 2.1.97 and pivoted that surface area into the new /powerup command.

On the surface they look like the same idea: a small creature that lives in your terminal and reacts to your AI assistant. Underneath, they answer different questions. Codex Pets is a status layer — a always-visible window into agent state. Claude Buddy was a identity artifact — a deterministic, lifelong companion derived from your account UUID.

This guide compares both systems feature by feature, explains why they took such different paths, and gives you a concrete migration plan if you used Claude Buddy and now want a Codex Pet (or want to stay in the Claude Code ecosystem with /powerup instead).

If you only read one section, read this table. Everything below is detail.

Dimension	Codex Pets	Claude Code Buddy
Status	Live (May 2026)	Retired in v2.1.97 — replaced by /powerup
Vendor	OpenAI	Anthropic
Spawn command	/pet and /hatch	/buddy (no longer available)
Pet identity	You pick from 8 built-ins or generate via AI	Deterministic from your accountUuid — no choice
Built-in pets	8 (Codex, Dewey, Rocky, etc.)	18 species × 5 rarity tiers
Customization	/hatch generates pets from a prompt	None — your buddy is fixed
Surface	Floating overlay window	Inline ASCII art in the CLI
State signaling	Yes — red clock, green check, thought bubbles	No — buddy was decorative
Cross-platform	macOS + Windows	Anywhere Claude Code ran
Third-party ecosystem	Petdex (467+ pets), Codex Pet Share	Community tools, claudebuddy.art
Emotional weight	Low — pets are interchangeable	High — your buddy is irreplaceable

The matrix already tells most of the story: Codex Pets optimizes for utility and choice, Claude Buddy optimized for identity and permanence. Neither approach is wrong; they serve different jobs.

Codex Pets ships inside the Codex desktop app on macOS and Windows. After updating, type /pet in the prompt and a small animated companion spawns into a floating window that hovers above your editor. There are eight built-in designs to choose from, each with a distinct personality and visual style.

The /pet Command

Running /pet opens a picker with all eight built-ins. The default is a blue creature also named Codex. Other options include Dewey (a duck-shaped companion) and Rocky. You can switch pets at any time without losing state.

The /hatch Command

If none of the eight built-ins fit your vibe, type /hatch followed by a prompt and the model will generate a custom pet on the fly. This is the killer feature: every developer can have a unique companion, but unlike Claude Buddy, the uniqueness comes from your imagination, not from a hash of your account ID.

Status Signaling

The pet is not just decorative. Its thought bubble communicates agent state in real time:

• Red clock face — the agent is paused, waiting for your approval before running a command
• Green checkmark — the agent finished a task and is ready for a new prompt
• Active thread display — shows which conversation the agent is currently working on

This solves a real workflow problem. Codex agents can run for minutes on a single task, and developers were tab-switching constantly to check progress. The pet keeps that information glanceable.

Claude Code Buddy worked very differently. It launched as a hidden Tamagotchi-style feature inside Claude Code and was tied to your accountUuid via a deterministic pipeline:

1. Your UUID was concatenated with the salt friend-2026-401
2. The combined string was hashed with FNV-1a to a 32-bit integer
3. That integer seeded a Mulberry32 PRNG
4. The PRNG sequentially picked rarity, species, eyes, hat, shiny status, and 5 stats

The system included 18 species (Duck, Dragon, Owl, Octopus, and 14 more), 5 rarity tiers (Common 60%, Uncommon 25%, Rare 10%, Epic 4%, Legendary 1%), an independent 1% Shiny chance, and a 5-stat personality system. Combined odds for a Legendary Shiny of any species: 1 in 10,000.

The killer property: same UUID, same buddy, every time. Forever. Two developers could compare buddies the way trading-card collectors compared cards. Your buddy was as much a part of your developer identity as your GitHub avatar.

Why It Was Retired

In v2.1.97, Anthropic removed the /buddy command entirely and routed its surface area into /powerup — a productivity-focused feature that tracks shipped features rather than displays a pet. The community took it hard. See our post on the v2.1.97 great vanishing for the full timeline.

What Survives

The algorithm is deterministic and the source code leaked, so the buddy computation survives even though the feature does not. That is what claudebuddy.art is: a faithful reimplementation of the original algorithm. Paste your UUID, get the buddy you would have had. Browse all 18 species at /species. The bodies are eternal even when the runtime is gone.

Both systems grew third-party ecosystems, but they serve different needs.

Petdex: Codex's Killer Advantage

Petdex (petdex.crafter.run) is a community catalog of 467+ open-source Codex companions. Anyone can publish a pet, and installation is one command:

npx petdex install <pet-name>COPY

The catalog ranges from a Super Saiyan Blue Goku-style companion to a monochrome detective spider in a fedora to a Game & Watch–style pixel pet. There is also Codex Pet Share, an alternative gallery focused on shareable companion designs.

The implication for the ecosystem: Codex Pets has near-zero friction for new content. If you can imagine a pet, you can build it, publish it, and have it spread through npm in an afternoon. This is closer to the VS Code extension marketplace than to Tamagotchi.

Claude Buddy Checker

The Claude Buddy ecosystem evolved differently — toward archival and identity, not customization. claudebuddy.art exists because users wanted to keep finding out what their buddy was, even after the official feature went away. Tools like the MCP-based revive tool aim to restore the runtime experience.

The contrast is sharp: Petdex grew because Codex Pets is meant to be customized; the Buddy Checker grew because Claude Buddy was meant to be permanent and was lost.

If you used Claude Code Buddy and are now switching to Codex (or running both), here is the practical migration path.

Step 1: Record What You Had

Before doing anything else, paste your old accountUuid into claudebuddy.art and screenshot the result. Your buddy's species, rarity, stats, and any name you gave it locally are part of your developer history. Save them to a personal README, dotfiles repo, or private gist.

Step 2: Decide What You Want From a Pet

Codex Pets and Claude Buddy answered different questions:

• Want agent state at a glance? Codex Pets is the right tool. /pet in Codex, pick a built-in, done.
• Want a unique creature that is yours and only yours? Use /hatch with a prompt that means something to you. Save the prompt — it is the closest analogue to a deterministic UUID.
• Want to keep the Claude Code ecosystem and skip Codex entirely? Use /powerup for productivity tracking, and let claudebuddy.art be your buddy archive.

Step 3: Install One or Two Petdex Pets

Even after picking a built-in, browse Petdex. The community pets are surprisingly good and they signal something about your taste the way a desktop wallpaper does.

Step 4: Do Not Try to Recreate Your Old Buddy

It is tempting to /hatch a pet that looks exactly like your old Legendary Shiny Dragon. Resist. Codex Pets is not the same medium. Trying to copy a buddy makes the new pet feel like a counterfeit. Use the migration as a chance to pick something new.

Is Codex Pets free?

Yes. Codex Pets ships with the Codex app at no extra cost on both macOS and Windows. Petdex pets are open source and free to install via npx petdex install.

Can I get my Claude Code Buddy back?

Not in the official Claude Code runtime — /buddy was removed in v2.1.97 and has not returned. You can still view your buddy at claudebuddy.art using your accountUuid, and community projects like the MCP-based revive tool reimplement the experience outside the official client.

Are Codex Pets deterministic like Claude Buddy was?

No. Codex Pets are user-chosen (or AI-generated via /hatch). There is no algorithm that maps your account ID to a specific pet. This is a deliberate design choice — Codex Pets prioritizes customization, Claude Buddy prioritized permanence.

Which pet system is better for productivity?

Codex Pets, by a wide margin. The status overlay (red clock, green check, active thread) gives you real workflow information. Claude Buddy was charming but purely decorative. If your goal is shipping code faster, the Codex pet is doing real work.

Can I use Codex Pets and Claude Code together?

Yes. They run in different processes and do not conflict. Many developers use Claude Code for one project type and Codex for another, and the Codex pet only renders when the Codex app is in focus.

What happens if I switch built-in pets in Codex?

State persists across pet swaps. The pet is a skin over the same agent activity feed, so changing from Dewey to Rocky does not reset anything. Petdex pets behave the same way.

Will Anthropic bring Buddy back?

No public statement either way. The pivot to /powerup suggests the decision was strategic, not temporary. If you want a pet inside Claude Code, your realistic options are the community MCP revive tool or — honestly — using Codex for the pet experience.

Want to see what Buddy you would have had? Try the Claude Buddy Checker. Browse the full species catalog. Track your shipped features with /powerup.