starslittle/dsh-queue-plus
DSH 排队消息增强面板：编辑、删除、插话、排序与批量删除功能
Listed
15
Session
Bundle verified
Preview
What it does
A simple DSH queue panel for editing, removing, steering, reordering, and bulk removal.
Best for
- DSH Web users who frequently queue messages and need to edit, remove, steer, or reorder them before execution.
- Touch or keyboard workflows that benefit from bulk removal and explicit up/down ordering controls.
- Queues where concurrent-change protection should reject stale reorder attempts instead of applying an incorrect order.
Not ideal for
- Workflows that need to manage steering or context queues rather than the regular message queue.
- Managing subagent queues owned by a parent Agent.
- Bulk deletion that must include messages added after confirmation; only messages visible at confirmation time are targeted.
- DSH versions whose Web plugin contract has diverged from the documented rc.6 target.
README
dsh-queue-plus
| English | 简体中文 |
一个更好用的 DSH 排队消息面板：编辑、删除、插话、排序和批量删除。
Queue Plus 使用 DSH 官方插槽接管 QueueDock，不隐藏或复制排队消息；停用或卸载插件后，官方队列会自动恢复。
功能
- 编辑、删除或插话发送排队消息。
- 拖动消息，或使用上下箭头调整执行顺序。
- 一键批量删除，确认后按 DSH 官方方式逐条处理。
- 新队列自动展开，并记住手动收起状态。
- 支持中文、英文、键盘和触屏操作。
安装
推荐安装 Release 中的预构建包，无需授权安装脚本：
dsh plugin --profile web add -w https://github.com/starslittle/dsh-queue-plus/releases/download/v0.3.0/dsh-queue-plus-0.3.0.tgz
重启 dsh web。运行中连续发送至少两条“排队”消息，队列标题旁会出现“排序”。
装完怎么验
| 现象 | 怎么办 |
|---|---|
| 排队两条后标题旁出现「排序」 | 已生效 |
| 没有「排序」 | 确认已重启，并选「排队发送」而不是马上发送 |
| 关掉或卸载后队列变回原样 | 正常 |
边界
- 单条和批量删除都调用 DSH 官方
conversation.updateQueue(..., { kind: 'remove' })。 - 删除全部只处理确认时可见的消息；并发变化时可能部分完成，不会误删随后加入的消息。
- 排序使用服务端确认和并发保护；若队列已经变化，本次排序会拒绝而不是排乱。
- 不操作 steering / context 队列，也不管理父 Agent 所有的 subagent 队列。
- 卸载后官方队列自动恢复。
Frequently Asked QuestionsFAQ
Use the verified command dsh plugin --profile default add github:starslittle/dsh-queue-plus in a DSH-enabled shell. The command resolves the public package metadata and keeps the plugin attached to the catalog identity shown on this page.
Compatibility follows the bundle and profile status shown above. If a profile is not detected, keep the plugin disabled there and check the repository documentation before enabling it in production.
The GitHub link and activity metadata are the source of truth for releases and maintenance. Revisit this page after a new release to confirm the catalog has observed the latest version.