Georgi Pepelyankov
We want to make ClickUp Chat our main internal messaging tool. The blocker is that it's a closed room. In Slack and Teams, third-party AI assistants like Claude and OpenAI dots can join channels, get @mentioned, read the thread they're in, and reply natively. ClickUp Chat only works well with ClickUp's own agents. Teams that use more than one model have to keep Slack running just for their AI workflows, so we end up with two chat tools.
What we're asking for:
  • Chat bot/app platform: third-party apps can be installed into a workspace and added to channels and DMs as bot users with their own identity and avatar.
  • @mention and event triggers: bots receive message, mention, reaction and thread-reply events, like Slack's Events API.
  • Native replies: bots post into threads with rich text, attachments, and streamed or updated messages, not just one-way webhooks.
  • Scoped context access: admins grant bots access per channel to read history and linked tasks and docs, using the permissions we already have.
  • Admin controls: an allowlist of approved apps, per-channel install, audit logs of bot activity, and a way to revoke access.
  • Interop with Super Agents: external agents and ClickUp agents can work in the same thread and hand off to each other.
Why it matters: ClickUp is positioning Chat as a Slack replacement. For AI-heavy teams, Slack's biggest advantage right now is that it lets any assistant in. Being model-agnostic in Chat would remove the main reason to keep paying for Slack. It would also make ClickUp the place where people and agents work together, whichever model a team prefers.