openclaw - 💡(How to fix) Fix [Bug]: idletimeout seconds [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#74353Fetched 2026-04-30 06:25:06
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
2
Author
Timeline (top)
closed ×1commented ×1labeled ×1

Provider timeoutSeconds does not appear to fully replace retired agents.defaults.llm.idleTimeoutSeconds for LM Studio cold-load models

Root Cause

Provider timeoutSeconds does not appear to fully replace retired agents.defaults.llm.idleTimeoutSeconds for LM Studio cold-load models

Code Example

## Steps to Reproduce

1. Configure LM Studio as a local OpenAI-compatible provider with a large model that takes longer than 60120 seconds to cold load.
2. Set `models.providers.<id>.timeoutSeconds` to a high value, such as `900`.
3. Ensure the model is unloaded/cold in LM Studio.
4. Run an OpenClaw agent request against that provider/model.
5. Observe whether OpenClaw waits for the configured provider timeout or fails/fallbacks before the first token.
6. Compare this behavior to the former `agents.defaults.llm.idleTimeoutSeconds` setting, which previously prevented premature failover during cold load.
7. Run `openclaw doctor --fix` and observe that the old `agents.defaults.llm` block is removed as legacy.

    Compare against the old legacy setting, which previously allowed the same cold model to load successfully:

{
  "agents": {
    "defaults": {
      "llm": {
        "idleTimeoutSeconds": 300
      }
    }
  }
}

### Expected behavior

## Expected Behavior

When `models.providers.<id>.timeoutSeconds` is configured for a local LM Studio / OpenAI-compatible provider, OpenClaw should apply that timeout to the entire model request path, including:

- provider HTTP request timeout
- OpenAI-compatible streaming request
- time-to-first-token wait
- model stream idle watchdog
- embedded-runner failover timing

For example, with:

---

## Actual Behavior

In OpenClaw `2026.4.26`, `openclaw doctor --fix` removes the previous `agents.defaults.llm.idleTimeoutSeconds` setting as legacy and reports:

---
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Provider timeoutSeconds does not appear to fully replace retired agents.defaults.llm.idleTimeoutSeconds for LM Studio cold-load models

Steps to reproduce

A slightly shorter version:

## Steps to Reproduce

1. Configure LM Studio as a local OpenAI-compatible provider with a large model that takes longer than 60–120 seconds to cold load.
2. Set `models.providers.<id>.timeoutSeconds` to a high value, such as `900`.
3. Ensure the model is unloaded/cold in LM Studio.
4. Run an OpenClaw agent request against that provider/model.
5. Observe whether OpenClaw waits for the configured provider timeout or fails/fallbacks before the first token.
6. Compare this behavior to the former `agents.defaults.llm.idleTimeoutSeconds` setting, which previously prevented premature failover during cold load.
7. Run `openclaw doctor --fix` and observe that the old `agents.defaults.llm` block is removed as legacy.

    Compare against the old legacy setting, which previously allowed the same cold model to load successfully:

{
  "agents": {
    "defaults": {
      "llm": {
        "idleTimeoutSeconds": 300
      }
    }
  }
}

### Expected behavior

## Expected Behavior

When `models.providers.<id>.timeoutSeconds` is configured for a local LM Studio / OpenAI-compatible provider, OpenClaw should apply that timeout to the entire model request path, including:

- provider HTTP request timeout
- OpenAI-compatible streaming request
- time-to-first-token wait
- model stream idle watchdog
- embedded-runner failover timing

For example, with:

```json
"models": {
  "providers": {
    "local-workers": {
      "baseUrl": "http://(agent):1234/v1",
      "auth": "token",
      "api": "openai-completions",
      "timeoutSeconds": 900
    }
  }
}

### Actual behavior

```md
## Actual Behavior

In OpenClaw `2026.4.26`, `openclaw doctor --fix` removes the previous `agents.defaults.llm.idleTimeoutSeconds` setting as legacy and reports:

```text
Removed agents.defaults.llm; model idle timeout now follows models.providers.<id>.timeoutSeconds.

### OpenClaw version

2026.4.26

### Operating system

macos 26.4.1

### Install method

Installed via pnpm / npm global install on macOS.

### Model

Qwen3.6-35B

### Provider / routing chain

OpenClaw gateway → local-workers provider → LM Studio 

### Additional provider/model setup details

_No response_

### Logs, screenshots, and evidence

```shell

Impact and severity

No response

Additional information

Short version:

Unknown. Last working behavior was prior to 2026.4.26, when `agents.defaults.llm.idleTimeoutSeconds` was still accepted and effective.

extent analysis

TL;DR

The models.providers.<id>.timeoutSeconds setting may not be fully replacing the retired agents.defaults.llm.idleTimeoutSeconds for LM Studio cold-load models, causing premature failover.

Guidance

  • Verify that the models.providers.<id>.timeoutSeconds setting is correctly configured and applied to the entire model request path.
  • Check the OpenClaw logs for any errors or warnings related to timeout settings or model loading.
  • Compare the behavior with the old agents.defaults.llm.idleTimeoutSeconds setting to identify any differences.
  • Consider setting a higher value for models.providers.<id>.timeoutSeconds to see if it resolves the issue.

Example

No code snippet is provided as it is not clearly supported by the issue.

Notes

The issue seems to be related to the replacement of the retired agents.defaults.llm.idleTimeoutSeconds setting with models.providers.<id>.timeoutSeconds. However, without more information about the OpenClaw configuration and logs, it is difficult to provide a definitive solution.

Recommendation

Apply workaround: Increase the value of models.providers.<id>.timeoutSeconds to a higher value, such as 1200, to see if it resolves the issue. This may help to prevent premature failover during cold load.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug]: idletimeout seconds [1 comments, 2 participants]