Skip to content

chore(opencode): use NVIDIA NIM only - #902

Open
seonghobae wants to merge 9 commits into
mainfrom
cursor/opencode-nvidia-nim-only-26ed
Open

chore(opencode): use NVIDIA NIM only#902
seonghobae wants to merge 9 commits into
mainfrom
cursor/opencode-nvidia-nim-only-26ed

Conversation

@seonghobae

@seonghobae seonghobae commented Aug 16, 2026

Copy link
Copy Markdown
Collaborator

Summary

ContextualWisdomLab no longer uses GitHub Models. This PR rewrites the repo OpenCode config so inference is NVIDIA NIM only.

  • Default model: nvidia-nim/nvidia/llama-3.3-nemotron-super-49b-v1.5
  • Small model: nvidia-nim/meta/llama-3.3-70b-instruct
  • Provider: nvidia-nim at https://integrate.api.nvidia.com/v1
  • Auth: {env:NVIDIA_API_KEY} (org secret NVIDIA_NIM_API_KEY is aliased to this name)
  • enabled_providers: ["nvidia-nim"]
  • share: "disabled" and lsp: false to match the org NIM-only OpenCode template

Removed github-models, openai/gpt-5, STRIX_GITHUB_MODELS_TOKEN, and any COPILOT_GITHUB_TOKEN path. Existing MCP servers (codegraph, deepwiki, context7, web_search) are unchanged.

Also hardens a flaky frontend coverage test that raced 열기 buttons against vi.useFakeTimers(), which failed ci / frontend on the previous head.

Test plan

  • opencode.jsonc parses as JSON
  • Repo-wide search has no github-models, openai/gpt-5, STRIX_GITHUB_MODELS_TOKEN, or COPILOT_GITHUB_TOKEN
  • Provider base URL is https://integrate.api.nvidia.com/v1 and the API key is {env:NVIDIA_API_KEY}
  • npm run test -- src/App.coverage.test.tsx (17 passed)
  • Required OpenCode Review and ci / frontend succeed on the latest head
Open in Web Open in Cursor 

Replace GitHub Models with nvidia-nim at integrate.api.nvidia.com/v1,
authenticated by NVIDIA_API_KEY. Drop STRIX_GITHUB_MODELS_TOKEN and
COPILOT_GITHUB_TOKEN so OpenCode follows the org NIM-only policy.

Co-authored-by: Seongho Bae <[email protected]>
@seonghobae
seonghobae marked this pull request as ready for review August 16, 2026 16:12
@cursor

cursor Bot commented Aug 16, 2026

Copy link
Copy Markdown

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

@coderabbitai

coderabbitai Bot commented Aug 16, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 52 minutes

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

Wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: a2ac6657-5a56-47e0-bdb3-94fe2471a11a

📥 Commits

Reviewing files that changed from the base of the PR and between 729eacc and 57ff321.

📒 Files selected for processing (2)
  • frontend/src/App.coverage.test.tsx
  • opencode.jsonc

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.

cursor[bot]
cursor Bot previously approved these changes Aug 16, 2026

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Review (head 38f4d238)

Repo-local opencode.jsonc now defaults to NVIDIA NIM only:

  • nvidia-nim/nvidia/llama-3.3-nemotron-super-49b-v1.5
  • nvidia-nim/meta/llama-3.3-70b-instruct
  • Provider https://integrate.api.nvidia.com/v1

GitHub Models leftovers (github-models, openai/gpt-5, STRIX_GITHUB_MODELS_TOKEN, COPILOT_GITHUB_TOKEN) are gone. Review-agent key systems are untouched. JSONC is valid JSON. Catalog IDs and 128K context limits match the current NIM cards.

{env:NVIDIA_API_KEY} is the official NVIDIA SDK / OpenCode env name. Org runners bind secrets.NVIDIA_NIM_API_KEYNVIDIA_API_KEY. This is the documented alias, not a contract defect. Do not rewrite it to {env:NVIDIA_NIM_API_KEY} or local OpenCode and existing reusable workflows will miss the key.

Non-blocking follow-ups (not merge blockers):

  • Hosted catalog pages mark both model IDs deprecated on 2026-08-25; bump when the org catalog moves.
  • reasoningEffort: "high" is OpenAI-shaped metadata and may be a no-op on NIM (Nemotron uses an empty system prompt vs /no_think).

Next buyer-facing gap after this config PR: collision-free Prisma identifier allocation (#898).

Open in Web View Automation 

Sent by Cursor Automation: Fix Issues

Comment thread opencode.jsonc Outdated
Align with the org NIM-only OpenCode template so a new synchronize
retriggers the cancelled Required OpenCode Review bootstrap.

Co-authored-by: Seongho Bae <[email protected]>
The auto-layout coverage test raced: it switched to fake timers before
the diagram list rendered, so CI could miss the 열기 button. Wait for
those buttons with real timers first, matching the other diagram tests.

Co-authored-by: Seongho Bae <[email protected]>
@seonghobae

Copy link
Copy Markdown
Collaborator Author

@opencode-agent review

Please review exact current head b8ce0c3. Re-evaluate this head only; do not transfer predecessor approvals or check evidence.

@seonghobae
seonghobae enabled auto-merge August 20, 2026 04:51
@opencode-agent

Copy link
Copy Markdown
Contributor

Queued @opencode-agent for PR #902 at head 78c6da9bf44b664018016c8ff2103a900867f072. Central exact-name Actions artifacts are the durable dispatch ledger; existing review workflows remain authoritative for the final verdict and failure evidence.

@opencode-agent

Copy link
Copy Markdown
Contributor

Already queued @opencode-agent on this exact request for PR #902 at head 78c6da9bf44b664018016c8ff2103a900867f072. Central exact-name Actions artifacts are the durable dispatch ledger; existing review workflows remain authoritative for the final verdict and failure evidence.

@opencode-agent

Copy link
Copy Markdown
Contributor

Queued @opencode-agent for PR #902 at head 57ff32131c7a28d9d5ed146325a327c687b1ea49. Central exact-name Actions artifacts are the durable dispatch ledger; existing review workflows remain authoritative for the final verdict and failure evidence.

@opencode-agent

Copy link
Copy Markdown
Contributor

Already queued @opencode-agent on this exact request for PR #902 at head 57ff32131c7a28d9d5ed146325a327c687b1ea49. Central exact-name Actions artifacts are the durable dispatch ledger; existing review workflows remain authoritative for the final verdict and failure evidence.

2 similar comments
@opencode-agent

Copy link
Copy Markdown
Contributor

Already queued @opencode-agent on this exact request for PR #902 at head 57ff32131c7a28d9d5ed146325a327c687b1ea49. Central exact-name Actions artifacts are the durable dispatch ledger; existing review workflows remain authoritative for the final verdict and failure evidence.

@opencode-agent

Copy link
Copy Markdown
Contributor

Already queued @opencode-agent on this exact request for PR #902 at head 57ff32131c7a28d9d5ed146325a327c687b1ea49. Central exact-name Actions artifacts are the durable dispatch ledger; existing review workflows remain authoritative for the final verdict and failure evidence.

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