Feature request: let one bot run tasks from different groups in parallel, or let the owner pick which queued task goes first
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- backend, developer-experience
Research direction
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.
Written by the indexing model from the issue text.
Description
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
- 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).
- 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.
- Let the owner reorder the queue or press "do this first", which pauses the current task at the next step boundary.
- When a task has waited more than a few minutes, tell the group who it is waiting on and why, instead of staying silent.
- Dominant language
- TypeScript
- Stars
- 277
- Forks
- 27
- Avg merge
- 2h 47m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from DuskBotAI/duskbot
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 1 day
-
After uninstalling an own server, the desktop app stays on it and shows Cloudflare's Error 1033 pageOpen
Difficulty 3/5 1-2 days Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
install.sh --tailscale replaces whatever the host already serves on tailnet port 443Possibly taken @viniciusbregoli claimed this today. Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
All issues in DuskBotAI/duskbot
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vercel-labs/ui#865 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
outline/outline#14638 · 1 comment ·
Maintainers usually reply within 1 day
-
wayfinder:grilling
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
patricktree/cup#484 ·
-
bot:ai-assisted component:platform-js status:untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
midnightntwrk/platform-js#69 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day