Wild Ideas: Pets in CI/CD and Other Impossible Combos

Where these pixel pet ideas come from

Every couple of weeks somebody posts a screenshot with a pet parked next to a red pipeline, and the replies fill up with pixel pet ideas. Most are jokes. A few are jokes that somebody actually built.

I went through roughly forty of them and sorted them by effort. A handful run today with nothing but a shell script. Some need a real integration. The rest belong in the joke pile, and I say that as someone who likes them.

The fun codex pet ideas that work today

The pet is a folder on disk. Anything that can move files around can change which one you see, which is why these four need no permission from Codex at all.

• Build status mirror: a script watches the pipeline and points Codex at the green pet or the red one
• Standup timer: the pet drops into its waiting state two minutes before the call starts
• Branch guard: a different pet on main than on feature branches, so you notice before running the wrong command
• Focus blocks: one pet for deep work hours, another for the review block after lunch
• None of these read your CI. Your script does, and it moves a folder.

Creative pet use off the desktop

The creative pet use cases hold up better than the automation ones, mostly because a finished image does not break when an API changes.

• Changelog art: the same pet in every release image, so the series reads as one product
• Team wiki: new hires generate one and it lands next to their name on the onboarding page
• Conference slides: a pixel pet in the corner reads better than another stock illustration
• Support docs: screenshots that all use one theme look like they came from one team

The impossible pet combos

Now the part everybody asks about. These come up in every thread, and none of them work the way people describe them.

• Live reaction to test output: the sprite sheet has nine fixed states. A script can pick one, but it cannot invent a tenth.
• A pet inside the pull request: pets render on your desktop. Anything inside a PR is an image somebody uploaded.
• Coverage-driven pet moods: coverage is a number and the pet has no idea what a number is. You would still be the one reading it.
• One shared pet for the whole team: every install is local, so two people see two pets on two machines.
• A pet that fixes the build: this one I would pay for. It does not exist.

What a working setup costs you

For one person this is usually more setup than the payoff. It starts making sense when five people share the same script.

• One shell script, 20 to 40 lines, no dependencies beyond curl
• Two sprite sheets, one for green builds and one for red
• A cron entry or a webhook that calls the script
• Roughly nine seconds to install a pet by hand, less once the folder move is scripted
• Five minutes of debugging the first time the script runs as the wrong user

Pick one and try it

Start at /, generate a pet from any photo you have lying around, and read why these companions stick at /blog/why-developers-love-desktop-companions. Terminal install steps are at /blog/install-codex-pet-terminal and plan limits are on /pricing. The generator itself lives at codexpetgenerator.com.