Install Codex Pet
Install pets into Omnibot's selectable pet directory while preserving the official Codex package format.
Workflow
- Extract the lowercase pet slug or collection slug from the request. Do not guess when no slug is present.
- Confirm
node,npm, andnpxare available. If they are missing, report that the embedded {{OMNIBOT_TERMINAL_DISTRIBUTION}} environment needs its base packages installed. - Point the official CLI at Omnibot's Codex-compatible pet root, then run the requested command:
shexport CODEX_HOME=/workspace/.omnibot npx --yes codex-pets add claude-pixel
For a collection:
shexport CODEX_HOME=/workspace/.omnibot npx --yes codex-pets add-collection cats
- Validate each installed pet:
shsh /workspace/.omnibot/skills/install-codex-pet/scripts/validate_codex_pet.sh claude-pixel
- Report the installed display name and
/workspace/.omnibot/pets/<pet-id>/. The appearance page discovers the package automatically; do not copy it into another pet directory.
Rules
- Keep
CODEX_HOME=/workspace/.omnibotfor everycodex-petscommand. The package defaults to/root/.codex, which the Omnibot appearance scanner does not use. - Use the npm CLI directly. Do not generate replacement art, rewrite the downloaded manifest, or hand-build a package.
- Accept only lowercase slugs made from letters, digits, and hyphens.
- Treat command failures, missing
pet.json, missingspritesheet.webp, an id mismatch, or an unexpectedspritesheetPathas installation failures. - Never expose credentials or add API keys to commands.
CODEX_PETS_API_BASEmay be used only when the user explicitly provides a trusted alternate service.

