Skip to content
Masko

Codex integration

Give Codex a custom desktop pet.

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.

See how it works ↓

Codex pet states

Know when Codex is working or needs you.

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.

  1. 01
    Working

    The pet moves while Codex is using tools or progressing through a task.

  2. 02
    Waiting

    A quiet attention state tells you when the session needs input.

  3. 03
    Approval

    The mascot points you back to the native Codex permission prompt.

  4. 04
    Completed

    A finished reaction makes the result visible away from the Codex window.

  5. 05
    Error

    An interruption or failure gets a distinct reaction instead of disappearing in a tab.

Needs attentionWorkingOpen the right session.

Five readable signals

Follow Codex without watching the window.

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.

  1. Working

    Tools and subagents are active

  2. Waiting

    The session needs input

  3. Approval

    Open the native Codex prompt

  4. Completed

    The task has finished

  5. Error

    The session stopped unexpectedly

Codex needs youApproval requestedOpen the native prompt →

How it works

Connect Codex to Masko.

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.

  1. 01Install Masko

    Open the Apps or Integrations area in Masko Desktop.

  2. 02Connect Codex

    Install the supported configuration at ~/.codex/hooks.json and Codex session logs.

  3. 03Run a session

    Watch the mascot change as the agent works, waits, asks, or finishes.

In practice

Built-in Codex pets and Masko solve different jobs.

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.

Built-in Codex pet and Masko feature comparison
CapabilityBuilt-in Codex petMasko
Where it livesInside the Codex experienceAs a floating character across your Mac desktop
Character choiceCodex pet choices and supported customizationCreate from a sentence or image, or choose a marketplace mascot
Activity signalsCodex activity inside CodexCodex hooks and session logs mapped to visible mascot states
Agent coverageCodexCodex plus other supported coding-agent integrations
Questions and approvalsAnswered in the native Codex surfaceShows the request, then opens or focuses Codex to answer

Choose the built-in Codex pet

Best when you want a playful character contained inside the Codex experience.

Choose Masko

Best when you want your own animated mascot across the desktop, with Codex state and other supported integrations in one character.

AI agents

Your mascot keeps watch over Codex.

  1. 01Know when an agent needs you.

    See when Codex is working, waiting, asking, or done.

  2. 02Keep the work moving.

    Approve a supported command or answer a question through your mascot.

  3. 03Jump to the right session.

    Return to the exact terminal or app without hunting through tabs.

〉_ Bash

Run a build?$npm run build

Builds the app. Nothing else changes.

Questions

The practical bits.

Does Masko replace the built-in Codex pet?

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.

Can I create my own Codex pet?

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.

How does Masko connect to Codex?

Masko uses the supported local connection associated with ~/.codex/hooks.json and Codex session logs. Its health screen can install or repair that connection.

Can I answer Codex from the mascot?

Masko shows the request and returns you to Codex, where the answer remains under Codex control.

What does Masko see from Codex?

Current support covers session lifecycle, tool activity, subagent activity, questions and approvals, completion and interruption.

What is the current Codex limitation?

Masko does not pretend to answer Codex permissions directly. It opens or focuses the correct Codex surface.

Which Macs can run Masko?

Masko Desktop supports macOS 14 or newer.

Masko for Mac

Give Codex a custom desktop pet.