codex - 💡(How to fix) Fix Expose custom interaction hooks and APIs for Codex desktop pets

What variant of Codex are you using?

Codex App (desktop), with custom pets generated/installed through Hatch Pet. This may also be relevant to CLI/SDK surfaces if they expose the same pet/action contract later.

What feature would you like to see?

Please expose a supported interaction/API contract for Codex desktop pets, beyond visual spritesheet customization.

Requested capabilities:

• Let a custom pet declare safe interactions in pet.json, e.g. click, double-click, right-click/context menu, hover, drag/drop, and optional keyboard shortcut actions.
• Let those interactions call first-party Codex actions or approved deep links, such as:
  • open/tuck the pet;
  • open the current or related Codex thread;
  • create a new thread for a configured workspace/prompt;
  • open a local project dashboard or app route through an allowlisted URL/deeplink;
  • invoke a named skill/command where permissions allow.
• Expose a small, documented read-only status/event API for pets to observe agent/thread state, e.g. idle, running, waiting for user, ready for review, failure, latest activity category, active workspace/thread id.
• Keep the contract permissioned and safe: no arbitrary command execution by default; require user approval/allowlisting for external URLs, local apps, workspace commands, and any write-capable integration.
• Document the interaction contract so third-party dashboards can integrate with the official Codex pet instead of building their own always-on launcher.

Additional information

Related but distinct: #20863 asks for configurable animation sequences and activity events. This request is about interaction hooks and open integration surfaces.

Use case: a local project dashboard or personal wiki may want the official Codex pet to act as a lightweight entry point and status surface. For example, clicking the pet could open the project dashboard, create a project-specific Codex thread, or show safe actions for maintaining the project. Without supported hooks, users either treat pets as visual-only status indicators or build a separate desktop companion/launcher, which duplicates the Codex pet's role.

A minimal first version could be a manifest-defined context menu with allowlisted codex:// actions and read-only status events. More advanced versions could expose a small SDK/API for registered local apps.