Skip to content

bug: bedrock kimi-k2.5 can stop with no final assistant output #15137

Closed as not planned

Description

@jacksonwilliamsva

Description

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.

Plugins

None

OpenCode version

1.2.10

Steps to reproduce

  1. Configure model: amazon-bedrock/moonshotai.kimi-k2.5 (region: ap-southeast-2).
  2. Start a new session in plan mode.
  3. 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."
  4. Wait for tool activity to complete.
  5. Intermittently, the assistant stops with no final visible response.
  6. 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

Operating System

Bazzite

Terminal

Ptyxis

Activity

  1. added
    coreAnything pertaining to core functionality of the application (opencode server stuff)
    on Feb 26, 2026
  2. github-actions commented on Feb 26, 2026

    @github-actions
    Contributor

    This issue might be a duplicate of existing issues. Please check:

  3. jacksonwilliamsva commented on Feb 26, 2026

    @jacksonwilliamsva
    Author

    Thanks — this does look very similar to #14221 and #13807.
    I can confirm the same symptom pattern on my setup:

  4. assigned and unassigned on Apr 26, 2026
  5. removed
    bugSomething isn't working
    coreAnything pertaining to core functionality of the application (opencode server stuff)
    on May 3, 2026
  6. github-actions commented on Jul 4, 2026

    @github-actions
    Contributor

    To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions