One pet per primary action

INSTALL ONLY WHAT YOU CHOOSE.

Free, unofficial animated pets for the Codex desktop app—not standalone mobile apps. Choose a released pet; every route installs only that Part-scoped pet.

Choose a pet and install ↓

36 validated pets are live

Choose your companion.

The selection below controls the one primary Codex action and its verified fallback installers.

PART 01Jonathan Joestar, Part 1 pixel Codex petJonathan Joestar

Current selectionJonathan Joestarpart-01-jonathan-joestar

01 Open in Codex

Requires the Codex desktop app with Pets support. If the codex:// link does not open, use Other install methods below.

Open in Codex ↗

After install open Codex Settings > Pets, select Refresh, then choose the pet.

Other install methods
02

Bash

macOS and Linux installer with SHA-256 and manifest validation.

curl -fsSL https://pixelstand.pet/install.sh | bash -s -- part-01-jonathan-joestar
03

PowerShell

Windows installer with the same package integrity checks.

& ([scriptblock]::Create((irm https://pixelstand.pet/install.ps1))) part-01-jonathan-joestar
04

npx

Cross-platform Node installer using the selected Part-scoped pet ID.

npx --yes --package=github:geoqiao/jojo-codex-pet jojo-codex-pet part-01-jonathan-joestar

We count anonymous aggregate command-copy and Open in Codex actions. These totals show install intent—not completed installations or identifiable visitors.

Browse every released pet

Each detail page includes the same pet-specific Codex deep link and verified command installers.

Before you install

Install FAQ

Which method should I use?

Use Open in Codex when your browser can hand the deep link to Codex. Bash is for macOS or Linux, PowerShell is for Windows, and npx works anywhere a current Node.js runtime is available.

Where do command installers put the pet?

They write the selected runtime package to $CODEX_HOME/pets/<pet-id>. Without CODEX_HOME, the default is ~/.codex/pets/<pet-id>.

How does Codex discover it?

After a command finishes, open Codex Settings → Pets, choose Refresh, then select the installed pet.

What gets verified?

Bash, PowerShell, and npx download the checksum list, pet.json, and spritesheet, then verify SHA-256 plus the manifest ID and V2 contract before replacing runtime files.

What happens if I install the same pet again?

A command installer refreshes the files under the same stable pet ID after validation. It does not create a duplicate or add another pet.