The short version
Pet Studio keeps the artwork shared and changes the delivery package for the target you choose. The current export surface names nine targets:
- Codex, with a native pet.json and spritesheet.webp package.
- Claude Code, through a lifecycle hooks bridge.
- Gemini CLI, through a lifecycle hooks bridge.
- OpenCode, through a local event plugin bridge.
- GitHub Copilot CLI, through user-level hooks.
- Cursor, through lifecycle hooks.
- Agent Pets, through a desktop-runner compatibility package.
- Petdex, through Petdex and Codex storage installation.
- Clawd on Desk, through a Codex pet-directory adapter.
Why the target matters
The target determines where the files are installed and which lifecycle event can display the companion. A hooks or plugin bridge is not the same thing as a native pet package, so read the generated README and follow the target's current extension rules.
A safe installation checklist
- Download the package for the agent you actually use.
- Read its README and inspect the included integration.json.
- Install it in the target's documented user or project directory.
- Run the target's own smoke check before enabling it for daily work.
The export is an integration artifact, not a promise that a third-party agent will accept every future version. Provider and agent interfaces remain the source of truth. You can create a pet in Studio and choose the target package after the shared artwork is ready.