$ the-wire · showcase
Fix explicit-agent fleets, remove payload timing race
By RepoJournal · Filed · About OpenClaw · Composed from the cited sources · methodology
![openclaw-docs-sync[bot]](https://avatars.githubusercontent.com/u/13697529?v=4)
Control UI terminals and model setup now work in explicit-agent fleets after a fix for a race condition that surfaced during Gateway restarts.
Explicit multi-agent fleets failed Control UI terminal opens and model setup with `AgentSelectionRequiredError`, especially while the UI reconnected after a Gateway restart. The fix makes repository ownership and agent selection explicit, so these operations resolve to the selected agent rather than failing. [1]
The diagnostics change reordering the large shard exposed a pre-existing one-second timeout around lazy Responses transport initialization. The payload timing race is resolved by failing from the stream's terminal result and pre-aborting egress, making payload serialization "a strict offline contract." [2]
Crabbox hardened sync behavior: it now rejects native Jujutsu workspaces to prevent Git discovery from escaping the `.jj` workspace and syncing the wrong revision. [3] The diagnostic credential redaction was made context-aware, failing closed on ambiguous bytes while preserving quoted shell syntax and JSON siblings. [4]
Action items
- → Review explicit-agent fleet deployments for the AgentSelectionRequiredError fix openclaw/openclaw [plan]
- → Check sync behavior on native Jujutsu workspaces after the rejection change openclaw/crabbox [plan]
References
- [1] fix: terminals and model setup fail in explicit-agent fleets ↗ openclaw/openclaw
- [2] test(agents): remove d60a98e payload timing race ↗ openclaw/openclaw
- [3] fix(sync): reject native Jujutsu workspaces ↗ openclaw/crabbox
- [4] fix(worker): harden diagnostic credential redaction ↗ openclaw/crabbox
