awaiter sub-agent approval prompt did not surface
Resolved 💬 9 comments Opened Feb 25, 2026 by rwagner3 Closed Feb 27, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
Version and model details:
╭──────────────────────────────────────────────────╮
│ >_ OpenAI Codex (v0.105.0) │
│ │
│ model: gpt-5.3-codex high /model to change │
│ directory: ~ │
╰──────────────────────────────────────────────────╯
Codex described the issue like so:
• You’re right. What happened:
- I launched the benchmark via the awaiter sub-agent.
- That command needed escalated permissions (tailnet network access).
- The approval prompt didn’t surface correctly in the sub-agent panel, so it looked stuck.
edit: Ubuntu 24.04
9 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Please use
/feedbackto upload the logs and session details, then post the thread ID here.While I did use /feedback and let it upload the logs and session details as well as followed the URL it provided here to open the ticket, I didn't realize I needed to capture the thread ID. Please close if I haven't provided enough info. I'll know to retain the thread ID next time.
If you still have the thread around, you can look up its ID using
/status. If you're able to find it, post it here and I'll dig into the logs. If not, please feel free to file a new issue if you see it again.I ran into the same issue
019c97c6-91a4-7612-9afb-28d70a10a8b2• Spawned Basil [awaiter]
└ Run
some command• Waiting for Basil [awaiter]
! Approval needed in Basil [awaiter]
Same here, ID 019c9a27-94fe-7051-8417-3bf655736fe0
Confirmed on the latest version (v0.106.0). Downgrading to v0.104.0 (
npm install -g @openai/codex@0.104.0) resolves the problem and restores normal behavior.https://github.com/openai/codex/pull/12995
Not sure if I had the same issue as described here, but in any case my thread ID is
019ca20b-361b-7980-bc52-e3b1e88b9e0e