Feature Requests

I'm the project manager and like to keep everything connected. Sometimes, people send messages in the channel that should be replies in a thread. I'd like the ability to move those messages to a thread once they have been posted.

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.

Add a pen to highlight anything on shared screen of the other person so that we can guide them with tasks.

Hi ClickUp Support, I'm using ClickUp Desktop on Linux (AppImage) and spellcheck has stopped working in the chat editor. It used to highlight misspelled words, but it no longer does. Environment: OS: Ubuntu/Linux ClickUp Desktop (AppImage) Electron 41.2.0 / Chrome 146.x What's happening: Spellcheck is enabled in system preferences (~/.config/ClickUp/preferences.json has "dictionaries": ["en-US", "ru-RU"]), and the Electron session confirms it is active (spellCheckerEnabled: true, languages: ["en-US", "ru-RU"]). However, right-clicking on a clearly misspelled word always shows an empty misspelledWord field with no suggestions. Root cause I identified: The ProseMirror-based chat editor intercepts all keyboard input via beforeinput event and calls preventDefault() before inserting text directly into the DOM. Because of this, Chrome's input pipeline never registers the keystrokes as "user-typed text" - which is a prerequisite for the native spellchecker to run. As a result, spellcheck is silently skipped regardless of session or element-level configuration. This is a known incompatibility between ProseMirror's input handling and Chromium's spellcheck mechanism. Request: Please integrate spellcheck at the ProseMirror/editor level directly - either by using a JS-based spell checking library (e.g. nspell, typo.js) or by invoking Electron's webContents.session.checkSpelling() on words after they are committed to the editor state, and surfacing corrections through the editor's own suggestion UI or context menu. This is a significant usability issue for non-English speakers who rely on spellcheck to write in multiple languages. Thank you.

Searching channels is not intuitive, would be good to have tags or categories or similar to find channels quicker

Instead of adding my 20 members of a Team I would love to just share a channel with an entire Team with one click

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.

Allow one to send a message as "silent" which does not notify the other person with a sound. This is great for use cases where you want to message someone, but it really does not matter that they reply directly. Discord implements this by prefixing a message with "@silent". Messages sent that way should have a small icon indicating that they were sent "silent".

At the moment, when a Guest is given access to a chat channel, they can then initiate DM's with people. It would be great to be able to turn this off for guest users.

Currently we have to add people to the im channels at a time. I wish I could add to multiple channels at once.