Update Grok for 0.2.118 - #469
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
grok-4.5model-sfor truly unmaterialized sessionsWhy
Grok 0.2.118 retired the previous Composer utility model, recommends
--no-auto-updatefor automated ACP/headless use, and can resume UUID sessions independently of the current directory. Poracode's cwd-local materialization check could incorrectly reuse-safter a project move, creating a blank duplicate instead of resuming the durable conversation.Validation
pnpm exec vitest run src/supervisor/agents/grok src/supervisor/agents/commandBuilders.test.ts— 100 passedpnpm run typecheckpnpm run lintpnpm run fmt:checkpnpm run test— 7,945 passed; two unrelated Windows Cursor temp-directory cleanup tests hitEPERM, then the isolated file rerun passed 8/8 with 2 skipped