feat(usage-doc): update OpenCode config example with GPT-5.2 and Gemini v1beta by ding113 · Pull Request #597 · ding113/claude-code-hub

ding113 · 2026-01-12T16:56:00Z

Summary

Add OpenAI GPT-5.2 model configuration with reasoningEffort options
Add GPT-5.2-small variant using medium reasoning effort
Fix Gemini baseURL to use /v1beta endpoint
Update i18n strings across 5 languages to reflect different baseURLs per provider

Test plan

Verify usage-doc page renders correctly
Check i18n strings display properly in all 5 languages
Confirm OpenCode config example is valid JSON

Greptile Overview

Greptile Summary

This PR updates the OpenCode configuration documentation to add GPT-5.2 model support with reasoning effort options and fix the Gemini baseURL to use the v1beta endpoint. The i18n strings across all 5 languages were updated to reflect that different providers use different baseURL endpoints.

Changes Made

GPT-5.2 Configuration: Added gpt-5.2 and gpt-5.2-small models with reasoningEffort settings ("xhigh" for full model, "medium" for small variant)
OpenAI Options: Added store: false, setCacheKey: true, and include: ["reasoning.encrypted_content"] options
Gemini Endpoint: Updated cchGemini baseURL from /v1 to /v1beta
i18n Updates: Updated all 5 language files to document separate baseURLs per provider
Test Updates: Enhanced test expectations to validate new configuration features

Critical Issue Found

The implementation has a critical logic error that will cause:

Test failures: The test expects "npm": "@ai-sdk/openai" NOT to appear in output, but the code includes it
Runtime failures: Models reference openai/gpt-5.2 but provider is named cchGPT, causing model resolution to fail

Root cause: The GPT provider at line 1099 of page.tsx is named cchGPT, but the model references at lines 1083-1084 use openai/gpt-5.2 format. OpenCode's provider_id/model_id pattern requires these to match. The provider should be renamed from cchGPT to openai.

Architecture Fit

This change fits into the existing usage documentation pattern of providing complete configuration examples for CLI tools. The addition of GPT-5.2 reasoning models and the Gemini v1beta endpoint correction align with keeping documentation current with evolving API capabilities.

Confidence Score: 1/5

This PR has critical bugs that will cause test failures and runtime errors - NOT safe to merge as-is
Score of 1 reflects critical logic errors found during thorough analysis. The provider naming mismatch (cchGPT vs openai) will cause: (1) test suite to fail on line 73 of opencode-usage-doc.test.tsx which explicitly checks that "@ai-sdk/openai" should NOT be present, (2) OpenCode to fail at runtime when resolving models because "openai/gpt-5.2" references a non-existent provider named "openai". While the i18n translations are correct and the Gemini v1beta change is valid, the core configuration is broken. The fix is straightforward (rename cchGPT to openai) but essential before merge.
Critical attention needed on src/app/[locale]/usage-doc/page.tsx - provider naming must be fixed before merge. Test file and i18n files are fine.

Important Files Changed

File Analysis

Filename	Score	Overview
src/app/[locale]/usage-doc/page.tsx	1/5	Critical provider name mismatch: provider named `cchGPT` but model references use `openai/` prefix, causing resolution failure and test failures
tests/unit/usage-doc/opencode-usage-doc.test.tsx	5/5	Test expectations updated correctly to validate new GPT-5.2 config and Gemini v1beta URL, will fail due to code not matching
messages/en/usage.json	5/5	i18n updated correctly to document separate baseURLs for different providers, consistent with other languages

Sequence Diagram

