Stream idle timeout — no response for 330s. The connection may have dropped.

Open
  • Is something wrong?
#659 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
52/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
electron, nextjs, typescript
Domain
backend, desktop

Research direction

Start at the stream timeout handling for the Claude Code SDK runtime and trace how the 330-second idle limit is applied, especially for the DeepSeek provider. The issue gives no file or test names, so first locate the timeout code and its tests; done means complex tasks no longer time out unexpectedly or users can configure the timeout.

Written by the indexing model from the issue text.

Description

bug
CodePilot 版本 / Version

0.58

操作系统与架构 / OS & arch

windows11

Runtime

Claude Code (SDK)

Provider / Model

deepseek

是否可复现 / Reproducible?

每次都能复现 / always

复现步骤 / Steps to reproduce

复杂任务经常 Stream idle timeout — no response for 330s. The connection may have dropped.

期望 vs 实际 / Expected vs actual

如果不好修复建议搞个自己设置超时时间

日志 / 截图 / session id

No response

影响面 / Impact
  • 涉及文件写入或可能误改/丢失数据 / involves file write or possible data loss
  • 导致崩溃、闪退或对话被自动中断 / causes crash / quit / auto-interrupt
Dominant language
TypeScript
Stars
6.5k
Forks
697
No merged PRs in 30d

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from op7418/CodePilot

All issues in op7418/CodePilot

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.