Arunkumar Rajasekaran
Allow rich third party agent support in ClickUp chat.
Specifically, here's what's blocking us:
  1. No WebSocket / Persistent Connection API Slack offers Socket Mode — our assistant opens a persistent outbound WebSocket connection and receives events in real-time (sub-second). ClickUp has no equivalent. This is the difference between an assistant that feels instant and one that feels laggy.
  2. No Chat Event Subscriptions We cannot subscribe to real-time events for ClickUp Chat messages (message sent, message updated, mentions, etc.). For task events, ClickUp webhooks work, but Chat has no push mechanism at all. We'd be forced to poll a REST API, which is architecturally fragile and inherently slow.
  3. No Interactive Message Components Slack supports Block Kit — buttons, forms, modals, inline actions. Our assistant can present interactive options, collect input, and trigger workflows directly within a message. ClickUp Chat currently supports only text and basic markdown. There's no way to send a message with an "Approve / Reject" button pair, for example.
  4. No Thread-Level Event Granularity Slack provides thread-scoped events — our assistant can maintain per-topic context in threads, deliver scheduled outputs into specific threads, and keep channels clean. ClickUp Chat doesn't thread at the same level.