mirror of
https://github.com/hansjone/dsh-im-ops.git
synced 2026-10-10 06:30:46 +08:00
e1bc9dd0d0
Show what the agent is actually doing during a turn, the way Claude Code does: interim explanation text, every Tool call, and the error detail when a tool fails, each as its own pushed message before the final markdown answer. - HarnessReplyTracker.consume now returns every frame of a polling batch in order (same-batch text frames collapse to the latest) instead of dropping all but the last event, which silently ate tool-call frames that shared a batch with their result - tool frames carry callId; status frames carry the correlated toolName and a flattened error text parsed from the tool/result error payload (message, or name: code) - the QQ bridge holds interim step text until the next tool call (or the end of the turn) pushes it, emits 'Tool call <name>' per call, emits 'Tool call <name>\nError: <reason>' for failures, and skips re-sending interim text that already equals the final answer Other channels keep their existing behaviour: the status frame still reads '正在整理结果…' and they ignore the new optional fields. |
||
|---|---|---|
| .. | ||
| client-api.test.mjs | ||
| client-lifecycle.test.mjs | ||
| client-ui.test.mjs | ||
| config-store.test.mjs | ||
| connection-supervisor.test.mjs | ||
| device-auth.test.mjs | ||
| dingtalk-api.test.mjs | ||
| dingtalk-bridge.test.mjs | ||
| dingtalk-card-stream.test.mjs | ||
| dingtalk-controller.test.mjs | ||
| dingtalk-runtime.test.mjs | ||
| harness-client.test.mjs | ||
| plugin-host.test.mjs | ||
| production.test.mjs | ||
| rpc.test.mjs | ||
| state-store.test.mjs | ||