openclaw - 💡(How to fix) Fix [Feature]: Support Mattermost progress-preview streaming under the Codex harness without forcing visibleReplies: "automatic"

Type: Feature request

OpenClaw version: 2026.5.28

Summary:

Under the Codex app-server harness (openai/gpt-5.5 + agentRuntime.id: "codex", codex plugin enabled), the Mattermost progress preview no longer renders during generation. The channel is configured with:

"channels": { "mattermost": { "streaming": {
  "mode": "progress",
  "progress": { "label": "auto", "toolProgress": true, "maxLines": 4, "maxLineChars": 180 }
}}}

This worked on the PI runtime. After migrating to the Codex harness, the progress/status preview during tool-heavy turns stopped appearing.

Root cause (from docs):

Per the Codex harness runtime docs, under the harness, visible replies default to the message tool — the agent posts to the channel only when it calls message(action="send"), which is a discrete post that bypasses the automatic delivery pipeline that emits the progress preview. Setting messages.visibleReplies: "automatic" restores the legacy automatic delivery path (and progress), but for any agent that also calls message(action="send") this reintroduces double-posting.

Separately, Mattermost is not listed in the streaming channel-mapping table (only Telegram/Discord/Slack are documented), so its progress-preview behavior under the Codex harness appears unwired.

Request:

Emit the Mattermost progress preview (streaming.mode: "progress", toolProgress: true) during Codex-harness turns independent of the visibleReplies final-reply delivery mode — i.e., stream tool start/update/end events to the Mattermost preview while the Codex turn is in flight, regardless of whether the final reply is delivered via the message tool or the automatic path. This avoids forcing operators to choose between progress streaming and double-posting.

Impact: Any Mattermost deployment on the now-canonical Codex harness loses in-flight progress visibility on long, tool-heavy turns.