Skip to content

Chat: A Codex hook-blocked message can leave the conversation Working #27658

Closed as not planned

Description

@brennanb2025

What happens

When a Codex prompt-checking script (a hook) refuses a submitted prompt, Codex can finish the turn without echoing the message. Orca can leave the conversation showing Working and prevent the next message from proceeding.

Expected

Read the hook’s refusal, settle the unanswered message when that turn completes, and let the user send another message.

Notes

An earlier attempt is in #25049, closed because it was too far behind main; its description has the diagnosis. On origin/main, src/main/native-chat/agent-session-wire/provider-frame-disposition.ts:39 suppresses hook completion, and src/main/codex/codex-structured-turn-end-settlement.ts:125 returns no rejection for a normally completed turn.

Activity

  1. brennanb2025 commented on Oct 12, 2026

    @brennanb2025
    ContributorAuthor

    Moving this to our internal tracker, so closing it here to keep this list to user-reported issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions