You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
bug: bedrock kimi-k2.5 can stop with no final assistant output #15137
Using OpenCode with amazon-bedrock/moonshotai.kimi-k2.5, responses can stop silently after tool activity. The run appears to complete internally, but no final assistant text is shown to the user.
Send a broad analysis prompt, e.g.:
"Audit this repository and produce a complete 3-part plan: architecture assessment, implementation roadmap, and risk register. First explore all docs/config/source files, then return one final consolidated report."
Wait for tool activity to complete.
Intermittently, the assistant stops with no final visible response.
Export the session and inspect the final assistant message.
Screenshot and/or share link
No share link (private repository).
Sanitized evidence from session exports:
providerID: amazon-bedrock
modelID: moonshotai.kimi-k2.5
mode: plan
one run shape:
assistant message A: finish="tool-calls" with successful tool results
assistant message B: finish="stop", output tokens > 0, but parts contain only step-start/step-finish and no text part
another run shape:
task tool state.status="completed"
task tool output is empty wrapper: "<task_result>...</task_result>" (no content)
parent assistant then ends with finish="stop" and no user-visible text
Activity
github-actions commentedon Feb 26, 2026
This issue might be a duplicate of existing issues. Please check:
jacksonwilliamsva commentedon Feb 26, 2026
Thanks — this does look very similar to #14221 and #13807.
I can confirm the same symptom pattern on my setup:
In my sanitized export:
If this is already tracked/fixed in Kimi K2.5 on AWS Bedrock: multiple failures — premature end_turn, silent stops, and toolResult format errors #14221 or Kimi K2.5 on Bedrock: premature end_turn due to Converse API tool call parsing bugs #13807, happy to close this as duplicate.
github-actions commentedon Jul 4, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.