Feature request: let one bot run tasks from different groups in parallel, or let the owner pick which queued task goes first

未关闭
#26 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
typescript

调研方向

Start by locating the bot task queue and execution flow, then trace how group tasks are scheduled and how the group and bot pages display task status. The proposal spans parallel sessions, queue visibility and controls, and wait notifications; done means these behaviors work together while the default per-bot concurrency remains 1.

由索引模型根据 Issue 内容生成。

描述

Version

0.2.15

Problem

A bot that is a member of several groups only works on one task at a time. On 17 Nov bikinin was in both "Deck Sales Kit Miso" and "Miso Cover Reels". Its deck revision turn started 18:11 WIB and was still running at 18:37 (152 tool calls, still making progress). The Cover Reels task it got at 18:11 sat in its queue the whole time, so the Cover Reels group (and the owner) waited about 30 minutes with no visible work. The other group member could only answer "waiting for its turn in the queue".

The groups themselves do run in parallel (Cover Reels and Deck turns overlap in the trail log), so the bottleneck is the per-bot single queue, and it is invisible in the UI.

Proposal
  1. Allow a bot to run up to N tasks in parallel when they come from different groups or threads (each in its own session/workspace subfolder), with N set per bot (default 1 for safety, 2 or 3 opt-in).
  2. Show the bot's queue in the group and in the bot's page: what it is doing now, what is waiting, and since when.
  3. Let the owner reorder the queue or press "do this first", which pauses the current task at the next step boundary.
  4. When a task has waited more than a few minutes, tell the group who it is waiting on and why, instead of staying silent.
主要语言
TypeScript
星标
277
派生
27
平均合并
2 小时 47 分钟
30 天内合并 PR
1

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

DuskBotAI/duskbot 的其他 Issue

查看 DuskBotAI/duskbot 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。