Kimi-CLI does not seem to respect task timeout parameters, leading to persistent timeouts

[YunfanZhang42]

What version of Kimi Code CLI is running?

1.30

Which open platform/subscription were you using?

Kimi Code

Which model were you using?

kimi-for-coding

What platform is your computer?

Linux 6.8.0-101-generic x86_64 x86_64

What issue are you seeing?

Kimi-CLI no longer respects timeout limit set by the model in the tool call. The tasks seem to always be terminated at 60s, disregarding the timeout limit set by the model. This behavior is the same in VSCode Plugins as well as CLI. This leads to serious issues and breaks my workflows.

Please see the following screenshot for an example:

What steps can reproduce the bug?

Ask Kimi to run a long running task and there is high probability of triggering this issue. I tried to designed a prompt that can reliably trigger this issue but there is no success.

What is the expected behavior?

Kimi-CLI respects the timout parameter set by the model in tool calls, allowing long running tasks to finish.

Additional information

I suspect this issue is introduced by the background bash task feature in #1477 . Dropping the version back to 1.22 fixes this problem.

[bloodycoder]

Draft PR opened for review: #1840

What is included:

• support timeout_s alias for timeout
• explicit validation errors for unsupported timeout keys (timeout_ms, timeoutSeconds)
• conflict validation when both timeout and timeout_s are provided
• ACP timeout/message aligned with normalized timeout value

Validation:

• pytest tests/acp/test_terminal_timeout.py tests/tools/test_background_tools.py tests/tools/test_shell_bash.py -q
• 48 passed

If needed, I can add/adjust e2e coverage in a follow-up commit.