Skip to content

Multiple Bot cluster accumulates messages under idle state; partial Bots get stuck in thinking state and fail to process queued messages #129

Closed

Description

@shiehXJ

What happened? / 发生了什么?

When setting up multiple teams comprising approximately 13 bots, a total of 179 inter-bot messages accumulated over a 15-minute period. The bots were working frantically (even though the "Chief" had not explicitly assigned tasks), while three bots became stuck with messages continuously queuing; specifically, one bot had a queue of 16 messages and remained in a state of "thinking" without actually processing them.

Screenshot (strongly recommended) / 截图(强烈建议)

Image Image

Steps to reproduce / 复现步骤

  1. Create team structure: One top-level team containing three sub-teams (Test Team, Dev Team, Product Team). Each sub-team has its own Chief who can only schedule bots within the sub-team. The top-level team has a Chief responsible for scheduling all bots under the parent team.
  2. Import a project and send it to the Chiefs. Configure corresponding skills and accessible platforms for each bot.
  3. Observe that bots start generating excessive continuous inter-bot conversations spontaneously.

Diagnostics / 诊断信息

DS Bot 0.1.2
DSH 0.2.0-rc.2
Surface DSH Desktop
OS darwin 25.5.0 arm64
Node v24.18.1
Browser Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) @deepseek-ai/dsh-desktop/0.2.0-rc.2 Chrome/152.0.7977.54 Electron/44.0.0 Safari/537.36
Language zh
Team 17 Bots, 1 Main, 4 group chats
Models deepseek-official/deepseek-flash

Recent host errors (4 of 4, oldest first):

2026-10-13T11:35:48.394Z WARN host memory review of session-f99636c0-d93a-41cb-864a-eddbd1b4bdcd failed: the model's answer holds an entry memory cannot keep: An entry holds at most 300 characters; this one has 305. Keep one fact per entry, or save the details as several entries in a topic.
2026-10-13T11:51:16.407Z WARN host memory review of Chief left out a change: Your memory's MEMORY.md would have 4078 of its 4000 characters. Make room first: move details into a topic (remember with topic, then forget them here), merge entries with replace, or forget what no longer matters.
2026-10-13T11:51:16.408Z WARN host memory review of Chief left out a change: Your memory's MEMORY.md would have 4055 of its 4000 characters. Make room first: move details into a topic (remember with topic, then forget them here), merge entries with replace, or forget what no longer matters.
2026-10-13T11:51:16.408Z WARN host memory review of session-3e9e6e94-2b88-4035-b322-ab983bcfce1a failed: Your memory's MEMORY.md would have 4078 of its 4000 characters. Make room first: move details into a topic (remember with topic, then forget them here), merge entries with replace, or forget what no longer matters.

Privacy / 隐私

  • This report has no API keys, tokens or personal data. / 报告里没有 API key、token 或个人信息。

Activity

  1. Fei2411 commented on Oct 13, 2026

    @Fei2411
    Owner

    Fixed by #130 and #136.

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

    bugSomething isn't working

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions