Skip to content

助手执行过程中没有任何进展反馈,用户不知道当前在做什么 #131

Open

Description

@Birfy

问题

在助手面板里发起任务后,中间没有任何实时反馈,看不出进展到哪一步、还要多久,也不知道是不是卡住了。

复现

  1. 本地运行 opendirector serve(main 2579ce58,macOS arm64),文本模型配置为 MiniMax-M3.1-Flash
  2. 新会话中输入:「我想做一个孙悟空大战达斯维达的的视频」
  3. 界面只显示「执行记录 · 3 次调用 3/3 已完成」和一行「思考中…」,之后长时间没有任何新信息

期望

执行期间持续给出可见的进展,例如:

  • 当前在做哪一步(理解需求 / 写脚本 / 分镜 / 生成图片或视频…)
  • 流式输出模型的中间回复或计划
  • 长耗时步骤显示已等待时长或预计进度
  • 失败或超时时明确提示,而不是一直停在「思考中…」

实际

只有「思考中…」,3 次调用都显示已完成,但之后没有任何输出或状态变化,用户无法判断是在正常运行还是已经卡住。

Activity

  1. Birfy commented on Nov 6, 2026

    @Birfy
    ContributorAuthor

    后续证据(2026-11-06 约 16:30–16:58 Asia/Shanghai)

    同一项目「未命名项目 2」、用户发「继续」后的助手 run d8713e62-3ff8-453e-921f-114d30b982b9:

    • 轨迹里仅 opendirector job wait 就有约 586 条工具事件(约 293 次 complete),针对同一个视频 job 56b8d594-…
    • 期间绝大多数 wait 回执仍是 status: running / phase: poll,界面几乎看不到「还在等供应商 / 已等多久 / 失败原因」
    • job 最终失败后(providerCode: 1027),工具状态仍记为 complete(无 error 字段),更不利于用户理解

    相关新开:#136(1026/1027 文案)、#137(长 wait 后会话过期)。

  2. Zhangbo-cn commented on Nov 16, 2026

    @Zhangbo-cn
    Contributor

    One concrete cause of "stuck on 思考中…" with the activity list showing everything complete, filed separately as #345 with a provider-free repro.

    The last expectation in this issue is "失败或超时时明确提示,而不是一直停在「思考中…」". That case is reachable without any provider being at fault: the model gateway applies a hard-coded 120s read timeout (model_gateway.py:127). If the provider's first byte takes longer, the gateway returns 502, the bundled OpenCode runtime re-sends the same body, and nothing terminal ever reaches the panel.

    Trace of one turn against a stub endpoint that accepts the request and never answers (<project>/agent-runs/<turn>.model.jsonl):

    +   0.0s model.request
    + 120.0s model.error    ReadTimeout   forwardedBytes: 0
    + 122.1s model.request
    + 242.2s model.error    ReadTimeout
    + 246.4s model.request
    + 366.4s model.error    ReadTimeout
    + 375.6s model.request
    + 495.6s model.error    ReadTimeout
    + 514.0s model.request
    + 634.0s model.error    ReadTimeout
    + 670.6s model.request
    + 790.6s model.error    ReadTimeout
    

    Stored conversation afterwards:

    user      status=complete     text='你好'
    assistant status=interrupted  text=''
    

    So the persisted status is already interrupted and AssistantPanel.tsx:490 renders a label for it, but the panel only picks that up on reload. During the live turn the user sees the earlier tool calls marked complete and an indefinite "thinking" line, exactly as described in the report. Repro script and charts: #345.

    How this relates to #324: that PR collapses the repeated opendirector job wait rows and fails the activity when the job fails, which covers the long-wait half of this issue. The timeout path above is a different half — the turn itself never ends — and is not addressed by it. The remaining items listed here (step labels, streamed plan, elapsed time) are separate again.

    I measured first-byte latency for three providers before filing, to check whether 120s is a realistic ceiling rather than a theoretical one: DeepSeek deepseek-v4-pro median 0.2s, Zhipu glm-5 median 1.0s, Moonshot kimi-k3 median 13.3s with 4 of 12 calls failing to connect at all; in an earlier window the same kimi-k3 body returned its first byte after 73-180s, 2 of 6 above the timeout. Numbers and method are in #345. I hold keys for those three only, so self-hosted vLLM, proxied endpoints and long-context reasoning models remain unmeasured.

    Happy to take the timeout path as a PR if maintainers agree with the direction proposed in #345; the repro needs no paid credentials, so it can carry a regression test that fails on the current revision.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:agentAgent runtime, assistant chat and toolstype:bugSomething is broken

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions