Back to Signal Feed
CodeTracked since May 20, 2026

Switch AGOR Slack output to native Block Kit tables with safe fallbacks

The PR replaces Slack markdown table rendering that previously used monospace code fences by emitting Slack Block Kit `table` blocks, and adds automatic fallback to the legacy monospace section when Slack table size or multi-table limits are hit.

Slack Block Kit tablemarkdown table renderingformatMessagesendMessage

What Happened

  • The PR replaces Slack markdown table rendering that previously used monospace code fences by emitting Slack Block Kit `table` blocks, and adds automatic fallback to the legacy monospace section when Slack table size or multi-table limits are hit.
  • The PR replaces Slack markdown table rendering that previously used monospace code fences by emitting Slack Block Kit `table` blocks, and adds automatic fallback to the legacy monospace section when Slack table size or multi-table limits are hit.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Implemented markdown-to-Slack table conversion that renders the first/eligible table as a native `table` block and introduces per-table fallback checks for Slack limits (oversized cells/rows/columns or second+ table), while extending the message contract to carry block payloads through the gateway route.

Why Track This

Why It Matters

Slack users of AGOR now get cleaner, aligned table messages in Slack instead of code-block-wrapped text, so operational and monitoring data in tables is easier to read at a glance and still avoids message failures by falling back to a known-safe format when limits are exceeded. This also changes the gateway contract to propagate optional block payloads end-to-end, which can affect message compatibility in custom integrations; monitor whether fallback triggers correctly at limit boundaries and whether Slack API responses change for messages that include blocks.

Impact

Slack users of AGOR now get cleaner, aligned table messages in Slack instead of code-block-wrapped text, so operational and monitoring data in tables is easier to read at a glance and still avoids message failures by falling back to a known-safe format when limits are exceeded. This also changes the gateway contract to propagate optional block payloads end-to-end, which can affect message compatibility in custom integrations; monitor whether fallback triggers correctly at limit boundaries and whether Slack API responses change for messages that include blocks.

What To Watch Next

  • Watch whether Slack Block Kit table becomes a repeated pattern.
  • Track follow-up changes around AI Workflow Automation.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: table_fallback_limit_regression, block_payload_format_incompatibility.
Open Topic TimelineOpen Technical EventOpen Original Sourcetable_fallback_limit_regression / block_payload_format_incompatibility / slack_message_rendering_failure

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

preset-io/agor PR #1225: feat(gateway/slack): render markdown tables as Block Kit table blocks

Pull request #1225 updates the AGOR gateway’s Slack path so `formatMessage`/`sendMessage` can return and pass an optional block payload, using native Slack tables for eligible markdown tables while preserving behavior for oversized or extra tables.