sequenceDiagram
    participant User
    participant Browser
    participant UsageDocPage
    participant UsageDocContent
    participant OpenCodeConfig
    participant i18n

    User->>Browser: Navigate to /usage-doc
    Browser->>UsageDocPage: Render page
    UsageDocPage->>i18n: Load translations (en/ja/ru/zh-CN/zh-TW)
    i18n-->>UsageDocPage: Return usage.json messages
    UsageDocPage->>UsageDocContent: Pass origin and translations
    UsageDocContent->>OpenCodeConfig: Build config JSON
    Note over OpenCodeConfig: provider: cchClaude (v1)<br/>provider: cchGPT (v1) ❌<br/>provider: cchGemini (v1beta)<br/>model: "openai/gpt-5.2" ❌<br/>small_model: "openai/gpt-5.2-small" ❌
    OpenCodeConfig-->>UsageDocContent: Config JSON string
    UsageDocContent->>Browser: Render documentation with config example
    Browser-->>User: Display usage documentation
    
    Note over OpenCodeConfig: ISSUE: Provider "cchGPT" should be "openai"<br/>to match model references

…ni v1beta - Add OpenAI GPT-5.2 model configuration with reasoningEffort options - Add GPT-5.2-small variant using medium reasoning effort - Fix Gemini baseURL to use /v1beta endpoint - Update i18n strings to reflect different baseURLs per provider Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

coderabbitai · 2026-01-12T16:56:16Z

📝 Walkthrough

Walkthrough

此PR更新OpenCode配置文档和示例，跨越五个语言版本的消息文件明确了提供商基础URL映射（cchClaude/openai使用v1，cchGemini使用v1beta），并更新了GPT-5.2和Gemini配置，包含新的模型定义和推理参数。

Changes

类别 / 文件	变更摘要
多语言消息文件更新 `messages/en/usage.json`, `messages/ja/usage.json`, `messages/ru/usage.json`, `messages/zh-CN/usage.json`, `messages/zh-TW/usage.json`	更新OpenCode配置说明中的提供商baseURL指南：用明确的提供商映射替换通用指南（cchClaude/openai使用${resolvedOrigin}/v1；cchGemini使用${resolvedOrigin}/v1beta）；修改模型选择示例，新增openai/gpt-5.2范例。每个文件变更+2/-2
使用文档页面配置 `src/app/[locale]/usage-doc/page.tsx`	添加顶级字段model和small_model配置为openai/gpt-5.2；将gpt-5.2展开为详细对象，包含reasoningEffort、store和include字段；新增gpt-5.2-small模型定义；更新Gemini baseURL从v1改为v1beta；为cchGPT提供商添加store和setCacheKey选项
单元测试更新 `tests/unit/usage-doc/opencode-usage-doc.test.tsx`	移除对@ai-sdk/openai的npm入口期望；添加新模型配置期望（openai/gpt-5.2及gpt-5.2-small）；新增reasoningEffort值验证（xhigh和medium）；验证store:false和setCacheKey:true；验证reasoning.encrypted_content；添加Gemini baseURL为v1beta的断言

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

PR #545: 同样修改了usage-doc模型配置文件，标准化GPT-5.2模型命名和示例格式。
PR #582: 直接更新了OpenCode使用文档的配置内容（importantPoints和模型示例，以及Gemini baseURL），与此PR修改的文档内容存在直接重叠。

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: updating OpenCode config example with GPT-5.2 and Gemini v1beta, which aligns with the file changes across usage.json translations and the usage-doc page component.
Description check	✅ Passed	The description clearly summarizes the changeset including GPT-5.2 model configuration, GPT-5.2-small variant, Gemini baseURL fix, and i18n updates across 5 languages, directly relating to all modified files.

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

✨ Finishing touches

📝 Generate docstrings

🧪 Generate unit tests (beta)

Create PR with unit tests
Post copyable unit tests in a comment
Commit unit tests in branch feat/usage-doc-opencode-config-update

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

gemini-code-assist · 2026-01-12T16:56:17Z

Summary of Changes

Hello @ding113, I'm Gemini Code Assist¹! 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 focuses on enhancing the documentation and configuration examples for AI models within the application. It introduces new OpenAI GPT-5.2 model configurations, including a 'small' variant with specific reasoning efforts, and rectifies the base URL for the Gemini API to align with its '/v1beta' endpoint. Additionally, it ensures that these updates are accurately reflected in the internationalized usage documentation across multiple languages, improving clarity and correctness for users interacting with various AI providers.

Highlights

