Back to Signal Feed
CodeTracked since May 19, 2026

Use supported `reasoning` interleaved field for Cerebras Zai-GLM

The PR changes how reasoning text is sent for Cerebras by adding `reasoning` as an allowed `interleaved.field` and making Zai-GLM models default to that field, replacing top-level `reasoning_content` that Cerebras rejects.

Cerebras APIZai-GLMinterleaved.fieldreasoning_content

What Happened

  • The PR changes how reasoning text is sent for Cerebras by adding `reasoning` as an allowed `interleaved.field` and making Zai-GLM models default to that field, replacing top-level `reasoning_content` that Cerebras rejects.
  • The PR changes how reasoning text is sent for Cerebras by adding `reasoning` as an allowed `interleaved.field` and making Zai-GLM models default to that field, replacing top-level `reasoning_content` that Cerebras rejects.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Introduced API-compatibility fix for Cerebras by registering `reasoning` as a supported `interleaved.field` and switching default Zai-GLM behavior to send reasoning text through this supported path instead of `reasoning_content`.

Why Track This

Why It Matters

Cerebras users running Kilo-Org/kilocode with Zai-GLM no longer face request failures in reasoning workflows, so inference flows that include reasoning turns can continue without breaking API calls. This works by replacing the unsupported top-level `reasoning_content` payload with the supported inline `reasoning` interleaved field for Cerebras, so operators should watch whether any existing clients still emit `reasoning_content` and whether other provider profiles need equivalent field mappings to avoid new compatibility regressions.

Impact

Cerebras users running Kilo-Org/kilocode with Zai-GLM no longer face request failures in reasoning workflows, so inference flows that include reasoning turns can continue without breaking API calls. This works by replacing the unsupported top-level `reasoning_content` payload with the supported inline `reasoning` interleaved field for Cerebras, so operators should watch whether any existing clients still emit `reasoning_content` and whether other provider profiles need equivalent field mappings to avoid new compatibility regressions.

What To Watch Next

  • Watch whether Cerebras API becomes a repeated pattern.
  • Track follow-up changes around Tool Calling.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: legacy_reasoning_content_calls, zai_glm_default_field_behavior_regression.
Open Topic TimelineOpen Technical EventOpen Original Sourcelegacy_reasoning_content_calls / zai_glm_default_field_behavior_regression / provider_schema_drift

Supporting Evidence