Notification setup generator for Claude Code, Codex and Gemini CLI.

Codex's built-in alerts, with the bell.

Optional: Codex's built-in Mac alerts.

In ~/.codex/config.toml

If the file already has a [tui] section, don't add the [tui] line again. Under the existing one, change the value of any of these keys that is already there and add only the missing ones. A second [tui] header, or the same key written twice, stops Codex from reading the file.

What the bell does depends on your terminal. In Terminal, open Settings > Profiles > Advanced > Bell to choose a sound, a badge or a bouncing Dock icon.

Hooks for your selected alert.

In ~/.claude/settings.json

Add these entries to the "hooks" object in the file, next to what is already there. Do not replace the file: it can hold your other settings and other tools' hooks. Settings files are strict JSON, so no comments and no trailing commas. Easier: paste your current file in the merge box below.

Add these as new entries in the file. Cowork Island and other tools can write to this same file, so never overwrite it; the merge box below does this for you. Then open Codex, type /hooks and trust each new entry: Codex skips new or changed hooks until you do.

Add these entries to the "hooks" object in the file, next to what is already there, or use the merge box below. Gemini CLI hooks may print only JSON, so each command ends by printing {}.

Add this setting to the file, next to what is already there, or use the merge box below.

{
  "hooks": {
    "Stop": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "/usr/bin/osascript -e 'on run argv' -e 'display notification (item 1 of argv) with title (item 2 of argv) subtitle (item 3 of argv) sound name \"Glass\"' -e 'end run' 'Claude Code finished' 'Claude Code' \"${PWD##*/}\""
          }
        ]
      }
    ],
    "Notification": [
      {
        "matcher": "permission_prompt|elicitation_dialog|elicitation_url_dialog",
        "hooks": [
          {
            "type": "command",
            "command": "/usr/bin/osascript -e 'on run argv' -e 'display notification (item 1 of argv) with title (item 2 of argv) subtitle (item 3 of argv) sound name \"Funk\"' -e 'end run' 'Claude Code needs you' 'Claude Code' \"${PWD##*/}\""
          }
        ]
      }
    ]
  }
}

• For Claude Code, permission alerts and input requests from connected tools arrive about 6 seconds after the prompt appears, and typing pushes them back. That is how Claude Code's Notification hook works. Other questions may not trigger this hook.
• The finished alert uses Stop, which fires each time Claude finishes a reply, not only at the end of a long task. It does not fire when you interrupt Claude.
• Claude Code holds back hooks in a folder until you accept its workspace trust dialog. On a work Mac, your organization may allow only its own hooks.
• If a session that is already open does not pick up the change, restart it.

Your randomly named ntfy topic.

Topics on ntfy.sh are public. Anyone who knows or guesses a topic name can read what is sent to it, so treat it like a password. That is why this topic is 32 random characters made by your browser, and why the hook sends only a fixed line such as “Claude Code finished”, never the agent's reply or the contents of your files.

On your phone, install the ntfy app and subscribe to this topic. ntfy.sh is a free third-party service with its own daily message limits.

Test it.

Paste this line in Terminal and press Return. It runs the same command the hook will run.

/usr/bin/osascript -e 'on run argv' -e 'display notification (item 1 of argv) with title (item 2 of argv) subtitle (item 3 of argv) sound name "Glass"' -e 'end run' 'Claude Code finished' 'Claude Code' "${PWD##*/}"

Test the bell.

Paste this line in Terminal and press Return:

printf '\a'