OpenAI GPT-5.2 Configuration: Added configuration for OpenAI GPT-5.2 model, including options for 'reasoningEffort'.
GPT-5.2-small Variant: Introduced a 'GPT-5.2-small' variant, configured with a medium reasoning effort.
Gemini Base URL Correction: Corrected the Gemini base URL to use the '/v1beta' endpoint, ensuring accurate API calls.
Internationalization Updates: Updated i18n strings across five languages to reflect the distinct base URLs for different providers.

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.

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. ↩

gemini-code-assist

Code Review

This pull request successfully updates the OpenCode configuration example to include the new GPT-5.2 models and corrects the Gemini baseURL. The corresponding internationalization strings and tests have also been updated. My review includes a critical fix for a test assertion that appears to be incorrect. Additionally, I've provided several suggestions to enhance the clarity of the configuration example and documentation text, which should improve the user experience.

gemini-code-assist · 2026-01-12T17:00:04Z

tests/unit/usage-doc/opencode-usage-doc.test.tsx

    expect(text).toContain('"npm": "@ai-sdk/anthropic"');
-    expect(text).toContain('"npm": "@ai-sdk/openai"');
    expect(text).toContain('"npm": "@ai-sdk/google"');
+    expect(text).not.toContain('"npm": "@ai-sdk/openai"');


This test assertion appears to be incorrect. The UsageDocContent component generates a configuration that includes "npm": "@ai-sdk/openai" for the cchGPT provider. Therefore, this not.toContain assertion will fail. It seems the original toContain was correct.

Suggested change

expect(text).not.toContain('"npm": "@ai-sdk/openai"');

expect(text).toContain('"npm": "@ai-sdk/openai"');

gemini-code-assist · 2026-01-12T17:00:04Z

messages/en/usage.json

          "Create an API key in the cch console and set the CCH_API_KEY environment variable",
-          "All providers use ${resolvedOrigin}/v1 as baseURL (cch v1 API base URL)",
-          "When selecting models, use provider_id/model_id (e.g. cchClaude/claude-sonnet-4-5-20250929)"
+          "cchClaude/openai use ${resolvedOrigin}/v1; cchGemini uses ${resolvedOrigin}/v1beta",


The phrasing cchClaude/openai use... could be slightly confusing, as it might be misinterpreted as a single provider named cchClaude/openai. To improve clarity, consider rephrasing to explicitly state that these are two separate providers.

Suggested change

"cchClaude/openai use ${resolvedOrigin}/v1; cchGemini uses ${resolvedOrigin}/v1beta",

"cchClaude and openai use ${resolvedOrigin}/v1; cchGemini uses ${resolvedOrigin}/v1beta",

gemini-code-assist · 2026-01-12T17:00:04Z

messages/ja/usage.json

          "cch の管理画面で API Key を作成し、環境変数 CCH_API_KEY を設定してください",
-          "3 つの provider すべてで baseURL は ${resolvedOrigin}/v1（cch の v1 API ベース URL）",
-          "モデル選択は provider_id/model_id 形式（例：cchClaude/claude-sonnet-4-5-20250929）"
+          "cchClaude/openai は ${resolvedOrigin}/v1、cchGemini は ${resolvedOrigin}/v1beta を baseURL に使用します",


The phrasing cchClaude/openai は... could be slightly confusing, as it might be misinterpreted as a single provider named cchClaude/openai. To improve clarity, consider rephrasing to explicitly state that these are two separate providers.

Suggested change

"cchClaude/openai は ${resolvedOrigin}/v1、cchGemini は ${resolvedOrigin}/v1beta を baseURL に使用します",

"cchClaude と openai は ${resolvedOrigin}/v1、cchGemini は ${resolvedOrigin}/v1beta を baseURL に使用します",

gemini-code-assist · 2026-01-12T17:00:04Z

messages/ru/usage.json

          "Создайте API key в панели cch и задайте переменную окружения CCH_API_KEY",
-          "Все provider используют ${resolvedOrigin}/v1 как baseURL (базовый URL cch v1 API)",
-          "При выборе модели используйте provider_id/model_id (например, cchClaude/claude-sonnet-4-5-20250929)"
+          "cchClaude/openai используют ${resolvedOrigin}/v1; cchGemini использует ${resolvedOrigin}/v1beta",


