Feature Requests

Currently, replies in threads (both in channels and direct messages) are only visible in the “Replies” section and do not consistently affect chat visibility or unread indicators in the main “Chat” list. This creates a fragmented and confusing experience when trying to follow ongoing conversations. Key issues: Chat ordering When I receive a reply in a thread within a channel, the channel does not move to the top of the Chat list. Chats are only surfaced when someone starts a new top-level message or sends a new DM. As a result, active discussions happening inside threads are easy to miss unless the user actively checks the Replies tab. Missing unread indicators for thread replies (channels & DMs) Replies added to existing threads do not trigger any unread indicator (badge/counter) on the corresponding channel or direct message in Chat list. The red dot appears only for new top-level messages, not for thread replies. This makes it unclear where new activity has occurred and causes important replies to be overlooked. Also, as a result, active discussions happening inside threads are easy to miss unless the user actively checks the Replies tab. Requested improvement: Thread replies should be treated as first-class chat activity: Channels and DMs should move to the top of the Chat list when a followed thread receives a new reply. Channels and DMs should display an unread indicator (badge/counter) when there is new activity inside a thread. Notification and visibility behavior for thread replies should be consistent across channels and direct messages. This would significantly improve conversation tracking, reduce missed replies, and make the Chat experience more intuitive, especially for teams that rely on threads for async communication.

Summary Enable teams to interact with Claude (including Claude Code) directly within ClickUp Chat—via DMs, channels, and threads—and allow Claude to securely use ClickUp Workspace context (tasks, docs, attachments, comments, tags, statuses, dashboards, automations) to provide accurate, actionable assistance. Mirror the Claude + Slack experience so users can @mention Claude in threads, open an assistant panel, and route coding tasks to Claude Code sessions—without leaving ClickUp. Problem Today, ClickUp AI is powerful, but many teams rely on Claude for coding, reasoning, and safe enterprise workflows. External models in ClickUp cannot answer with private Workspace data, which limits quality for real-world work like triaging tasks, summarizing docs, or generating PRDs with references. Meanwhile, developers and PMs collaborate in ClickUp Chat and threads, but can’t: Ask Claude to read linked tasks/docs and respond with in‑context answers. Route code/debug requests to Claude Code from within a channel or DM. Summarize a thread with citations to relevant tasks and docs. Automate follow‑ups (create tasks, update statuses, add comments) based on Claude’s suggestions. Proposed Solution Bring first‑class Claude integration to ClickUp Chat with these capabilities: 1) Surfaces Direct message with @Claude inside ClickUp Chat. Assistant panel accessible from Chat to consult Claude anywhere. Thread participation: @mention Claude in any channel/thread to assist, summarize, or generate outputs. 2) Claude Code routing Recognize coding intents in Chat and launch a Claude Code session (with code diffs/snippets attached). Let users hand off logs, code blocks, or task-linked repositories to Claude Code and receive fixes or patches back. 3) Secure context connectors Opt‑in connectors that let Claude read permitted context: Tasks, Docs, Comments, Attachments, Tags, Assignees, Statuses, Custom Fields, Dashboards, Automations metadata. Fine‑grained scoping (Space/Folder/List/Task/Doc) with role/permission inheritance; admins control what Claude can query and write. 4) Read and write operations (permissions-aware) Read: Search and reference relevant Workspace content with links back to sources. Write: Create/edit tasks, update statuses/fields, add comments, generate Docs, and post summaries—only where the user has permission. “Dry run” mode to preview changes before applying. 5) Enterprise controls Admin enablement per Workspace with org-wide or selective deployment. Audit logs for every Claude action (prompt, context accessed, changes made). Data boundaries: No cross‑workspace leakage; retention aligned to ClickUp policies. Per-user toggles to enable/disable Claude context use per conversation. 6) Great UX in Chat Unread indicators and chat ordering updated when Claude replies in threads. Inline citations to tasks/docs; expandable previews. One‑click actions: “Create task,” “Add comment,” “Update status,” “Start doc.” Saved prompts and reusable workflows. Example Use Cases In‑thread code debugging with Claude Code: Post a stack trace or failing snippet in Chat and have Claude Code analyze, propose a patch, and return a diff linked to a new task—directly from the thread. Repository‑aware fixes: Attach logs and task‑linked repo context so Claude Code generates precise changes (file paths, functions, tests) and opens a checklist task with patch steps. Cross‑artifact synthesis with citations: Ask Claude to summarize a conversation while pulling and citing relevant Tasks, Docs, comments, and attachments it discovered across Spaces/Lists. Permission‑aware bulk updates from Chat: “Close all tasks tagged ‘release‑blocked’ if PRs are merged” with a dry‑run preview, then apply changes respecting user roles. Multi‑component bug triage: Group incoming bug reports by component, severity, and assignee using workspace tags/custom fields, then create or update tasks at scale from one prompt. Requirements & Safeguards Respect ClickUp Roles/Permissions and Custom Roles; Claude acts only within the invoking user’s rights. Admin configuration: enable Claude app, context connectors, and Code routing; org and workspace scopes. Clear indicators when Claude used Workspace context; easy disconnect and per-chat disable. Compliant data handling and deletion aligned with ClickUp & customer policies.

