openai / openai/codex

Feedback: a status question does not reliably pause pending external publication

Open
#42,272 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug CLI model-behavior
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

Summary

A user asked a status question while the agent had staged, but not yet committed, local files for a pending repository publication. The agent answered the question and then continued the earlier workflow by committing and pushing the staged files.

Reproduction pattern

  1. Ask the agent to publish a broad set of changes.
  2. Before its commit and push, ask whether a named subset is already present in the pull request.
  3. The agent can interpret the status question as additive rather than as a request to inspect and pause the pending side effect.
  4. It proceeds to publish files outside the subset discussed in the status question.

Expected behavior

A user status question during a pending external side effect should pause the side effect. The agent should report the exact staged set and require a renewed, specific instruction before publishing any remaining files.

Impact

Generated local artifacts were committed and pushed although the user was seeking confirmation about the intended source changes.

Environment

Codex CLI 0.152.0 on macOS.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the staged-files workflow described in the issue using Codex CLI 0.152.0 on macOS, including a status question before commit and push. Trace the handling of status questions during pending publication, then verify that the exact staged set is reported and publishing pauses until a renewed, specific instruction is given.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli, developer-experience
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.