The phrasing cchClaude/openai используют... could be slightly confusing, as it might be misinterpreted as a single provider named cchClaude/openai. To improve clarity, consider rephrasing to explicitly state that these are two separate providers.

Suggested change

"cchClaude/openai используют ${resolvedOrigin}/v1; cchGemini использует ${resolvedOrigin}/v1beta",

"cchClaude и openai используют ${resolvedOrigin}/v1; cchGemini использует ${resolvedOrigin}/v1beta",

gemini-code-assist · 2026-01-12T17:00:04Z

messages/zh-CN/usage.json

          "请先在 cch 后台创建 API Key，并设置环境变量 CCH_API_KEY",
-          "三个 provider 的 baseURL 都使用 ${resolvedOrigin}/v1（cch v1 API 地址）",
-          "模型选择时使用 provider_id/model_id 格式（例如 cchClaude/claude-sonnet-4-5-20250929）"
+          "cchClaude/openai 使用 ${resolvedOrigin}/v1，cchGemini 使用 ${resolvedOrigin}/v1beta",


The phrasing cchClaude/openai 使用... could be slightly confusing, as it might be misinterpreted as a single provider named cchClaude/openai. To improve clarity, consider rephrasing to explicitly state that these are two separate providers.

Suggested change

"cchClaude/openai 使用 ${resolvedOrigin}/v1，cchGemini 使用 ${resolvedOrigin}/v1beta",

"cchClaude 和 openai 使用 ${resolvedOrigin}/v1，cchGemini 使用 ${resolvedOrigin}/v1beta",

gemini-code-assist · 2026-01-12T17:00:04Z

messages/zh-TW/usage.json

          "請先在 cch 後台創建 API Key，並設置環境變量 CCH_API_KEY",
-          "三個 provider 的 baseURL 都使用 ${resolvedOrigin}/v1（cch v1 API 地址）",
-          "模型選擇時使用 provider_id/model_id 格式（例如 cchClaude/claude-sonnet-4-5-20250929）"
+          "cchClaude/openai 使用 ${resolvedOrigin}/v1，cchGemini 使用 ${resolvedOrigin}/v1beta",


The phrasing cchClaude/openai 使用... could be slightly confusing, as it might be misinterpreted as a single provider named cchClaude/openai. To improve clarity, consider rephrasing to explicitly state that these are two separate providers.

Suggested change

"cchClaude/openai 使用 ${resolvedOrigin}/v1，cchGemini 使用 ${resolvedOrigin}/v1beta",

"cchClaude 和 openai 使用 ${resolvedOrigin}/v1，cchGemini 使用 ${resolvedOrigin}/v1beta",

coderabbitai

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In @tests/unit/usage-doc/opencode-usage-doc.test.tsx:
- Line 73: The test in tests/unit/usage-doc/opencode-usage-doc.test.tsx asserts
the serialized page content does NOT contain '"npm": "@ai-sdk/openai"', but the
cchGPT provider in page.tsx (the cchGPT configuration at/near the cchGPT
provider object) includes npm: "@ai-sdk/openai", so either remove that npm entry
from the cchGPT provider configuration or update the test assertion to expect
the string to be present (change expect(text).not.toContain('"npm":
"@ai-sdk/openai"') to expect(text).toContain('"npm": "@ai-sdk/openai"')). Locate
the cchGPT provider object in page.tsx and the failing assertion in
opencode-usage-doc.test.tsx and make the change so implementation and test
match.

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Cache: Disabled due to Reviews > Disable Cache setting

📥 Commits

Reviewing files that changed from the base of the PR and between c29eb7c and a3c8783.

📒 Files selected for processing (7)

messages/en/usage.json
messages/ja/usage.json
messages/ru/usage.json
messages/zh-CN/usage.json
messages/zh-TW/usage.json
src/app/[locale]/usage-doc/page.tsx
tests/unit/usage-doc/opencode-usage-doc.test.tsx

🧰 Additional context used

📓 Path-based instructions (5)

**/*.{js,ts,tsx,jsx}