Integrate brrr with Codex

Codex supports notifications via notify, which run an external program when Codex emits a supported event.

That makes Codex a good fit for brrr. You can use brrr-cli if you want a managed setup, or wire up notify yourself and post to your webhook with curl.

Use brrr-cli

brrr-cli sets up Codex integration by updating ~/.codex/config.toml. It installs the notify command to send notifications when Codex finishes.

Learn more on GitHub.

Configure Codex notify manually with curl

Codex reads ~/.codex/config.toml. The notify setting points to an external program, and the simplest manual setup is to have it invoke curl directly.

TOML
notify = [
  "curl",
  "-X",
  "POST",
  "https://api.brrr.now/v1/🙈🙈🙈🙈🙈🙈🙈🙈🙈🙈",
  "-d",
  "Codex finished responding."
]

This keeps the integration simple. Every time Codex emits the supported notification event, it runs curl and sends a plain text body to your brrr webhook.

About the notify payload

The external program receives a single JSON argument containing fields such as type, thread-id, turn-id, cwd, input-messages, and last-assistant-message. The simple curl example above ignores that argument and just sends a fixed message, which is often enough.

If you want to include more context later, you can replace the direct curl call with a small script that reads the JSON argument and formats a more detailed notification.

brrr-cli uses Codex' payload to send richer notifications with more context than the minimal direct curl setup.