OpenCode
OpenCode reasoning part or summaryParts parsing error
This error is not necessarily an API Key problem; separate config, adapter, upstream stream, and UI layers.
Start with these checks
The request may have succeeded, but OpenCode failed to parse streamed content.
- The error mentions reasoning part/text part not found, summaryParts, or a blank reply.
- The Provider points to the wrong interface format
- Confirm Provider, Base URL, and Model ID match
reasoning part/text part not foundsummaryParts01
Rule out Provider config first
Compare Provider ID, Base URL, and Model ID. Any mismatch can produce events the client does not expect.
02
Check adapter and interface format
Keep the npm adapter aligned with the generated config; a mismatch can prevent valid parts from being assembled.
- 1Confirm Provider, Base URL, and Model ID match
- 2Confirm the npm adapter came from the generated config
03
Separate upstream from client parsing
If the service has a result but parsing fails, keep the stream error and report a minimal reproduction instead of rotating the API Key.
- 1Confirm the npm adapter came from the generated config
- 2Retest with a short message and keep the full error
If it is still not fixed
Sources
Reconfigure
Return to the integration center and continue the setup steps.
Return to the related setup step