Chat commands, aborting tasks, and stopping a run

How do I stop internal system messages from showing in chat?

Most internal/tool messages only appear when verbose, trace, or reasoning is enabled for that session.Fix in the chat where you see it:

/verbose off
/trace off
/reasoning off

Still noisy: check session settings in the Control UI and set verbose to inherit; confirm you are not using a bot profile with verboseDefault: "on" in config.Docs: Thinking and verbose, Security.

How do I stop/cancel a running task?

Send any of these as a standalone message (no slash) to trigger an abort: stop, stop action, stop current action, stop run, stop current run, stop agent, stop the agent, stop openclaw, openclaw stop, stop don't do anything, stop do not do anything, stop doing anything, do not do that, please stop, stop please, abort, esc, exit, interrupt, halt. Common non-English triggers (French, German, Spanish, Chinese, Japanese, Hindi, Arabic, Russian) also work.For background processes started by the exec tool, ask the agent to run:

process action:kill sessionId:XXX

Most slash commands must be sent as a standalone message starting with /, but a few shortcuts (like /status) also work inline for allowlisted senders. See Slash commands.

How do I send a Discord message from Telegram? ("Cross-context messaging denied")

OpenClaw allows cross-provider messaging by default. An agent in Telegram or WebChat can send to Discord when the destination is configured and its tool and channel policies permit it.If you see “Cross-context messaging denied”, check for tools.message.crossContext.allowAcrossProviders: false globally or in the agent’s configuration. Remove that restriction or explicitly allow cross-provider messaging; this takes effect without a Gateway restart:

{
  tools: {
    message: {
      crossContext: {
        allowAcrossProviders: true,
        marker: { enabled: true, prefix: "[from {channel}] " },
      },
    },
  },
}

To block cross-provider messaging, set allowAcrossProviders: false. Per-agent values under agents.entries.<id>.tools.message.crossContext override the global setting. After upgrading, configurations that omit this setting use the new default; existing explicit values remain effective. No configuration migration is needed.An explicit restriction still applies when the current conversation target is unavailable, including after restart recovery or a subagent continuation. The source provider is enough to enforce it.

Why does it feel like the bot "ignores" rapid-fire messages?

Mid-run prompts are steered into the active run by default. Use /queue to choose active-run behavior:

steer (default) - guide the active run at the next model boundary.
followup - queue messages and run them one at a time after the current run ends.
collect - queue compatible messages and reply once after the current run ends.
interrupt - abort the current run and start fresh.

Add options to queued modes like debounce:0.5s cap:25 drop:summarize. See Command queue and Steering queue.

Start here

FAQ

Diagnostics

Community and meta

Chat commands, aborting tasks, and stopping a run

Chat commands, aborting tasks, and “it will not stop”

​Chat commands, aborting tasks, and “it will not stop”

Chat commands, aborting tasks, and “it will not stop”