Choose the built-in Codex pet
Best when you want a playful character contained inside the Codex experience.
Codex integration
Keep a custom mascot on your Mac while Codex works. It shows working, waiting, approvals, completion, errors, and subagent activity, then opens the right Codex surface when you need to respond.
Codex pet states
Masko turns Codex hooks and session activity into a few readable mascot states. Questions and permissions still belong to Codex, so Masko returns you to the right native surface.
The pet moves while Codex is using tools or progressing through a task.
A quiet attention state tells you when the session needs input.
The mascot points you back to the native Codex permission prompt.
A finished reaction makes the result visible away from the Codex window.
An interruption or failure gets a distinct reaction instead of disappearing in a tab.
Five readable signals
The mascot gives working, waiting, approval, completed, and error states a visible place on your desktop. Codex remains the source of truth for the task and every response.
Tools and subagents are active
The session needs input
Open the native Codex prompt
The task has finished
The session stopped unexpectedly
How it works
Masko connects through ~/.codex/hooks.json and Codex session logs. Its health screen installs or repairs the supported connection and confirms that activity is arriving.
Open the Apps or Integrations area in Masko Desktop.
Install the supported configuration at ~/.codex/hooks.json and Codex session logs.
Watch the mascot change as the agent works, waits, asks, or finishes.
In practice
Use the native Codex pet for a character inside Codex. Use Masko when you want a custom animated mascot that stays visible across your Mac and can connect to other supported agents too.
| Capability | Built-in Codex pet | Masko |
|---|---|---|
| Where it lives | Inside the Codex experience | As a floating character across your Mac desktop |
| Character choice | Codex pet choices and supported customization | Create from a sentence or image, or choose a marketplace mascot |
| Activity signals | Codex activity inside Codex | Codex hooks and session logs mapped to visible mascot states |
| Agent coverage | Codex | Codex plus other supported coding-agent integrations |
| Questions and approvals | Answered in the native Codex surface | Shows the request, then opens or focuses Codex to answer |
Best when you want a playful character contained inside the Codex experience.
Best when you want your own animated mascot across the desktop, with Codex state and other supported integrations in one character.
AI agents
See when Codex is working, waiting, asking, or done.
Approve a supported command or answer a question through your mascot.
Return to the exact terminal or app without hunting through tabs.
〉_ Bash
Run a build?$npm run buildBuilds the app. Nothing else changes.
Questions
No. The built-in pet belongs inside Codex. Masko adds a separate custom character that stays visible across your Mac and can represent activity from other supported agents too.
Yes. In Masko, you can create a mascot from a sentence or image, choose a marketplace character, or start with Ko, then connect that character to Codex activity.
Masko uses the supported local connection associated with ~/.codex/hooks.json and Codex session logs. Its health screen can install or repair that connection.
Masko shows the request and returns you to Codex, where the answer remains under Codex control.
Current support covers session lifecycle, tool activity, subagent activity, questions and approvals, completion and interruption.
Masko does not pretend to answer Codex permissions directly. It opens or focuses the correct Codex surface.
Masko Desktop supports macOS 14 or newer.
Masko for Mac