#Model timeout

1 messages · Page 1 of 1 (latest)

lament brook
#

How an i adjust the timeout of a model, I have some commands that seem to have taken a long time, and might have caused a timeout in openclaw. What is the default timeout, and how can I change it?

hardy lintelBOT
vestal plumeBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

hardy lintelBOT
pulsar nymphBOT
#

There are a few different timeouts in OpenClaw, and the right knob depends on what actually timed out:

  • Overall agent run: agents.defaults.timeoutSeconds, default is 172800s (48h)
  • LLM idle timeout: agents.defaults.llm.idleTimeoutSeconds, this is usually the important one for slow models. Current source says 120s if unset, but some older releases used 60s
  • Shell command / exec timeout: tools.exec.timeoutSec, default is 1800s (30m)

Useful examples:

openclaw config set agents.defaults.llm.idleTimeoutSeconds 300
openclaw config set agents.defaults.timeoutSeconds 3600
openclaw config set tools.exec.timeoutSec 7200
openclaw gateway restart

If it is just one exec call, you can also raise the timeout just for that command instead of changing the global config.

lament brook
#

2026.4.15 : Seems like I need to update idleTimeoutSeconds then

pulsar nymphBOT
#

Yep, if the model request itself is going idle, agents.defaults.llm.idleTimeoutSeconds is the right knob.

I’d try something like:

openclaw config set agents.defaults.llm.idleTimeoutSeconds 300
openclaw gateway restart

A few notes:

  • 300 = 5 minutes
  • 0 disables the idle timeout entirely
  • if you’re on a slow local model, 300 or 600 is usually a reasonable starting point

Docs: https://docs.openclaw.ai/concepts/agent-loop