bug(approval): the write-stdin approval overlay (Codex 0.151+) is never detected #64

Activity

1. Juliusolsson05

   added

   bugSomething isn't workingSomething isn't working

   provider:codexAffects Codex integrationAffects Codex integration

   on Sep 27, 2026
2. Juliusolsson05 commented on Sep 27, 2026

   

   Juliusolsson05

   on Sep 27, 2026

   OwnerAuthor

   More actions

   New evidence (W1, 2026-09-27, upstream source at tag rust-v0.157.1): this overlay is off by default in 0.157.1, so it does not block accepting 0.157.1.

   • Gate 1: a feature flag. The approval is requested only when the write_stdin_approval feature is enabled (core/src/unified_exec/stdin_approval.rs: !features().enabled(Feature::WriteStdinApproval) → Ok(None)). features/src/lib.rs declares that feature Stage::UnderDevelopment, default_enabled: false.
   • Gate 2: a retained escalation. Even with the flag on, the approval fires only for a terminal whose launch permissions differ from the current ones (escalated or with retained grants), or under strict auto-review. Plain input to a normal sandboxed terminal returns UseDefault → Ok(None).
   • The title. The command vector is always ["write_stdin","--session-id",<pid>,<input>], so command.get(2) always exists. In practice the title is always "Would you like to send input to terminal {pid}?"; the "existing terminal" wording is unreachable today.
   • The rendered overlay (upstream snapshot chatwidget/tests/snapshots/…write_stdin_approval_modal.snap):

       Would you like to send input to terminal 42?
     
       Input: "confirm\n"
     
     › 1. Yes, proceed (y)
       2. No, and tell Codex what to do differently (esc)
     
       Press enter to confirm or esc to cancel
     

   Why no live recording: triggering this overlay needs the under-development flag plus an escalated terminal. That means a model session with an approved escalation, which Agent Code's default launch never produces.

   Plan: keep this open as a real gap, but at lower priority than #63 and #65. When it is fixed:

   • add the title;
   • parse Input: "<input>" into the command field;
   • test against the upstream snapshot frame.

   I am removing it from agent-code#234's blocker list.