Feature Request

Different chat interfaces have fundamentally different input patterns, making a single global queue config a poor fit for all channels simultaneously.

Problem

Currently queue settings (mode, debounce, cap, drop) are global. This means you're always picking the least-bad tradeoff across all channels at once.

Channel differences:

• Telegram/mobile: Users type in bursts (3-4 short messages instead of one long one). Needs higher debounce (2-3s) + collect to batch thoughts together.
• TUI: Deliberate input, user can see the agent working in real time. Lower debounce (500ms) preferred. steer or interrupt are viable.
• Slack: Mix of quick reactions and longer thoughts. Medium debounce (1-2s) + collect or followup.

Proposed Solution

Allow queue settings to be overridden per-channel in config, falling back to global defaults. Example config shape:

agent:
  queue:
    mode: collect
    debounceMs: 1000
    cap: 20
    drop: summarize
    channels:
      telegram:
        debounceMs: 2000
      webchat:
        debounceMs: 500
        mode: steer
      slack:
        debounceMs: 1500
        mode: followup

Expected Behavior

Each channel uses its own queue settings where specified, falling back to global defaults for unspecified channels/settings.

Environment

• macOS Darwin 25.3.0 arm64
• OpenClaw 2026.3.13