怎么给对话加上一个重试按钮？

[baigongli]

有时候在用的时候会这样假死，curl 发请求，模型能正常响应，不懂什么原因，所以想dsh这边终止掉，然后重试一下

[liyangbing]

There is already a Session-level stop path in alpha.1: while the Turn is open, the composer shows Stop generating. It calls the scoped conversation cancel(), which invokes Session cancellation.\n\nUse it once, then wait for all four signs before continuing:\n\n1. Stop/generating control disappears.\n2. The streaming node is gone.\n3. Partial output is shown as stopped/interrupted.\n4. The Host/Session log closes the Turn durably with turn/end reason aborted.\n\nA separate successful curl only proves endpoint reachability. The active Harness request can still be stuck in its specific payload/stream, tool execution, Session Remote, or browser projection. If reload shows a closed Turn, capture browser/Remote reconnect evidence; if Stop fails and the Turn stays open, capture the session/cancel result, Agent phase, Host error, and last event sequence.\n\nA generic Retry button is not currently equivalent to the existing llm/retry row: that row is runtime policy for one model request. Before user resubmission, check the last tool/external effect. If no effect was admitted, send a revised follow-up after the durable abort. If an effect committed, tell the Agent what happened rather than repeating it. If outcome is unknown, reconcile the external system first. Use Branch into a new conversation only at a proven durable boundary, or start a clean Session with a concise handoff when the history is ambiguous.\n\nA safe product Retry should preserve the aborted Turn, expose the replay boundary, gate unknown/non-idempotent effects, create a new retry identity, deduplicate clicks, and never rewrite append-only history. Full source-pinned decision guide: https://github.com/sandbaseai/deepseek-harness-handbook/blob/main/docs/en/troubleshooting/stuck-turn-stop-and-retry.md