Skip to content

Conversation

jif-oai
Copy link
Contributor

@jif-oai jif-oai commented Oct 22, 2025

No description provided.

Copy link
Contributor

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +168 to +169
fn build_denial_reason_from_output(output: &ExecToolCallOutput) -> String {
format!("command failed: {}\nretry without sandbox?", output.aggregated_output.text)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Keep approval reason string stable

The retry prompt now formats command failed: {output}\nretry without sandbox?, which includes the full aggregated command output. The existing approval tests (core/tests/suite/approvals.rs) assert the reason is the constant "command failed; retry without sandbox?", so this change will immediately break those scenarios and reintroduces OS‑specific and potentially multiline text into the approval reason. Either trim/normalize the message or update the tests and callers that expect the concise string.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant