# Long local-model runs finish but the chat reports an error **URL:** \ **Category:** Troubleshooting\ **Tags:** configuration, local-models, models, performance, troubleshooting\ **Created:** [September 14, 2026, 10:31pm UTC](https://community.openclaw.ai/t/long-local-model-runs-finish-but-the-chat-reports-an-error/79 "2026-09-14T22:31:11Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![ArchivedMember](https://avatars.discourse-cdn.com/v4/letter/a/e56c9b/32.png) [@ArchivedMember](https://community.openclaw.ai/u/ArchivedMember)\ **Post date:** [September 14, 2026, 10:31pm UTC](https://community.openclaw.ai/t/long-local-model-runs-finish-but-the-chat-reports-an-error/79/1 "2026-09-14T22:31:11Z")
> **Adapted community discussion:** Paraphrased and condensed from an anonymized public OpenClaw Discord support conversation from September 2026. Technical guidance was reviewed for OpenClaw 2026.9.3. I am testing a slow local model through the browser interface. A long task can run for more than 15 minutes and complete its work, but the chat reports an error instead of returning the final reply. The model server does not report a context overflow. Is an OpenClaw timeout cutting off the response? ---
**Author:** ![OpenClawSupport](https://avatars.discourse-cdn.com/v4/letter/o/49beb7/32.png) [@OpenClawSupport](https://community.openclaw.ai/u/OpenClawSupport)\ **Post date:** [September 14, 2026, 10:31pm UTC](https://community.openclaw.ai/t/long-local-model-runs-finish-but-the-chat-reports-an-error/79/2 "2026-09-14T22:31:11Z")
There are two relevant limits: `agents.defaults.timeoutSeconds` covers the whole agent run, while `models.providers..timeoutSeconds` covers the provider request and stream. Check both effective values and follow the logs while reproducing the problem: ```bash openclaw config get agents.defaults.timeoutSeconds openclaw config get models.providers.PROVIDER_ID.timeoutSeconds openclaw logs --follow ``` Completed work with a missing final reply points more toward an expired run or provider stream than context overflow. For jobs this slow, a background session can also be more resilient. ---
**Author:** ![ArchivedMember](https://avatars.discourse-cdn.com/v4/letter/a/e56c9b/32.png) [@ArchivedMember](https://community.openclaw.ai/u/ArchivedMember)\ **Post date:** [September 14, 2026, 10:31pm UTC](https://community.openclaw.ai/t/long-local-model-runs-finish-but-the-chat-reports-an-error/79/3 "2026-09-14T22:31:11Z")
What commands should I use to raise those limits from the terminal? ---
**Author:** ![OpenClawSupport](https://avatars.discourse-cdn.com/v4/letter/o/49beb7/32.png) [@OpenClawSupport](https://community.openclaw.ai/u/OpenClawSupport)\ **Post date:** [September 14, 2026, 10:31pm UTC](https://community.openclaw.ai/t/long-local-model-runs-finish-but-the-chat-reports-an-error/79/4 "2026-09-14T22:31:11Z")
Set the whole-run limit above the provider limit. These example values are in seconds: ```bash openclaw config set agents.defaults.timeoutSeconds 3600 openclaw config set models.providers.omlx.timeoutSeconds 1800 openclaw config get agents.defaults.timeoutSeconds openclaw config get models.providers.omlx.timeoutSeconds ``` Replace `omlx` with the actual key used under `models.providers` if yours differs. Current reference: [local models](https://docs.openclaw.ai/gateway/local-models). ---
**Author:** ![ArchivedMember](https://avatars.discourse-cdn.com/v4/letter/a/e56c9b/32.png) [@ArchivedMember](https://community.openclaw.ai/u/ArchivedMember)\ **Post date:** [September 14, 2026, 10:31pm UTC](https://community.openclaw.ai/t/long-local-model-runs-finish-but-the-chat-reports-an-error/79/5 "2026-09-14T22:31:11Z")
I changed both values and am testing now. Do I need another step to make them survive a restart? ---
**Author:** ![OpenClawSupport](https://avatars.discourse-cdn.com/v4/letter/o/49beb7/32.png) [@OpenClawSupport](https://community.openclaw.ai/u/OpenClawSupport)\ **Post date:** [September 14, 2026, 10:31pm UTC](https://community.openclaw.ai/t/long-local-model-runs-finish-but-the-chat-reports-an-error/79/6 "2026-09-14T22:31:12Z")
No. `openclaw config set` writes persistent configuration, so those values survive Gateway and computer restarts. You can rerun the two `config get` commands to verify what was saved. ---
**Author:** ![ArchivedMember](https://avatars.discourse-cdn.com/v4/letter/a/e56c9b/32.png) [@ArchivedMember](https://community.openclaw.ai/u/ArchivedMember)\ **Post date:** [September 14, 2026, 10:31pm UTC](https://community.openclaw.ai/t/long-local-model-runs-finish-but-the-chat-reports-an-error/79/7 "2026-09-14T22:31:12Z")
Raising the timeouts worked. The local model still took a while, but the chat completed without the error. ---
**Author:** ![OpenClawSupport](https://avatars.discourse-cdn.com/v4/letter/o/49beb7/32.png) [@OpenClawSupport](https://community.openclaw.ai/u/OpenClawSupport)\ **Post date:** [September 14, 2026, 10:31pm UTC](https://community.openclaw.ai/t/long-local-model-runs-finish-but-the-chat-reports-an-error/79/8 "2026-09-14T22:31:12Z")
That confirms the timeout was the immediate problem rather than context overflow. The remaining delay is model generation speed; for faster interactive work, reduce the model’s reasoning or output budget, or use a smaller local model.