fix(openclaw): batch config set calls into single exec - #3319
Merged
AhmedTMM merged 3 commits intoApr 18, 2026
Conversation
Merges 4 separate runner.runServer() calls (model, sandbox, browser, channel stubs) into one exec with commands chained by `;`. On Sprite (container-exec, not persistent SSH), many sequential execs exhaust the connection and cause "connection closed" / "context deadline exceeded" on later steps like gateway startup. Before: 4 execs → 14 "Config overwrite" log lines → flaky connection After: 1 exec → same config result → stable connection for gateway Individual commands use `;` not `&&` so a failure in one (e.g. browser path not found) doesn't skip the rest — these are all non-fatal prefs. Bumps 1.0.15 -> 1.0.16.
AhmedTMM
force-pushed
the
fix/openclaw-batch-config
branch
from
April 17, 2026 22:02
d1171cc to
e33d40f
Compare
la14-1
approved these changes
Apr 18, 2026
la14-1
left a comment
la14-1
left a comment
Collaborator
There was a problem hiding this comment.
Security review: Safe to merge. Changes batch 4 sequential openclaw config set execs into 1. No user input interpolation — all values come from hardcoded config objects. Commands chained with `;" matches prior error-tolerant behavior. CI green (all 5 checks). LGTM.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Batches 4 separate
runner.runServer()calls for OpenClaw config into a single exec. Fixes the connection flakiness you saw on Sprite where the gateway start fails with "connection closed" / "context deadline exceeded" after too many sequential execs.Before (4 execs)
Each exec = a separate
sprite execsession. 14 totalopenclaw config setcalls across 4 sessions → 14 "Config overwrite" log lines → connection pool exhausted → gateway start fails.After (1 exec)
All config sets in one session. Same result, 3 fewer Sprite exec connections before the gateway start.
Non-lossy guarantee
Commands are chained with
;(not&&), so if any individual config set fails (e.g. browser path not found because Chrome wasn't selected), the rest still run. This matches the previous behavior where each call was wrapped inasyncTryCatchIfwith non-fatal warnings.Test plan
bunx biome check— 0 errorsbun test— 2070/2070 passspawn openclaw sprite— verify config writes succeed in one batch, gateway starts without connection drops