fix: notify agent session on background exec completion by default#741
Open
BingqingLyu wants to merge 1 commit into
Open
fix: notify agent session on background exec completion by default#741BingqingLyu wants to merge 1 commit into
BingqingLyu wants to merge 1 commit into
Conversation
Previously, successful background exec processes with empty output would silently complete without notifying the parent agent session. This caused a major UX gap in multi-agent orchestration workflows where an orchestrator agent dispatches coding agents (Claude Code, Codex) in background — the orchestrator was never woken up on completion, leaving users waiting indefinitely. Changes: - Default notifyOnExitEmptySuccess to true (was false) Background processes that complete successfully now always enqueue a system event, even when stdout is empty. Agents should always know when their dispatched work finishes. - Align runExecProcess default with createExecTool (both use !== false) - Reduce exec exit wake coalesce delay to 50ms (was 250ms) Exec completion is time-sensitive for orchestration flows. - Update tests and config docs to reflect new defaults Users who want the old behavior can set: tools.exec.notifyOnExitEmptySuccess: false Fixes openclaw#18237
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
Background exec processes that complete successfully with empty output currently silently exit without notifying the parent agent session. This is the #1 UX gap in multi-agent orchestration workflows.
Problem
When an orchestrator agent (e.g., Hikari) dispatches a coding agent (Claude Code, Codex) via
exec background:true, the coding agent finishes but the orchestrator is never woken up — users see silence until they manually check in.Root cause:
notifyOnExitEmptySuccessdefaults tofalse, so successful exits with empty/cleared output skip the system event + heartbeat wake entirely.Related issue: openclaw#18237
Changes
notifyOnExitEmptySuccessdefaultfalsetrueWhy
tools.exec.notifyOnExitEmptySuccess: false.Testing
bash-tools.test.tspass ✅Fixes openclaw#18237