Skip to content

Deepseek-API creates too many chat.deepseek.com conversations #11

Closed

Description

@42e6

Every time you send a post to 127.0.0.1:8000, Deepseek-API creates a new conversation and pastes the whole backlog of chat into it, over and over. This unnecessarily overloads Deepseek™'s resources, and creates a confusing list of conversations, where each conversation is only a single reply with the whole backlog uploaded again. It also quickly looks very SPAM-ish and unnecessarily triggers Deepseek™.

It would be nice if Deepseek-API develops the concept of session, where it submits posts in the same session to the same chat.deepseek.com conversation, without pasting the whole backlog again and again. Then, Deepseek can internally do its backlog compression and send to its models in ways it wants as per the chat.deepseek.com implementation.

Activity

  1. Repository owner deleted a comment from AmanCode22 on Oct 30, 2026
  2. sums001 commented on Oct 30, 2026

    @sums001
    Owner

    True and that's the default behavior, but you can use chat sessions to avoid that

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions