Codex Desktop shows background hook transcript noise, while the TUI does not #17479

What version of the Codex App are you using (From “About Codex” dialog)?

26.409.20454

What subscription do you have?

Pro

What platform is your computer?

25.0.0 arm64 arm

What issue are you seeing?

I’m integrating Codex into a notchi and found an inconsistency between the Codex TUI and Codex Desktop.

Problem

The same background hooks behave cleanly in the Codex TUI, but Codex Desktop still surfaces hook-related transcript noise in the conversation UI.

This makes Desktop much harder to integrate with for background apps that use hooks only as an internal event bridge.

What I observed

Using the same Notchi integration hooks:

In the terminal TUI

The conversation looks nice without hooks. Example:

In Codex Desktop

The Desktop thread still surfaces hook-related noise / behavior that makes hook-based background integrations feel much worse.

Why this matters

For integrations like Notchi, hooks are the best technical integration path:

• push-based
• low-latency
• structured
• much better than polling rollout/session files

If Codex Desktop cannot hide non-user-facing hook activity cleanly, integrations are pushed toward weaker file-monitoring workarounds just to avoid transcript pollution.

Expected behaviour

Codex Desktop should handle background/internal hooks at least as cleanly as the TUI does.

Ideally there should be a supported way for Desktop to suppress non-user-facing hook transcript entries, for example:

• honoring a hook-level suppression flag
• or otherwise not rendering background hook lifecycle rows into the chat UI

Additional context

There is prior work related to hook-status rendering here for TUI:

• #17266

What steps can reproduce the bug?

1. Configure Codex with a local hook intended only for background/internal integration.
   Example: any simple hook script that forwards Codex events to another process without intending to show user-facing output.

2. Use that same hook configuration in both:

   • terminal codex TUI
   • Codex Desktop

3. Start a conversation in each client.

4. Send a few normal prompts that trigger the configured hook events during ordinary usage.

5. Compare how the transcript is rendered in each surface.

What is the expected behavior?

No response

Additional information

No response