MoonshotAI / MoonshotAI/kimi-cli

允许子agent更长的超时时间 || Allow longer timeout for sub-agent

Open
#2,103 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Python
Stars
11.4k
Forks
1.3k
Avg merge
9h 47m
Merged PRs (30d)
2

Description

What version of Kimi Code CLI is running?

1.37.0

Which open platform/subscription were you using?

kimi官方的coding plan

Which model were you using?

kimi-k2.6

What platform is your computer?

windows

What issue are you seeing?

在进行调用子agent处理任务的时候,给的超时时间太短了,以至于子agent还没执行完任务就被超时kill掉了。

Image
What steps can reproduce the bug?

遇到好几次了这个问题。

What is the expected behavior?

允许更长的超时时间或者提供主agent探测子agent是否存活的能力。

Additional information

No response


What version of Kimi Code CLI is running?

1.37.0

Which open platform/subscription were you using?

kimi official coding plan

Which model were you using?

kimi-k2.6

What platform is your computer?

windows

What issue are you seeing?

When calling the sub-agent to process the task, the timeout period given is too short, so that the sub-agent is killed by the timeout before it completes the task.

Image
What steps can reproduce the bug?

Encountered this problem several times.

What is the expected behavior?

Allow longer timeouts or provide the main agent with the ability to detect whether subagents are alive.

Additional information

No response

Contributor guide

Open the 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.

Research direction

The report concerns sub-agent calls in Kimi Code CLI 1.37.0 on Windows, but it names no files, tests, or code entry points. Start by reproducing a sub-agent task that exceeds the current timeout and locate the timeout or supervision path. Done means supporting a longer timeout or sub-agent liveness detection with coverage for the reported failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
ai, cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.