agent-signals

Screen codex/busy-v0-164-0

A turn runs, about 2 s after the Enter. The busy line "◦ Working (1s • esc to interrupt)" is above the box. The box, its placeholder and the footer "? for shortcuts" stay drawn while the turn runs, so the footer is not a proof of IDLE: a reader must first look for "esc to interrupt". tg-bridge asked for this screen (tg-bridge #120). Measured with the scenario scenarios/codex/screens.sh.

Expected state
BUSY
Agent version
Codex CLI 0.164.0
Provenance
measured-edited
The text of the screen codex/busy-v0-164-0: 120 columns by 40 rows, a plain capture.

  >_ OpenAI Codex (v0.164.0)
     /work/example

  To get started, describe a task or try one of these commands:

  /init - create an AGENTS.md file with instructions for Codex
  /status - show current session configuration
  /permissions - choose what Codex is allowed to do
  /model - choose what model and reasoning effort to use
  /review - review any changes and find issues


› Count from 1 to 40, one number on each line. Use no tool.



















◦ Working (1s • esc to interrupt)


› Ask Codex to do anything

  GPT-6-Luna default · /work/example
  ← for agents · ? for shortcuts                                                               ⚠ 1 warning · f2 to view

Download the exact bytes of this screen Read the metadata file on GitHub

Expected result

state
BUSY
dialog
none

Metadata

agent
codex
agent_version
0.164.0
measured
2026-10-30
capture
plain
pane
120 columns, 40 rows
provenance
measured-edited
edits
  • the path of the throwaway folder is scrubbed to /work/example, so each line that held it is shorter
negative_control_for
idle-v0-164-0
facts