Notifications
Consume live Codex progress through SDK streams or MCP notifications.
Codex does not expose a hosted webhook API. For in-process integrations, consume the SDK's async events generator. For MCP integrations, consume protocol notifications such as thread/started, turn/completed, and codex/event/*.
Treat event types as a discriminated union and handle unknown future events safely. Use turn.completed as the completion boundary and inspect the emitted items for command, file, MCP, and error details.
Aggiornato il 31 ago 2026