Add /timeout so we can adjust the timeout

[isbafatima90-arch]

What feature would you like to see?

When using kimi cli to install something then it keeps getting killed by timeout (60s) if we could spesify our timeout for our task becasue different tasks neeed different ammount of time, it would be perfect.

Additional information

No response

[xiaoju111a]

Thanks for the feedback!

Here's how the Shell tool timeout currently works:

• Default timeout: 60 seconds
• Max timeout: 300 seconds (5 minutes)
• Timeout is a tool parameter that the LLM decides on each call

The issue is that the LLM doesn't proactively set a longer timeout for installation commands.

Workaround: You can explicitly tell the agent in your conversation to "use a longer timeout, like 300 seconds" — the LLM will then pass that value when calling the Shell tool.

[iamshaynez]

Hope we can have the option to set or even remove timeout limit. For certain tasks, the execution time is expected to be long.

[Speike-SHL]

Or how can we proactively awaken Kimi so that when running a long task, Kimi knows to come back later to check if it's completed? Is this somewhat similar to OpenClaw?

[Br1an67]

Submitted PR #1507 implementing a /timeout command. Users can now run /timeout 600 to set the shell command timeout to 600 seconds (or any positive integer). The setting acts as a floor — the LLM can still request higher timeouts if needed.