Codex Pet ZIP Package
See the pet, product surface, and environment currently held in the browser.
Choose a downloadable pet to reveal its pinned one-line npx installer in the first screen. The installer verifies pet.json and spritesheet.webp before writing the local pet folder. Desktop and Codex CLI use the command; ChatGPT Web uses the transparent WebP when Upload pet is available. ZIP, checksums, and manual scripts remain available as fallbacks.
LOCAL TOOLUse the first control. No sample output is presented as evidence.
Select a published pet and target. The page pins its installer version and pet ID, then keeps manual files, checksums, activation, and rollback nearby. This guide covers versioned community packages from this site. OpenAI's built-in Create your own pet workflow is separate, and account availability is never assumed.
The workspace reports the selection, current local result, source category, and remaining limitation without presenting an empty field as proof.
See the pet, product surface, and environment currently held in the browser.
Read one conclusion from the visible inputs.
See which record or test remains missing.


This tool handles one page decision, keeps processing local, and exposes evidence limits, next links, and corrections.
Copy a command that fixes both the installer version and the selected pet ID.
The installer checks exact byte sizes and SHA-256 before it creates the pet folder.
Use ZIP for a manual local install or direct WebP for ChatGPT Web.
Preserve an existing pet folder, activate the new pet, and keep a clear reversal path.
Desktop, Web, CLI, and IDE create different evidence needs for this package-specific setup plan. Product facts below were checked on 2026-07-26.
Name the intended product and environment before relying on a result.
| Context | Evidence and limitation |
|---|---|
| ChatGPT Desktop | Copy the pinned npx command, let the installer verify both files, then refresh Pets and select the installed companion. |
| ChatGPT Web | Download the transparent 1536×1872 WebP and use Upload pet only when the feature is available for the current account and workspace. |
| Codex CLI | Run the pinned npx command, then open /pets in iTerm2 3.6+, Kitty graphics, or a Sixel-capable terminal; tmux and Zellij are unsupported. |
| IDE extension | Current official guidance provides no pet picker or floating overlay in the IDE extension, so this page does not present it as an install target. |
Preserve the original input and current environment before changing a file, setting, or install state. Make one observable change at a time and record the result before continuing.
Keep diagnosis, implementation, verification, and correction as separate stages.
Open a pet detail page to confirm the character and its nine animation rows.
Use the one-line installer for Desktop or CLI, or choose the direct WebP for ChatGPT Web.
Let the CLI verify both files before writing, or check SHA-256 when using a manual fallback.
Activate the pet in the intended product and restore the backup if the result is not correct.
Official facts, community profiles, tests, and unknown claims stay separate.
This evidence track cites the strongest source and leaves missing facts visible.
Use current first-party Pets guidance for product behavior and workflow facts.
Read current sourceName the non-official format source, version, and checked date.
codex pet formatRecord a reproducible environment, method, outcome, and limitation.
codex pet compatibilityRoute missing, stale, or contested evidence to verification and contact.
contact codex petsThese visible answers describe current behavior and limits; no FAQ structured data or search appearance is promised.
Choose a pet, copy its pinned npx command, run it in a supported local environment, then refresh and select the installed pet. Use the manual files only when needed.
Use the ZIP only as a manual Desktop or CLI fallback. Use the direct transparent WebP for ChatGPT Web Upload pet when that feature is available.
Each release ZIP contains one pet-ID folder with pet.json and spritesheet.webp. The current 1.0.0 downloads use the legacy v1-compatible 8×9 atlas.
The local contract uses ${CODEX_HOME:-$HOME/.codex}/pets/<pet-id>/. Windows and WSL have separate home directories, so confirm which product reads the folder.
Confirm the intended surface, refresh Pets on Desktop or open /pets in CLI, and verify that the package folder and selected environment match the plan.
Current official guidance says tmux and Zellij are unsupported for pet rendering. Use iTerm2 3.6+, Kitty graphics, or Sixel in the CLI path.
No. hatch-pet is the built-in creation workflow. This page guides an existing downloadable community package without claiming that it created a new pet.
No. SHA-256 proves byte identity only. You must still refresh, select, and observe the pet in the intended product.
Every link reaches a real P0 route with descriptive anchor text and a matching intent.
Return to the first control, add only the pet, product surface, and environment, and compare the installation plan with its limit.