Skip to content

Register Slack charts as Channel components - #26

Merged
tylerslaton merged 2 commits into
mainfrom
update-slack-data-visualization
Aug 3, 2026
Merged

Register Slack charts as Channel components#26
tylerslaton merged 2 commits into
mainfrom
update-slack-data-visualization

Conversation

@tylerslaton

Copy link
Copy Markdown
Contributor

Summary

  • convert render_chart from a manually posted defineChannelTool to defineChannelComponent
  • register RenderChart through createChannel({ components })
  • remove the duplicate manual entry from appTools
  • preserve native Slack.Block.DataVisualization rendering on Slack and render a portable unsupported-platform notice elsewhere
  • add a Channel-level integration test proving an agent component call posts the native Slack visualization block

Why

The initial visualization PR used the new Slack block but did not use the Channels SDK's agent-rendered component abstraction. This follow-up makes render_chart a first-class Channel component so the SDK owns argument validation, posting, and tool exposure.

Impact

The agent-facing name and chart schema remain render_chart; the registration path now uses the component registry as intended.

Validation

  • pnpm install --frozen-lockfile
  • pnpm check-types
  • pnpm test — 160 passed
  • cd agent && uv run pytest — 70 passed
  • node node_modules/railway/dist/iac/bin.js
  • git diff --check

@tylerslaton
tylerslaton marked this pull request as ready for review August 3, 2026 21:12
Signed-off-by: Tyler Slaton <tyler@copilotkit.ai>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant