Skip to content

Feature request: config option to suppress sub-agent announce #8299

@jzOcb

Description

@jzOcb

Problem

When using sessions_spawn, the sub-agent announce step runs after completion and posts a summary to the requester chat. The only way to suppress this is for the sub-agent model to reply exactly ANNOUNCE_SKIP during the announce step.

The problem: The sub-agent model frequently ignores the ANNOUNCE_SKIP instruction in the task, even when explicitly stated. This means unverified, potentially fabricated summaries get posted directly to the chat before the main agent can review them.

Current workaround

Include When prompted to announce, reply exactly: ANNOUNCE_SKIP in the task. This works ~60% of the time — models sometimes follow it, sometimes don't.

Requested feature

A config option to suppress announce at the framework level:

{
  agents: {
    defaults: {
      subagents: {
        announcePolicy: "skip"  // "skip" | "always" | "model" (default)
      }
    }
  }
}

Or a per-spawn parameter:

sessions_spawn({ task: "...", announce: false })

Why this matters

  • Sub-agent output is unverified — fabricated data, file paths, false claims
  • The main agent should always be the gatekeeper between sub-agent and user
  • Prompt-based enforcement has inherent unreliability
  • Code/config enforcement is the only way to guarantee behavior

Environment

  • OpenClaw version: 2026.1.24-1
  • Model: Claude Opus 4.5 (main) / Sonnet 4 (sub-agents)
  • Channel: Telegram

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Normal backlog priority with limited blast radius.clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.clawsweeper:needs-product-decisionClawSweeper marked this issue as needing a product or behavior decision.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.enhancementNew feature or requestimpact:message-lossChannel message delivery can be lost, duplicated, or misrouted.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions