Skip to content

Conversation

@USerik
Copy link

@USerik USerik commented Jan 16, 2026

The model mapping for 'z.ai coding plan' was incorrectly pointing to 'z-ai' instead of 'zai-coding-plan', which would cause model resolution failures when users selected the z.ai coding plan provider.

This fix ensures the correct model identifier is used for z.ai coding plan, aligning with the expected model naming convention.

Summary by CodeRabbit

  • Bug Fixes
    • Corrected provider identifier mapping to ensure proper recognition and integration of 'z.ai coding plan'.

✏️ Tip: You can customize this high-level summary in your review settings.

The model mapping for 'z.ai coding plan' was incorrectly pointing to 'z-ai'
instead of 'zai-coding-plan', which would cause model resolution failures
when users selected the z.ai coding plan provider.

This fix ensures the correct model identifier is used for z.ai coding plan,
aligning with the expected model naming convention.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @USerik, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request resolves a critical bug where the 'z.ai coding plan' provider was misconfigured with an incorrect model identifier. The fix updates this mapping to the correct value, preventing potential model resolution failures and ensuring the system functions as expected for users of this specific provider.

Highlights

  • Model Mapping Correction: The model mapping for 'z.ai coding plan' was incorrectly set to 'z-ai'.
  • Resolution of Model Failures: The incorrect mapping could cause model resolution failures when users selected the 'z.ai coding plan' provider.
  • Updated Mapping: The mapping has been corrected to 'zai-coding-plan' to align with the expected model naming convention.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@coderabbitai
Copy link

coderabbitai bot commented Jan 16, 2026

📝 Walkthrough

Walkthrough

A provider mapping value in OpencodeProvider is updated to correct the identifier for 'z.ai coding plan' from 'z-ai' to 'zai-coding-plan', affecting the internal providerIdMap used during provider output parsing.

Changes

Cohort / File(s) Summary
Provider ID Mapping Update
apps/server/src/providers/opencode-provider.ts
Updated providerIdMap entry: 'z.ai coding plan' now maps to 'zai-coding-plan' (previously 'z-ai')

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A mapping was tweaked, oh what a sight,
From 'z-ai' to 'zai-coding-plan' so right,
One little string, precisely aligned,
The provider now perfectly defined! ✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately reflects the main change: correcting the z.ai coding plan model mapping from 'z-ai' to 'zai-coding-plan'.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
  • 📝 Generate docstrings


📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 78e5ddb and 9f9f32a.

📒 Files selected for processing (1)
  • apps/server/src/providers/opencode-provider.ts
🧰 Additional context used
📓 Path-based instructions (3)
**/*.{ts,tsx,js,jsx}

📄 CodeRabbit inference engine (CLAUDE.md)

Always import from shared packages (@automaker/*), never from old relative paths

Files:

  • apps/server/src/providers/opencode-provider.ts
apps/server/src/**/*.{ts,tsx}

📄 CodeRabbit inference engine (CLAUDE.md)

Use createEventEmitter() from lib/events.ts for all server operations to emit events that stream to frontend via WebSocket

Files:

  • apps/server/src/providers/opencode-provider.ts
**/*.{ts,tsx}

📄 CodeRabbit inference engine (CLAUDE.md)

Use resolveModelString() from @automaker/model-resolver to convert model aliases (haiku, sonnet, opus) to full model names

Files:

  • apps/server/src/providers/opencode-provider.ts
🔇 Additional comments (1)
apps/server/src/providers/opencode-provider.ts (1)

1038-1040: LGTM! Correct fix for the z.ai coding plan provider mapping.

The fix properly distinguishes between the base z.ai provider (mapped to z-ai) and the specific z.ai coding plan (now correctly mapped to zai-coding-plan). This ensures correct model resolution when users authenticate with the z.ai coding plan.

✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request correctly fixes a model mapping for 'z.ai coding plan' in the OpenCode provider, which was causing model resolution failures. The change is straightforward and addresses the issue described. My main feedback is to improve test coverage for the parseProvidersOutput method to prevent similar issues in the future.

lmstudio: 'lmstudio',
opencode: 'opencode',
'z.ai coding plan': 'z-ai',
'z.ai coding plan': 'zai-coding-plan',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

While this change correctly fixes the mapping, the parseProvidersOutput function lacks unit tests. To prevent regressions and ensure the robustness of provider parsing, I recommend adding tests for this logic in apps/server/tests/unit/providers/opencode-provider.test.ts. A test case could verify that 'z.ai coding plan' correctly maps to 'zai-coding-plan' and that other providers are also mapped as expected.

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