chore: bump GLM to 5.2, refresh grok/mimo slugs, drop legacy Gemini CLI#17
Open
kulvirgit wants to merge 1 commit into
Open
chore: bump GLM to 5.2, refresh grok/mimo slugs, drop legacy Gemini CLI#17kulvirgit wants to merge 1 commit into
kulvirgit wants to merge 1 commit into
Conversation
kulvirgit
force-pushed
the
chore/glm-5.2-drop-gemini
branch
2 times, most recently
from
ace13d5 to
b05228f
Compare
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (10 files)
Verified:
Previous Review Summaries (2 snapshots)Current summary above is authoritative. Previous snapshots are kept for context only. Previous reviewStatus: No Issues Found | Recommendation: Merge Files Reviewed (10 files)
Verified:
Previous review (commit b05228f)Status: No Issues Found | Recommendation: Merge Files Reviewed (10 files)
Verified:
Reviewed by glm-5.2 · Input: 40.9K · Output: 12.3K · Cached: 272.7K |
kulvirgit
force-pushed
the
chore/glm-5.2-drop-gemini
branch
from
b05228f to
f79fd61
Compare
- Update `glm5` from GLM-5.1 to GLM-5.2 (`zai-coding-plan/glm-5.2`) in both default configs, the Claude setup wizard, the Codex setup reference, and the README panel table. - Refresh two stale model slugs that 404 on OpenRouter: `grok-4.20-beta` → `grok-4.3`, `mimo-v2-pro` → `mimo-v2.5-pro`. - Remove the legacy bare-`gemini` CLI compatibility paths from the command specs and skill references (preflight `gemini` legacy branch, "or legacy `gemini`" qualifiers, and the `command: "gemini"` migration notes). Gemini stays as a model, executed via the Antigravity CLI (`agy`) — only the deprecated bare-`gemini` handling is dropped. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
kulvirgit
force-pushed
the
chore/glm-5.2-drop-gemini
branch
from
f79fd61 to
5a66388
Compare
kulvirgit
changed the title
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
1 participant
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.
Summary
zai-coding-plan/glm-5.2) across both default configs, the Claude setup wizard, the Codex setup reference, and the README panel table.grok-4.20-beta→grok-4.3,mimo-v2-pro→mimo-v2.5-pro.geminiCLI handling only. Gemini stays as a model, executed via the Antigravity CLI (agy, shipped in [codex] migrate Gemini native CLI to Antigravity #15). This removes just the deprecated bare-geminicompatibility: the preflightgeminilegacy branch, the "or legacygemini" qualifiers on theagypaths, and thecommand: "gemini"→agymigration notes.Gemini +
agyare not removed. No models added/removed, so quorum is unchanged (Claude 10, Codex 8).Test plan
glm-5.2,grok-4.3,mimo-v2.5-prosmoke-tested viakilo run→ all return PONGagyexecution paths still present in all command specs and skill referencesgeminimodel entry retained in both configslegacy gemini/ bare-gemini-CLI references remain