It would be great to have a feature, especially for chats where you can record a video of you talking for announcements, etc. Not just the screen recording. This is a feature we use in Slack that we are really going to miss when moving over to Chat.

Reply-in-thread is great for discussions that need long, focused conversations without disturbing others. It works really well when a topic is complex and needs multiple back-and-forth messages. But not every message needs to become a thread. Communication naturally has both short and long conversations. For quick questions or short replies, using threads can feel heavy and slow things down. In those cases, being able to quote a message and reply directly in the main chat is much more useful. It keeps the context clear while making the reply visible right away. This helps team understand faster, scan conversations more easily, and respond more quickly without opening a separate thread. Having both reply-in-thread and quote-reply options would give us more flexibility to communicate in the way that fits each situation best.

It would be wonderful if there was a way that we could add people to a channel that is attached to a list that is like an announcement channel. Admins should be able to post to the channel, but everyone else in the workspace should just be able to view the channel and nothing else. So far our attempts at making the list and corresponding views "View Only" for everyone but admins don't seem to be affecting the channel and we consistently have users posting.

I'm still on the fence about the "everything" representation in the Home sidebar, and I'm glad that my manual Chat channel order is represented there, but forcing the dedicated Chat window to only sort in order of recent use seems bizarre to me. I depend on my manual sort order to quickly get where I need to go in Chat, I never use that "most recent" sort order. Even if you only offered Alphabetical as an alternative, it would be an improvement — at least then I could reliably find any channel where I expect it to be. But Manual/Custom order is my personal preference, I just want a consistent structure that groups things in the way that makes sense for me and my org.

It'd be great to have a read receipt or icon to let users know when a chat message has been read.

In order to convince my team to move from Slack to ClickUp Chat, it needs to be a little more intuitive and user-friendly. 3.0 was actually closer to this and I was beginning to migrate and get people on board, but then 4.0 happened and we had to stop everything and run back to Slack. My baseline needs for ClickUp Chat so that we can ditch Slack are: 1- You can leave the Home tab the way it is, but the ClickUp Chat tab needs to stand on its own and have its own notifications (red number icons on the Chat tab are crucial). 2- Once inside the Chat tab, all channels and DMs should be present, customizable, in their own sections, and have sorting options based on personal preference. 3- Maintain an 'Unread' view that you can leave open and when someone sends a ClickUp Chat message (DM or in a channel), it will appear, no matter what channel or DM it's coming from. This is more of an emphasis - I think this already exists. 4- Once a message is read, it should automatically clear out of the Unread area. And messages should only appear there if they are indeed unread. Right now, if I have the Unread filter on and click into a channel, when I come back to the Unread view, it has that channel displaying in the Unread area even though everything is read. 5- Option to send a reply to a message to the larger channel instead of only nesting it inside of the parent message. 6- Have replies show up as their own notification. 7- Ability to search ClickUp Chat messages only. 8- Somewhere within ClickUp Chat to view recent activity (least important). I think that's all. It has a lot of other really great features, but these basics are necessary for our team. Some of them may already exist, so please kindly point out if that's the case, but I don't see it unless I said so up top haha. Thank you!!

In Slack Huddles, when someone shares their screen others are able to "draw" on the screen being shared using the pen tool. This is extremely helpful for teams working remotely.

As our team grows and expands we find our selves categorizing folders and team lists a little differently but with chat tied to a particular folder, we're unable to really achieve the new task organizing structure we want without losing the chat thread our team has a lot of history with. I know we can create new chat threads but being able to simply disconnect old chat threads from a certain folder or list would be incredibly helpful to not loose data/continuity.