# Chat SDK agents can now stream generative UI with json-render

Source: [Vercel](https://vercel.com/changelog/json-render-and-chat-sdk-agents)  
Feed7 permalink: https://feed7.dev/p/json-render-and-chat-sdk-agents-0oce1io  
Published: 2026-11-06T21:00:00.000Z  
Trust: Official Source (official_source)

## Why Included

Chat SDK agents can stream typed JSON specs into platform-native cards through json-render. Schema validation and platform limits help catch malformed or oversized cards before they reach users.

## Source Summary

With **json-render**, a Chat SDK agent emits a JSON spec from a typed component catalog, which is rendered as a native card such as Slack Block Kit or Teams Adaptive Cards. Cards can include tables, charts, and buttons.

## Practical Implication

Builders can stream a card as content arrives; updates are sent at most every **500 ms** by default. Validate generated specs with `toCard`, and pass platform limits to reject cards that exceed an adapter’s capacity.

## Agent-Ready Context

With **json-render**, a Chat SDK agent emits a JSON spec from a typed component catalog, which is rendered as a native card such as Slack Block Kit or Teams Adaptive Cards. Cards can include tables, charts, and buttons.

Builders can stream a card as content arrives; updates are sent at most every **500 ms** by default. Validate generated specs with `toCard`, and pass platform limits to reject cards that exceed an adapter’s capacity.

Without explicit limits, adapters may degrade excess content; for example, Slack converts a second table into a code block. Validation can return issues for correction, but does not guarantee the model will produce a valid replacement.

## Connected Context

Feed7 judgment across 1024 accumulated Signals:

This gives Chat SDK agents a typed path from generated JSON to native interactive cards, with streaming, validation, and adapter limits. Validation can flag invalid or oversized specs, but does not ensure the model will correct them; platform-specific capacity still shapes what renders.

- [Pause workflows for approval with Chat SDK](https://feed7.dev/p/chat-sdk-durable-approvals-1yfmvu0) — Durable approvals use human decisions within Chat SDK workflows, while json-render provides a way to render native cards; together they clarify that card presentation and pausing or resuming the workflow are separate concerns.
- [Chat SDK adds Instagram adapter](https://feed7.dev/p/chat-sdk-adds-instagram-adapter-1kd8zgd) — Both concern native interactive cards across Chat SDK channels; the Instagram candidate highlights adapter-specific constraints, which fits json-render’s requirement to validate against each platform’s limits.

## Context Map

- Layer: tools
- Domains: coding
- Topics: agent-sdks, dev-ux, tool-use

## Uncertainty

- Without explicit limits, adapters may degrade excess content; for example, Slack converts a second table into a code block. Validation can return issues for correction, but does not guarantee the model will produce a valid replacement.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.
