fix(openclaw): fallback to conditions when AgentHarness phase=UNSPECIFIED#1966
Draft
nloke wants to merge 1 commit into
Draft
fix(openclaw): fallback to conditions when AgentHarness phase=UNSPECIFIED#1966nloke wants to merge 1 commit into
nloke wants to merge 1 commit into
Conversation
…FIED When the openclaw backend returns phase=UNSPECIFIED, the controller would never surface Ready=True to the AgentHarness. Fall back to checking status.conditions[Ready=True] in that case. See: kagent-dev#1958
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
1 participant
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.
Fixes #1958
Problem
When the openclaw backend returns
phase=UNSPECIFIEDfor a sandbox, theAgentHarnesscontroller never surfacesReady=True— the harness is stuck indefinitely even though the sandbox is healthy.Root Cause
translate.gomaps the OpenShellphasefield directly to theAgentHarnessready state. When openclaw reportsphase=UNSPECIFIED(which it does in some versions), there is no fallback — the controller sees no usable phase and never marks the harness ready.Fix
Add a fallback in
translate.go: ifphase=UNSPECIFIED, checkstatus.conditionsfor aReady=Truecondition and use that to determine readiness instead.Testing
Validated on a local kind cluster —
AgentHarnessreachesReady=Truewith this fix applied against an openclaw backend that reportsphase=UNSPECIFIED.