Add graceful fallback for missing response.id from NVIDIA NIM

[chindris-mihai-alexandru]

Description
OpenCode crashes with AI_InvalidResponseDataError: Expected "id" to be a string when the NVIDIA NIM endpoint returns a tool‑call response without an id field.

Reproduction steps

1. Obtain a valid NVIDIA_NIM_KEY.
2. Run the curl command from the NVIDIA issue (see that issue for the exact command).
3. The raw JSON response from NIM does not contain an id property.
4. OpenCode validates the payload and throws the error.

Expected behaviour
If the id field is missing or not a string, the integration should automatically generate a temporary UUID (e.g., msg_<uuid>) and continue processing instead of aborting.

Suggested implementation

function normalizeMistralResponse(resp: any): any {
  if (!resp.id || typeof resp.id !== "string") {
    resp.id = `msg_${crypto.randomUUID()}`;
  }
  return resp;
}

Add this guard before any SDK validation that expects id.

Impact
All users who call any NVIDIA NIM model from OpenCode will stop crashing.

Environment

• OpenCode version: 1.0.191
• NVIDIA NIM endpoint: https://integrate.api.nvidia.com/v1/chat/completions
• Model: Devstral-2-123B-Instruct-2512
• Date: 2025‑12‑28

[chindris-mihai-alexandru]

Related NVIDIA issue: NVIDIA/nim-deploy#182

[stromseng]

Related similar GLM 4.7 and others issue: #1880

[TimothyStiles]

It's just a hot-fix until something more permanent gets merged but I managed to solve the nvidia nim tool usage issues for myself with this plugin I put together.

[ltngonnguyen]

It's just a hot-fix until something more permanent gets merged but I managed to solve the nvidia nim tool usage issues for myself with this plugin I put together.

I tried installing your solution but it didn't work:

[TimothyStiles]

It's just a hot-fix until something more permanent gets merged but I managed to solve the nvidia nim tool usage issues for myself with this plugin I put together.

I tried installing your solution but it didn't work:

@ltngonnguyenI patched the issue and am waiting for NPM to update. If it doesn't work in 24 hours open an issue on the repo.