Skip to content

[Bug] v1.14.28 DeepSeek V4 thinking mode: content[].thinking must be passed back to API in multi-turn conversations #24803

Closed

Description

@zzk203

Description

Bug Description

When using DeepSeek V4 Flash with thinking mode enabled, multi-turn conversations fail with:
Bad Request: {"error":{"message":"The content[].thinking in the thinking mode must be passed back to the API.","type":"invalid_request_error","param":null,"code":"invalid_request_error"}}

Environment

Steps to Reproduce

  1. Configure deepseek-v4-flash model with thinking mode enabled
  2. Start a conversation with the model
  3. First turn works fine - model responds
  4. Second turn (continuing the conversation) fails with the above 400 error

Expected Behavior

The thinking content should be preserved and passed back to the API in subsequent requests, allowing multi-turn conversations to work correctly.

Actual Behavior

The first API call succeeds, but the second call fails with a 400 error indicating that content[].thinking is not being passed back.

Additional Context

Plugins

No response

OpenCode version

No response

Steps to reproduce

No response

Screenshot and/or share link

session.json

Operating System

No response

Terminal

No response

Activity

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

    @github-actions
    Contributor

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

    Please review the above issues and comment there if your situation matches, to help consolidate the discussion.

  3. CHesketh76 commented on Apr 28, 2026

    @CHesketh76

    Running into the same issue on Version 1.14.28.

  4. zzk203 commented on Apr 28, 2026

    @zzk203
    Author
    Image

    Thank you, it works fine after adding interleaved. @rekram1-node

  5. zzk203 commented on Apr 28, 2026

    @zzk203
    Author

    Running into the same issue on Version 1.14.28.

    Image Try this.
  6. froooze commented on Apr 30, 2026

    @froooze
    Image
  7. rekram1-node commented on Apr 30, 2026

    @rekram1-node
    Collaborator

    @froooze please supply more information:

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

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingcoreAnything pertaining to core functionality of the application (opencode server stuff)

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions