You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Re-verification follow-up to #11805 — #11805 was closed by #12018, whose merge commit is confirmed in v0.0.128. Re-verification on v0.0.128 shows that the original 120-second timeout and permanent-busy state are mitigated, but manual compaction still cannot complete because the generated summary is rejected by the quality guard.
Description
On N1x Linux with NemoClaw v0.0.128 and the supported managed vLLM configuration, a conversation that reaches the compaction path cannot be continued. The third prompt fails with a context-recovery error, and manually running /compact repeatedly ends with guard_blocked because the generated summary is missing required sections.
This is not a recurrence of the original permanent agent is busy state from #11805: the TUI continues accepting input and does not enter livenessState=blocked. It is a residual compaction-completion failure after #12018.
Platform scope: Reproduced on N1x Linux; other platforms were not tested.
Regression: Unknown — earlier versions with the same quality-guard configuration were not tested.
Launch the OpenClaw TUI on an N1x Linux sandbox using the supported managed vLLM configuration.
Send write 500 words essay about joke and wait for completion.
Send create python quick sort and execute it and wait for completion.
Send you are a frontend engineer, create a HTML page to demonstrate advantages and disadvantages of different agents.
After context recovery fails, run /compact manually.
Expected Result
Manual /compact should complete within the configured 300-second limit, reduce the active context, and allow the existing conversation to continue.
Actual Result
Prompts 1 and 2 complete successfully.
Prompt 3 does not complete and reports: Context is too large and auto-compaction could not recover this turn.
Manual /compact fails repeatedly with outcome guard_blocked.
The compaction attempts run for approximately 46–92 seconds before the generated summary is rejected for missing required sections.
The old 120-second timeout, livenessState=blocked, and permanent agent is busy state are not observed.
/new restores usability, but the existing conversation cannot be compacted and continued.
Logs
Compaction outcome: guard_blocked
Reason: generated summary was rejected for missing required sections
Observed duration across attempts: approximately 46–92 seconds
Note
Re-verification follow-up to #11805 — #11805 was closed by #12018, whose merge commit is confirmed in
v0.0.128. Re-verification onv0.0.128shows that the original 120-second timeout and permanent-busy state are mitigated, but manual compaction still cannot complete because the generated summary is rejected by the quality guard.Description
On N1x Linux with NemoClaw
v0.0.128and the supported managed vLLM configuration, a conversation that reaches the compaction path cannot be continued. The third prompt fails with a context-recovery error, and manually running/compactrepeatedly ends withguard_blockedbecause the generated summary is missing required sections.This is not a recurrence of the original permanent
agent is busystate from #11805: the TUI continues accepting input and does not enterlivenessState=blocked. It is a residual compaction-completion failure after #12018.Platform scope: Reproduced on N1x Linux; other platforms were not tested.
Regression: Unknown — earlier versions with the same quality-guard configuration were not tested.
Environment
Steps to Reproduce
write 500 words essay about jokeand wait for completion.create python quick sort and execute itand wait for completion.you are a frontend engineer, create a HTML page to demonstrate advantages and disadvantages of different agents./compactmanually.Expected Result
Manual
/compactshould complete within the configured 300-second limit, reduce the active context, and allow the existing conversation to continue.Actual Result
Context is too large and auto-compaction could not recover this turn./compactfails repeatedly with outcomeguard_blocked.livenessState=blocked, and permanentagent is busystate are not observed./newrestores usability, but the existing conversation cannot be compacted and continued.Logs
Related Issues