Back to Signal Feed
CodeTracked since May 20, 2026

Render AGOR Slack markdown tables as native Block Kit tables

AGOR’s Slack connector now converts eligible outbound markdown tables into Slack Block Kit `table` blocks instead of triple-backtick monospace blocks, with automatic fallback to the existing monospace section when Slack table limits are exceeded (including too many columns/rows/large cells or a second table in the same message), while non-table messages preserve the previous text-only wire shape.

AGOR gatewaySlackConnectorSlack Block Kit tableformatMessage

What Happened

  • AGOR’s Slack connector now converts eligible outbound markdown tables into Slack Block Kit `table` blocks instead of triple-backtick monospace blocks, with automatic fallback to the existing monospace section when Slack table limits are exceeded (including too many columns/rows/large cells or a second table in the same message), while non-table messages preserve the previous text-only wire shape.
  • AGOR’s Slack connector now converts eligible outbound markdown tables into Slack Block Kit `table` blocks instead of triple-backtick monospace blocks, with automatic fallback to the existing monospace section when Slack table limits are exceeded (including too many columns/rows/large cells or a second table in the same message), while non-table messages preserve the previous text-only wire shape.
  • 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 Slack-specific markdown table rendering path that prefers native Block Kit tables and introduced deterministic fallback rules so large or multiple tables remain visible through the existing monospace format without changing behavior for non-table messages.

Why Track This

Why It Matters

Slack messages sent from AGOR now show small markdown tables in a readable native table layout instead of code fences, so teams can scan structured updates faster and avoid manual interpretation or reformatting, while large/extra tables still render safely via fallback paths. The change introduces a new `OutboundPayload` contract (`text` plus optional `blocks`) and passes blocks through `SlackConnector.sendMessage` so render formatting is controlled at the gateway layer; operators should monitor fallback triggers around 20-column/100-row/cell-size limits and verify multi-table messages across environments to catch any future Slack limit or contract compatibility regressions.

Impact

Slack messages sent from AGOR now show small markdown tables in a readable native table layout instead of code fences, so teams can scan structured updates faster and avoid manual interpretation or reformatting, while large/extra tables still render safely via fallback paths. The change introduces a new `OutboundPayload` contract (`text` plus optional `blocks`) and passes blocks through `SlackConnector.sendMessage` so render formatting is controlled at the gateway layer; operators should monitor fallback triggers around 20-column/100-row/cell-size limits and verify multi-table messages across environments to catch any future Slack limit or contract compatibility regressions.

What To Watch Next

  • Watch whether AGOR gateway becomes a repeated pattern.
  • Track follow-up changes around Structured Outputs.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: watch_slack_table_cap_changes, watch_fallback_trigger_regressions.
Open Topic TimelineOpen Technical EventOpen Original Sourcewatch_slack_table_cap_changes / watch_fallback_trigger_regressions / watch_contract_compatibility_for_non_slack_connectors / watch_payload_field_presence_in_monitoring_and_logging

Supporting Evidence