Misleading “still working” messages after “Finished working” (no background tasks actually run)

Resolved 💬 6 comments Opened Nov 16, 2025 by iamhectorlopez Closed Feb 23, 2026

What version of Codex is running?

0.4.43 IDE extension cursor

What subscription do you have?

plus

Which model were you using?

gpt 5.1 high

What platform is your computer?

windows

What issue are you seeing?

Codex repeatedly claims it is still working on an expanded test suite, running dry runs locally, and that it will share updates shortly, even though the run has already finished and no further work is being done.

<img width="565" height="493" alt="Image" src="https://github.com/user-attachments/assets/93eccdc1-6209-41a8-a0df-9f519fd41da8" />

What steps can reproduce the bug?

  1. Open the codex cursor ide extension and use GPT-5.1-Codex with Agent (full access) on a local repo.
  2. Give the agent a long-running style instruction

The UI shows multiple entries like:
“Finished working • Considering response timing”
“Finished working • Considering next steps”

but no new commands are executed after that point or no files or code changes appear in the repo.

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

This issue has 6 comments on GitHub. Read the full discussion on GitHub ↗