Feature Requests

Make comment private and share only with selected people.

It's so easy to miss the threaded reply as it's currently collapsed by default... could there be an option to keep them expanded? Thanks!

This feature would allow comments on a task to be automatically closed once the task is marked as completed. It prevents further discussion on finalized tasks, reducing unnecessary notifications and ensuring a clean, clutter-free workspace. This option would help maintain focus on active tasks while preserving completed tasks for reference without additional input.

Would like to know who has seen and presumably read comments

Ever since a recent update, I am now longer able to select the gif I want when using the /giphy feature. It now pre-selects a gif for me and I am not allowed to change it unless I change my text search. I like to have these to add a bit of fun too the team but now it is just a huge time waster trying to find an appropriate gif.

There are so many reasons not to use Giphy, morally but also functionally, however it seems to be a 'do what slack does' reaction, instead of 'do what's best', which usually results in implementing whatever a bunch of 70 year old suits think was a good idea 10 years ago. For most things chat, please look towards Discord and away from Slack, GIF's being a prime example. Tenor is a better platform, the ability to choose from a grid of options, instead of refreshing, the list goes on

This request refers to the ClickUp MCP server (Model Context Protocol), used to connect AI agents and assistants to ClickUp programmatically. The scenario is an AI agent tasked with posting structured updates — such as email summaries, meeting notes, or status digests — directly to ClickUp tasks as comments, without manual intervention. Current behavior The clickup_create_task_comment tool exposed by the ClickUp MCP server currently only accepts a comment_text parameter, which sends the comment content as a plain string to the ClickUp API. As a result, any Markdown-like syntax (e.g. bold , italic , @mentions) is treated as literal text and rendered without formatting in the ClickUp UI. Expected behavior Comments created via the MCP tool should support rich text formatting — at minimum bold, italic, headings, and @mention resolution — in the same way that comments typed directly in the ClickUp web editor are rendered. Root cause The ClickUp API supports two distinct modes for comment content: comment_text — plain string, no formatting comment — an array of rich text blocks in ClickUp's proprietary format, which the web editor uses internally The ClickUp MCP server currently only wraps comment_text. Exposing the comment parameter (or an intermediate Markdown-to-ClickUp-rich-text conversion layer) would allow formatted output through the MCP tool as well. Proposed solution Add support for rich text input in the clickup_create_task_comment MCP tool, either by: Accepting a markdown_comment parameter and converting it server-side to ClickUp's rich text block format before calling the API, or Exposing the raw comment array parameter for advanced use cases where the caller constructs the block structure directly. Option 1 is preferred for ease of use, as it would be consistent with the markdown_description parameter already available in the clickup_update_task MCP tool — meaning the pattern is already partially established within the MCP server itself. Impact This limitation affects any AI agent workflow using the ClickUp MCP server where comments are generated programmatically. Without rich text support, the output is harder to read and loses the structure that makes it actionable in context — undermining one of the core use cases for integrating an AI agent with ClickUp via MCP.

Inbox notifications don't show the comment that's being indicated in the initial notification. It is necessary to run, many times, a huge thread that has already been read to access the notified comment. When clicking on the notified comment, we need it to appear at the top of the screen and not lost in the middle of the thread. Below are some examples: https://sharing.clickup.com/clip/p/t90131232415/20c6a85c-dea8-4c00-9785-206bdd4c84f8/20c6a85c-dea8-4c00-9785-206bdd4c84f8 .webm? filename=screen-recording-2026-10 -07-17% 3A49.webm https://sharing.clickup.com/clip/p/t90131232415/53236e28-76a3-42ee-bf50-18700758c392/53236e28-76a3-42ee-bf50-18700758c392 .webm? filename=screen-recording-2026-10 -08-10% 3A37.webm https://sharing.clickup.com/clip/p/t90131232415/27e53bdd-359d-47f6-a93f-1533ce4d098c/27e53bdd-359d-47f6-a93f-1533ce4d098c .webm? filename=screen-recording-2026-10 -08-11% 3A43.webm

We need a workspace-level report/card that shows, for each team member, how many assigned comments they currently have unresolved, regardless of whether the comment is on their own task or someone else’s task. Current limitation: At the moment, users can only see their own assigned comments in Home / Assigned Comments. There is no centralized view for managers or workspace owners to see assigned comment counts for other users, nor a per-user summary. Expected behavior: A list of users with a counter of Unresolved Assigned Comments. Clicking the counter opens a detailed view with the related comments and tasks. Filters: Workspace / Space / Folder / List, date range (optional), priority (optional), team/group (optional). Permissions respected (only show comments the viewer has access to). Optional metrics: overdue assigned comments, aging, trend over time. Use cases: Workload and follow-up visibility for managers, leads, and support teams. Identifying bottlenecks caused by unresolved assigned comments. Prioritization and accountability for reviews and approvals. Acceptance criteria: I can select a scope (workspace or subset) and see unresolved assigned comment counts per user. I can drill down to the underlying comments and tasks. Counts update near real time and respect permissions. Impact: Eliminates manual tracking and the need for external integrations or API-heavy workarounds to understand assigned comment workload across the team.

Replies made to comments within a task are easily lost and should be visible when scrolling through the Activity section. To view the replies you need to click the small text in the bottom right of the comment to see any comments, which is quite crucial when a project relies on what has been commented. I understand if this was done to avoid crowding the Activity section when there are many comments, but in that case only show the first 1-3 comments before having a 'Show more' button or similar. Would really appreciate a change like this and I believe it would boost workflow! Thank you!