You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
三个增强:群聊429自动唤醒、可编辑排队任务、完整推理/工具过程展示; Three enhancements: group wake on 429, editable queued tasks, full reasoning/tool transcript
#207
验证情况:npm test 560/560(新增 11 个测试),lint 0 错误,build-client --check 干净,另外在 Windows 上对原始 dev 做了 A/B 冒烟测试(结果一致;唯一失败的步骤 work_dir 保存,在未改动的 dev 上也能复现)。
我知道现在 PR 只开放给 collaborator。这些改动你们愿意直接收进 dev 当 PR 吗?还是希望我先按功能分别开 issue?需要的话我也可以把这个分支拆成三个独立 PR。
I run a team of Bots with DS Bot and built three enhancements on top
of the current dev (base f346351). Branch with the full change (22 files,
tests included): https://github.com/IIs-fanta/DeepSeek-Bot/tree/feat/team-resilience
Group chats wake a member that drops. A transient model failure (429,
transport, server, timeout) no longer ends a member's turn: the round
retries with backoff (20s/40s, bounded), shows a "waking it again"
line, and a member that failed after the round moved on is nudged to
pick its work back up before any failure is posted. Permanent failures
(quota, auth) still post at once.
edit_queued_message: every Bot can list / replace / cancel its own
messages still waiting unread in another Bot's inbox. When a queued
task changes direction, the task itself is rewritten in place (DSH
inbox replace(), keeps queue position, reply route and resume note)
instead of queueing a correction behind it.
Bot chats show the whole turn: per-step reasoning streams live, and
every ordinary tool call renders as a DSH-style disclosure row with
input/output; PTC sub-calls nest. Team tools keep their event lines;
hidden Bot-to-Bot turns stay hidden.
Verified: npm test 560/560 (11 new tests), lint 0 errors,
build-client --check clean, plus an A/B smoke bench against pristine dev
on Windows (identical results; the only failing step, work_dir saving,
reproduces on unmodified dev).
I know PRs are currently collaborator-only — would you accept these as
PR(s) into dev, or should I open separate issues per feature first? I can
split the branch into three PRs if preferred.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
基于当前的 dev(base f346351)做了三个增强。完整改动的分支在这(22个文件,测试也都带了):
https://github.com/IIs-fanta/DeepSeek-Bot/tree/feat/team-resilience
群聊里成员掉线会自动唤醒。遇到临时模型故障(429、传输问题、服务器错误、超时)不会直接结束这个成员的回合了:会带退避重试(20s/40s,有上限),并显示一句“再叫醒它一次”。如果某个成员在回合已经往下走之后才失败,也会被推一把,让它把活捡起来,再失败才会正式报错。永久失败(配额、鉴权这类)还是立刻报。
新增 edit_queued_message:每个 Bot 都能列出 / 替换 / 取消自己还在别人收件箱里未读的消息。当一个排队任务方向变了,会直接原地改写这个任务本身(用 DSH 收件箱的 replace(),队列位置、回复路由和 resume note 都保留),而不是再往后面塞一条修正消息。
Bot 聊天会把整个回合完整展示出来:每一步的推理会实时流式输出,普通工具调用会按 DSH 风格的折叠行显示输入/输出;PTC 子调用会嵌套显示。团队工具还是原来的事件行;隐藏的 Bot 对 Bot 回合继续保持隐藏。
验证情况:npm test 560/560(新增 11 个测试),lint 0 错误,build-client --check 干净,另外在 Windows 上对原始 dev 做了 A/B 冒烟测试(结果一致;唯一失败的步骤 work_dir 保存,在未改动的 dev 上也能复现)。
我知道现在 PR 只开放给 collaborator。这些改动你们愿意直接收进 dev 当 PR 吗?还是希望我先按功能分别开 issue?需要的话我也可以把这个分支拆成三个独立 PR。
I run a team of Bots with DS Bot and built three enhancements on top
of the current dev (base f346351). Branch with the full change (22 files,
tests included):
https://github.com/IIs-fanta/DeepSeek-Bot/tree/feat/team-resilience
Group chats wake a member that drops. A transient model failure (429,
transport, server, timeout) no longer ends a member's turn: the round
retries with backoff (20s/40s, bounded), shows a "waking it again"
line, and a member that failed after the round moved on is nudged to
pick its work back up before any failure is posted. Permanent failures
(quota, auth) still post at once.
edit_queued_message: every Bot can list / replace / cancel its own
messages still waiting unread in another Bot's inbox. When a queued
task changes direction, the task itself is rewritten in place (DSH
inbox replace(), keeps queue position, reply route and resume note)
instead of queueing a correction behind it.
Bot chats show the whole turn: per-step reasoning streams live, and
every ordinary tool call renders as a DSH-style disclosure row with
input/output; PTC sub-calls nest. Team tools keep their event lines;
hidden Bot-to-Bot turns stay hidden.
Verified: npm test 560/560 (11 new tests), lint 0 errors,
build-client --check clean, plus an A/B smoke bench against pristine dev
on Windows (identical results; the only failing step, work_dir saving,
reproduces on unmodified dev).
I know PRs are currently collaborator-only — would you accept these as
PR(s) into dev, or should I open separate issues per feature first? I can
split the branch into three PRs if preferred.
All reactions