fix(grok): Grok updates actually install on npm 12#24246

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.

External image Run configuration

• Source mode: Auto
• Repository: pingdotgg/t3code
• Branch: main
• File: .coderabbit.config.ts
• Commit: 220eb73
• Layers: Repository TS config
• Review profile: CHILL
• Plan: Advanced
• Run ID: 4cd013a7-f591-4015-8da9-7756de84277b

External image Commits

Reviewing files that changed from the base of the PR and between 0716eac3666daa5643213088315b57b981b89c81 and 4f4574175ee21a4ac1a0a726c5d2e464b4373e38.

External image Files selected for processing: 1

• packages/provider-grok/src/server/driver.ts

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 8 remain after this review.

Non-cask Grok updates now set npm_config_allow_scripts to @xai-official/grok. The test expectation includes this environment setting, and a maintenance comment describes npm’s postinstall behavior.

Changes: Grok update behavior

Layer / File(s)	Summary
Allow Grok postinstall during updates packages/provider-grok/src/server/driver.ts, packages/provider-grok/src/server/driver.test.ts	Non-cask updates add npm_config_allow_scripts for @xai-official/grok to the update environment. A comment describes npm’s postinstall behavior, and the test expects the setting.

Priority: External image Normal

Estimated code review effort: 2 (Simple) | ~8 minutes

Change: Bug fix · Severity of issue fixed: Medium

Suggested labels: size:S

Suggested reviewers: juliusmarminge, mnigos

The change aligns the Grok update environment with the stated npm 12 fix and is mergeable.

Check name	Status	Explanation
Title check	Passed	The title clearly identifies the Grok update fix and the npm 12 compatibility issue. It is concise, specific, and uses conventional commit wording.
Description check	Passed	The description includes all required sections: Problem, Change, Scope and approval, and Verification. It explains the failure, the implementation, linked issue approval, focused test results, runtime…
Linked Issues check	Passed	Issue #24249 requires the provider-card grok update path to allow @xai-official/grok scripts under npm 12. driver.ts now sets npm_config_allow_scripts to @xai-official/grok and spreads `cont…
Out of Scope Changes check	Passed	The diff changes only the Grok update environment and its focused test. The comment documents the npm 12 failure mode. These changes directly support issue #24249 and do not add unrelated settings, ca…

Full details: Description check

Explanation

The description includes all required sections: Problem, Change, Scope and approval, and Verification. It explains the failure, the implementation, linked issue approval, focused test results, runtime verification, limitations, and agent usage.

Full details: Linked Issues check

Explanation

Issue #24249 requires the provider-card grok update path to allow @xai-official/grok scripts under npm 12. driver.ts now sets npm_config_allow_scripts to @xai-official/grok and spreads context.env, so the nested postinstall can install the new binary while the instance environment remains present. The existing Homebrew cask branch is unchanged. driver.test.ts verifies the allowlist in the update action environment.

Full details: Out of Scope Changes check

Explanation

The diff changes only the Grok update environment and its focused test. The comment documents the npm 12 failure mode. These changes directly support issue #24249 and do not add unrelated settings, capabilities, or provider behavior.

🧪 Generate unit tests (beta)

• Create a new PR