chatkit-actions

Bidirectional action handling routes user interactions from client-side widgets to server handlers and back. This Skill enables you to define both client-handled actions (executed in the browser) and server-handled actions (executed on your backend), with automatic state synchronization and context propagation across the chat interface.

Yes. This Skill provides widget templates with full lifecycle support—from creation through replacement—allowing you to track widget state, handle user interactions, and update or remove widgets dynamically within chat workflows without manual context management.

This Skill handles cross-language action routing between TypeScript client-side handlers and Python server-side handlers. It manages action dispatch, hidden context propagation, and response synchronization, so your frontend and backend logic communicate seamlessly without extra integration code.

Widget-driven UX requires context to persist through action routing. This Skill automates hidden context propagation alongside action handlers, ensuring that state updates, navigation, and widget replacement maintain full context visibility across client and server boundaries.

No. This Skill unifies client-handled and server-handled action patterns under a single routing system. You define actions once and specify their execution target (client or server); the framework handles dispatch, state sync, and lifecycle events automatically.

Widget replacement is part of the full lifecycle this Skill manages. When a widget is replaced or removed, action handlers clean up, state is reset, and subsequent actions route to the new widget or stop gracefully, with no orphaned handlers or memory leaks.