Repository navigation
[step-names] Align Codex engine step names: "Install Codex CLI" vs "Execute Codex" #21956
Description
Activity
🍪 Issue Monster has assigned this to Copilot!
I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot coding agent.
The Copilot coding agent will analyze the issue and create a pull request with the fix.
Om nom nom! 🍪
Note
🔒 Integrity filtering filtered 2 items
Integrity filtering activated and filtered the following items during workflow execution.
This happens when a tool call accesses a resource that does not meet the required integrity or secrecy level of the workflow.- issue:[cli-consistency] CLI Consistency Issues - 2026-03-20 #21967 (
issue_read: Resource 'issue:[cli-consistency] CLI Consistency Issues - 2026-03-20 #21967' has lower integrity than agent requires. Agent would need to drop integrity tags [unapproved:all approved:all] to trust this resource.) - issue:[step-names] Align Codex engine step names: "Install Codex CLI" vs "Execute Codex" #21956 (
issue_read: Resource 'issue:[step-names] Align Codex engine step names: "Install Codex CLI" vs "Execute Codex" #21956' has lower integrity than agent requires. Agent would need to drop integrity tags [unapproved:all approved:all] to trust this resource.)
🍪 Om nom nom by Issue Monster · ◷
- issue:[cli-consistency] CLI Consistency Issues - 2026-03-20 #21967 (
- linked a pull request that will close this issuefix(codex): align execute step name to "Execute Codex CLI" #21972
on Mar 20, 2026
Step Name Alignment Issue
Found in:
.github/workflows/smoke-codex.lock.ymland 16 other Codex engine workflowsSummary
Codex engine workflows use inconsistent "CLI" suffix between their install and execute steps. All other engines use the "CLI" suffix in both install and execute step names — Codex installs with "CLI" but executes without it.
Issue Identified
[High Priority] Inconsistent CLI suffix: "Install Codex CLI" vs "Execute Codex"
Current step names (in same workflows):
name: Install Codex CLI— 17 workflowsname: Execute Codex— 17 workflows (same files)Established engine naming pattern:
Issue:
Install Codex CLIwas updated to add the "CLI" suffix (matching the Codex CLI official tool name), butExecute Codexwas not updated accordingly, leaving both names in the same workflow files.Suggested fix:
Update
Execute Codex→Execute Codex CLIin all 17 affected Codex workflows to match the install step and align with the engine naming pattern used by all other engines.Affected workflows (17 total, sample):
smoke-codex.lock.ymlai-moderator.lock.ymlchangeset.lock.ymlcodex-github-remote-mcp-test.lock.ymldaily-fact.lock.ymldaily-issues-report.lock.ymldaily-observability-report.lock.ymldeep-report.lock.ymlduplicate-code-detector.lock.ymlissue-arborist.lock.ymlschema-feature-coverage.lock.ymlsmoke-agent-all-merged.lock.ymlsmoke-agent-all-none.lock.ymlsmoke-agent-public-approved.lock.ymlsmoke-agent-public-none.lock.ymlsmoke-agent-scoped-approved.lock.ymlsmoke-call-workflow.lock.ymlAgentic Task Description
To fix this inconsistency:
.mdsource workflows for each affected.lock.ymlExecute Codex→Execute Codex CLIin each source filegh aw compile (workflow).mdto regenerate each.lock.ymlCodex CLIsuffix in each compiled fileRelated Files
.github/workflows/*.md(Codex engine workflows).github/workflows/*.lock.yml(17 affected files)docs/src/content/docs/reference/glossary.mdPriority
This issue is High Priority — it affects 17 workflows and breaks the established engine naming pattern.