What Can a Codex Pet Do? All 9 States Explained
2026-09-04
A Codex pet is a small animated companion that lives on your desktop. What it actually does, the nine animation states, and the limits worth knowing before you generate one.
The short answer
A Codex pet is a small animated pixel-art companion that lives on your desktop while you work. It is generated from a photo you upload, rendered as a spritesheet, and installed into a directory the Codex desktop app reads at startup.
It is cosmetic by design. It does not read your code, respond to commands, or surface notifications — it sits somewhere on screen and quietly animates. For most people that is the entire appeal: something familiar in the corner while you work.
The nine animation states
A standard pet ships with nine states, each an eight-frame loop that plays continuously. The set is idle, walk, run, sit, sleep, eat, play, happy, and a special or reaction state.
Idle is the one that matters most in practice. It runs the overwhelming majority of the time, so a pet with a good idle animation feels alive even if the other states are unremarkable — and a pet with a stiff idle feels broken no matter how good the rest are.
What the pet does not do
Being clear about limits saves disappointment. A Codex pet does not respond to what you are typing, does not react to build failures or test results, and has no concept of your project.
It also cannot be interacted with directly in most builds — clicking it does not trigger anything, and there is no menu of tricks. Think of it as a screensaver with better provenance rather than a virtual pet game.
Where it lives on screen
The pet renders as a small transparent sprite, usually near an edge or corner of the desktop, and drifts within a limited area rather than roaming freely across your windows.
Because the spritesheet carries an alpha channel, the background is genuinely transparent — your wallpaper shows through rather than a coloured box. This is the detail that separates a pet that looks embedded in your desktop from one that looks pasted on top of it.
Running several pets at once
You can install as many as you like. Each lives in its own folder under ~/.codex/pets, and each needs a unique name field in its pet.json.
Uniqueness is not optional. If two folders declare the same name, the loader mounts one and silently discards the other, which presents as a pet that simply refuses to appear despite a perfect install.
What it costs in performance
Very little. The whole package is one WebP spritesheet plus a JSON file, usually a few tens of kilobytes, and redrawing a small 2D sprite is trivial compared with an editor, a language server, and a browser.
WebP is used over PNG precisely for this reason: full transparency at a fraction of the file size, which keeps both load time and per-frame decode cost low on a surface you are looking at all day.
Getting one of your own
Upload a clear, centered photo to a Codex-aware generator and it handles background removal, pixelation, all nine animation states, and the metadata file — typically in about a minute.
What you get back is a ZIP containing spritesheet.webp and pet.json. Copy the folder into ~/.codex/pets, make the folder name match the name field, fully restart Codex, and it is running.
Frequently asked questions
What does a Codex pet actually do?
It is an animated pixel-art companion that sits on your desktop while you work. It cycles through nine animation states — idle, walk, run, sit, sleep, eat, play, happy, and a reaction state — and otherwise stays out of the way. It is cosmetic; it does not affect how Codex writes or runs code.
Does a Codex pet slow down my machine?
Barely. A pet is a single WebP spritesheet of around 1536x1872 pixels plus a small JSON file, typically a few tens of kilobytes. Redrawing a small 2D sprite is negligible next to anything else running while you code.
Can I have more than one pet?
Yes. Install each pet as its own folder under ~/.codex/pets and give every one a unique name field in its pet.json. Duplicate names cause the loader to pick one and silently ignore the rest.
Can the pet interact with my code or terminal?
No. The pet is purely visual — it does not read your code, respond to commands, or send notifications. Its animation states play independently of what you are doing.
Related posts
Try it yourself
Ready to turn your own photo into a pixel-art pet? Upload it on PetGen and get your spritesheet + pet.json in minutes.
Generate your pet now →