Skip to content

🤖 fix: preserve spacing around nested code execution tools - #4150

Merged
ammario merged 1 commit into
fix/codex-informational-commentsfrom
fix/code-execution-nested-spacing
Sep 8, 2026
Merged

🤖 fix: preserve spacing around nested code execution tools#4150
ammario merged 1 commit into
fix/codex-informational-commentsfrom
fix/code-execution-nested-spacing

Conversation

@ammar-agent

@ammar-agent ammar-agent commented Sep 8, 2026

Copy link
Copy Markdown
Collaborator

Stacked on #4151 (approval-waiter follow-up to the checker fix merged in #4149). Merge #4151 first; the diff against this PR's base remains spacing-only.

Summary

Keep all nested tool cards inset from the Code Execution border. The shared nested-tools container was cancelling its parent's horizontal padding with negative margins, so bordered cards such as task_send_message sat against the dashed frame. Removing that override fixes the shared layout rather than adding tool-specific spacing workarounds.

Validation

  • Added full-app desktop and phone stories covering agent_report, file_read, and task_send_message, including collapsed/expanded message cards. Geometry assertions verify border clearance, separation between tools, and no horizontal overflow.
  • Confirmed the new tests fail before the fix (1px edge clearance) and pass afterward. Storybook-manager checks at 375px and 1280px measured 13px clearance on both sides.
  • make static-check passed; 7 full-app Storybook tests and 63 targeted tool-renderer/unit tests passed.
Existing local validation limitation

The isolated CodeExecutionToolCall gallery has a Vite development-time circular-import error (Cannot access 'CodeExecutionToolCall' before initialization). Reproduced with the original production file as well. The full-app code-execution and agent-communication stories pass.


Generated with xum • Model: openai:gpt-6-astra • Thinking: xhigh • Cost: $24.54

@ammar-agent

Copy link
Copy Markdown
Collaborator Author

@codex review

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 8, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-09-08T18:42:29.718429Z 9f03376 Manual request
🔒 Security Review Completed 2026-09-08T18:42:48.473526Z 9f03376 Manual 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. What shall we delve into next?

Reviewed commit: fa36684efd

ℹ️ 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".

@chatgpt-codex-connector

Copy link
Copy Markdown

Security review completed. No security issues were found in this pull request.

Reviewed commit: fa36684efd

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

  • You comment "@codex security review"
  • A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

@ammar-agent

Copy link
Copy Markdown
Collaborator Author

Codex completed both code and security review with no findings, and its approval remains visible. Marking the completed status summary and clean security result as resolved: the current Codex Comments checker mistakes these informational comments for unresolved findings. No review findings or threads are being dismissed. Rerunning the check without broadening this spacing-only PR.

@ammar-agent
ammar-agent changed the base branch from main to fix/codex-informational-comments September 8, 2026 17:56
@ammar-agent

Copy link
Copy Markdown
Collaborator Author

@codex review

Rebased onto the separate checker fix in #4151. The spacing-only diff is unchanged. Restored both informational bot comments; the corrected checker now passes with them visible. Revalidated static checks, checker regressions, renderer tests, and all seven full-app desktop/phone stories.

@ammar-agent
ammar-agent force-pushed the fix/code-execution-nested-spacing branch from fa36684 to 8f9c3f4 Compare September 8, 2026 17:56
@chatgpt-codex-connector

Copy link
Copy Markdown

Security review completed. No security issues were found in this pull request.

Reviewed commit: 8f9c3f4b4a

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

  • You comment "@codex security review"
  • A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. 🚀

Reviewed commit: 8f9c3f4b4a

ℹ️ 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".

@ammar-agent

Copy link
Copy Markdown
Collaborator Author

@codex review

Updated the stack to the reviewed checker fix in #4151. The two-file spacing diff is unchanged; local static checks and checker regressions pass.

@ammar-agent
ammar-agent force-pushed the fix/code-execution-nested-spacing branch from 8f9c3f4 to fea601d Compare September 8, 2026 18:04
@chatgpt-codex-connector

This comment has been minimized.

@ammar-agent

Copy link
Copy Markdown
Collaborator Author

@codex review

Retrying the previous Codex service failure (Unknown error). No code changes since the last request; marking that failed-request notification outdated while this new review runs.

@chatgpt-codex-connector

Copy link
Copy Markdown

Security review completed. No security issues were found in this pull request.

Reviewed commit: fea601d8bd

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

  • You comment "@codex security review"
  • A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. 🎉

Reviewed commit: fea601d8bd

ℹ️ 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".

@ammar-agent

Copy link
Copy Markdown
Collaborator Author

@codex review

Rebased onto the approved final checker commit from #4151. The spacing-only diff is unchanged, and local static checks plus checker regressions pass.

@ammar-agent
ammar-agent force-pushed the fix/code-execution-nested-spacing branch from fea601d to 301a4a8 Compare September 8, 2026 18:28
@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. 👍

Reviewed commit: 301a4a82a4

ℹ️ 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".

Keep shared parent gutters intact instead of requiring per-tool spacing fixes. Add desktop and phone geometry regressions.

---

_Generated with `xum` • Model: `openai:gpt-6-astra` • Thinking: `xhigh` • Cost: `$15.92`_

<!-- mux-attribution: model=openai:gpt-6-astra thinking=xhigh costs=15.92 -->
@chatgpt-codex-connector

Copy link
Copy Markdown

Security review completed. No security issues were found in this pull request.

Reviewed commit: 301a4a82a4

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

  • You comment "@codex security review"
  • A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

@ammar-agent

Copy link
Copy Markdown
Collaborator Author

@codex review

Rebased onto current main and the reduced #4151 waiter follow-up. The checker implementation from merged #4149 is preserved unchanged; this PR still contains only the two spacing files. Static checks, all 11 checker regression groups, and all 7 full-app desktop/phone stories pass locally.

@ammar-agent
ammar-agent force-pushed the fix/code-execution-nested-spacing branch from 301a4a8 to 9f03376 Compare September 8, 2026 18:33
@chatgpt-codex-connector

This comment has been minimized.

@chatgpt-codex-connector

Copy link
Copy Markdown

Security review completed. No security issues were found in this pull request.

Reviewed commit: 9f0337682b

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

  • You comment "@codex security review"
  • A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

@ammar-agent

Copy link
Copy Markdown
Collaborator Author

@codex review

Retrying the code-review service request that returned Unknown error. No code changes. The failed-request notification is outdated; explicit approval is still required for this revision.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Keep them coming!

Reviewed commit: 9f0337682b

ℹ️ 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".

@chatgpt-codex-connector

Copy link
Copy Markdown

Security review completed. No security issues were found in this pull request.

Reviewed commit: 9f0337682b

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

  • You comment "@codex security review"
  • A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

@ammario
ammario added this pull request to the merge queue Sep 8, 2026
Merged via the queue into main with commit 7c1a58f Sep 8, 2026
35 of 38 checks passed
@ammario
ammario deleted the fix/code-execution-nested-spacing branch September 8, 2026 21:47
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.

2 participants