Hey, thanks for the report. This is a known limitation, not something in your setup.
Inline diff and review only track changes the model makes via the native edit tools. When the model edits files through the terminal, like running a Python script, it writes straight to disk and skips the review layer, so the inline diff doesn’t show up. That’s why Composer 2.5, which uses the edit tools, shows a diff, but Grok 4.5 often doesn’t when it switches to scripts. The changes are still real and you can see them in Source Control and git diff.
What you can do right now:
- Review those edits via Source Control or
git diff, everything in the working tree shows up there no matter how it was changed. - Prompt the model more strongly to edit via the edit tools, not via shell scripts, for example add a rule that it shouldn’t write files via Python or other scripts.
Related thread with details: Agent edits made via the terminal (script/shell writes) don't appear in the inline edit-review UI
I’ll pass along that Grok 4.5 seems more likely to switch to scripts as a separate note about model behavior. If you can check the transcript to see why it chose to edit via a script, like tool calls failing or the model thinking it was cheaper, that’d help a lot. Let me know how it goes.