Back to Signal Feed
CodeTracked since May 20, 2026

Agor Slack gateway switches markdown table rendering to native Block Kit

The PR changes Slack outbound message handling so markdown tables are rendered as native Slack Block Kit `table` blocks by default, with automatic fallback to the previous monospace section only when Slack table limits are exceeded or when a second table appears in the same message.

SlackBlock Kit table blockmarkdown table renderingformatMessage

What Happened

  • The PR changes Slack outbound message handling so markdown tables are rendered as native Slack Block Kit `table` blocks by default, with automatic fallback to the previous monospace section only when Slack table limits are exceeded or when a second table appears in the same message.
  • The PR changes Slack outbound message handling so markdown tables are rendered as native Slack Block Kit `table` blocks by default, with automatic fallback to the previous monospace section only when Slack table limits are exceeded or when a second table appears in the same message.
  • 1 evidence item attached for review.

What is Different

Before

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

Now

Added a block-aware message contract (`OutboundPayload`) and updated `formatMessage`/`sendMessage` to carry optional Slack blocks, then implemented `markdownToSlackPayload()` so normal markdown tables go out as native Slack tables while the system falls back to monospace code-fence formatting when table size/cell/multi-table constraints are exceeded.

Why Track This

Why It Matters

Users and operators sending tables through agor to Slack now get clearer, properly aligned table rendering in common cases instead of crude code-block formatting, while oversized or repeated tables still remain readable through a controlled fallback path. Continue monitoring `blocks` payloads for Slack API schema errors and watch fallback-trigger behavior around wide/long/multi-table messages, because those edge cases are now the practical correctness boundary of the new rendering path.

Impact

Users and operators sending tables through agor to Slack now get clearer, properly aligned table rendering in common cases instead of crude code-block formatting, while oversized or repeated tables still remain readable through a controlled fallback path. Continue monitoring `blocks` payloads for Slack API schema errors and watch fallback-trigger behavior around wide/long/multi-table messages, because those edge cases are now the practical correctness boundary of the new rendering path.

What To Watch Next

  • Watch whether Slack becomes a repeated pattern.
  • Track follow-up changes around AI Integration in IDEs.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: watch_slack_block_payload_schema_regressions, watch_large_or_multi_table_fallback_behavior.
Open Topic TimelineOpen Technical EventOpen Original Sourcewatch_slack_block_payload_schema_regressions / watch_large_or_multi_table_fallback_behavior / watch_connector_payload_type_assumptions

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

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

Replace monospace code-fence table wrapping with Slack Block Kit `table` blocks for outbound markdown tables, with dynamic fallback handling and payload-contract updates.