openclaw - 💡(How to fix) Fix Add config option to disable subagent completion notifications in /status [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#59166Fetched 2026-04-08 02:27:55
View on GitHub
Comments
1
Participants
2
Timeline
1
Reactions
0
Author
Timeline (top)
commented ×1

Code Example

/status

---

{
  "agents": {
    "defaults": {
      "subagentNotifications": {
        "mode": "silent" | "summary" | "full"
      }
    }
  }
}
RAW_BUFFERClick to expand / collapse

Problem

When a subagent task completes, the result is automatically appended to the /status output. This can make the status output very long and cluttered, especially when the user just wants to see basic runtime info (model, tokens, etc.).

Current Behavior

/status

Shows:

  1. Runtime status card (expected)
  2. All pending subagent completion events (can be very long)

Proposed Solution

Add a config option to control subagent notification behavior:

{
  "agents": {
    "defaults": {
      "subagentNotifications": {
        "mode": "silent" | "summary" | "full"
      }
    }
  }
}

Options:

  • silent: Don't show subagent completions in /status (user can check via other means)
  • summary: Show a brief one-line summary (e.g., "1 task completed")
  • full: Current behavior (show full result)

Default: full (backward compatible)

Use Case

Users who run many background tasks don't want to see all the results every time they check status. They can check specific task results separately if needed.

Alternative

Add a /status --brief flag that skips subagent notifications.

extent analysis

TL;DR

To address the issue of cluttered /status output, consider adding a configuration option to control subagent notification behavior, allowing users to choose between silent, summary, or full modes.

Guidance

  • Implement the proposed subagentNotifications config option with silent, summary, and full modes to give users control over the level of detail shown in the /status output.
  • Consider adding a /status --brief flag as an alternative solution to skip subagent notifications for users who prefer a command-line approach.
  • Evaluate the default mode for subagentNotifications to ensure it aligns with the most common user needs, potentially setting it to summary for a balance between information and clutter.
  • Test the implementation with various subagent task scenarios to ensure the chosen mode correctly filters or summarizes the output as expected.

Example

{
  "agents": {
    "defaults": {
      "subagentNotifications": {
        "mode": "summary"
      }
    }
  }
}

Notes

The effectiveness of this solution depends on the specific requirements and workflows of the users. It may be beneficial to gather feedback on the proposed modes and default setting to ensure they meet the needs of the majority of users.

Recommendation

Apply the workaround by implementing the subagentNotifications config option, as it provides a flexible solution that caters to different user preferences without requiring significant changes to the existing functionality.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING