openclaw - 💡(How to fix) Fix Add Slack streaming API and Block Kit support for agent progress updates [1 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#59874Fetched 2026-04-08 02:39:28
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Participants

Enable agents to show live progress updates using Slack's native task_card blocks and streaming API, similar to Attio's agent UX.

Root Cause

Enable agents to show live progress updates using Slack's native task_card blocks and streaming API, similar to Attio's agent UX.

Fix Action

Fix / Workaround

Current Workaround

RAW_BUFFERClick to expand / collapse

Summary

Enable agents to show live progress updates using Slack's native task_card blocks and streaming API, similar to Attio's agent UX.

Current State

  • OpenClaw's slack tool supports sendMessage and editMessage but only with plain text content
  • No support for Block Kit blocks parameter
  • No support for chat.startStream / chat.appendStream / chat.stopStream methods
  • nativeStreaming: true config exists but only streams text, not task updates

Requested

  1. Add blocks parameter to sendMessage and editMessage actions in the slack tool, allowing agents to send Block Kit JSON directly
  2. Add streaming actions to the slack tool: startStream, appendStream, stopStream
  3. Consider native progress mode where agents can emit checkpoint markers that auto-render as task_card blocks

Use Case

Agents processing multi-step requests can show live progress like:

  • ✅ Routed to billing skill
  • ✅ Queried Stripe (3 invoices found)
  • ⏳ Generating response...

This is the "Attio-style" agent UX that users expect from modern AI assistants.

Evidence (tested 2026-04-02)

  • task_card blocks work via raw Slack API (chat.postMessage / chat.update)
  • chat.startStream works in DM threads (returns ok: true)
  • Streaming fails in channels with missing_recipient_team_id (appears to be a Slack limitation for agent apps in public channels)

Current Workaround

Agents can use exec to call openclaw message send/edit CLI or raw curl to Slack API, but this requires exec approval and is clunky.

Links

extent analysis

TL;DR

To enable live progress updates, add support for Block Kit blocks parameter in sendMessage and editMessage actions and implement startStream, appendStream, and stopStream methods in the Slack tool.

Guidance

  • Add blocks parameter to sendMessage and editMessage actions to allow agents to send Block Kit JSON directly, enabling the use of task_card blocks.
  • Implement startStream, appendStream, and stopStream methods in the Slack tool to support streaming API, which will allow agents to show live progress updates.
  • Consider implementing native progress mode where agents can emit checkpoint markers that auto-render as task_card blocks, providing a seamless user experience.
  • Verify the implementation by testing the task_card blocks and streaming API in different scenarios, including DM threads and channels.

Example

{
  "blocks": [
    {
      "type": "task_card",
      "text": {
        "type": "plain_text",
        "text": "Routed to billing skill",
        "emoji": true
      },
      "checked": true
    }
  ]
}

This example shows a simple task_card block that can be used to display live progress updates.

Notes

The current workaround using exec to call openclaw message send/edit CLI or raw curl to Slack API is clunky and requires exec approval. The new implementation should provide a more seamless and efficient way to display live progress updates.

Recommendation

Apply workaround by adding support for Block Kit blocks parameter and implementing streaming API methods, as this will provide the desired "Attio-style" agent UX and enable live progress updates.

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

openclaw - 💡(How to fix) Fix Add Slack streaming API and Block Kit support for agent progress updates [1 participants]