Codex is reported as blocked while continuing work with pending asynchronous questions
Author: ryan-quenlumCreated Sep 18, 2026Updated Sep 18, 2026
Labelsbugmaintainer-neededp2linuxagent-detection
Is this a reproducible bug?
- I confirm this is a reproducible bug, not a feature request, idea, question, contribution proposal, or direction check.
- I reproduced this bug on the version and environment reported below using the exact steps provided.
Current behavior
Herdr's sidebar and herdr agent list report an actively running Codex pane as blocked. Codex continues executing tools and displays Working (... • esc to interrupt) while asynchronous questions are pending. Its terminal title contains Action Required.
Expected behavior
A pending asynchronous question should not make ongoing execution appear stopped. The displayed status should distinguish ongoing work from waiting for an answer before work can continue.
Reproduction
- Run Codex in Herdr and ask it to request optional input while continuing independent work.
- Leave its asynchronous question unanswered while it continues running tools. This was reproduced in an existing session with 26 pending questions.
- While Codex displays
Working (... • esc to interrupt), runherdr agent listandherdr agent explain <pane> --json. - Observe
blocked. The explanation reports bothosc_title_blocked: matched=trueandscreen_working_fallback: matched=true, with finalstate: blocked.
Impact
The agent roster tells me that a productive session is blocked, making it difficult to identify sessions that actually need me before they can proceed.
Environment
- Herdr version: 0.8.2 (client and running server), remote Codex detection manifest 2026.09.14.1; no local override.
- Update channel (stable or preview): stable.
- Operating system: Omarchy Linux.
- Terminal: foot, with Herdr's persistent server/client session.
- Shell, if relevant: bash.
- Relevant config, if any: Codex CLI 0.154.0. No custom detection manifest.
Source: herdrdev/herdr