Feature Requests

Summary Enable ClickUp Brain to generate executable “mini‑apps” from natural language prompts and workspace context. These apps should read and write ClickUp data (Lists, Tasks, Docs, Dashboards, Custom Fields, Tags, Comments, Attachments) with permission‑aware access and run as dynamic, interactive tools embedded in ClickUp. Support both internal workflows (inside ClickUp) and external use (lightweight client portals, prototypes, single‑task utilities). Problem Brain is strong at reasoning and content generation, but many high‑value workflows still require stitching views together, manual data transforms, or repetitive actions across Lists/Docs/Tasks. Teams need small, purpose‑built interactive tools that bind to live ClickUp data, execute multi‑step actions, and share outputs without leaving ClickUp or building separate integrations. Proposed Solution Introduce Brain‑generated mini‑apps that: Bind to data: Connect to Lists, Tasks, Docs, Dashboards, Saved Filters; expose fields and relations; support query, aggregate, and live updates. Extend to external data: Connect to Google Drive, GMail, Google Calendar, and other data sources. Provide interactive UI: Forms, tables, charts, buttons, wizards; adapt based on context (assignees, statuses, tags, custom fields). Execute actions: Create/update tasks and docs, set statuses, add comments, trigger automations, post to Chat, write to custom fields. Are permission‑aware: Enforce roles/custom roles/sharing for all reads and writes. Are deployable: Launch from Chat, Task, Doc, Dashboard, or standalone panel; share internally or externally with controlled access. Are composable: Save as templates, version apps, branch/test changes, reuse across Spaces. Example Mini‑Apps NDA Generator: Pick a template, fill variables (party names, dates, jurisdiction, term), render a final NDA, attach to the Task/Doc, post a Chat message, and open a “Sign & Track” task with due dates. Marketing Spend Planner: A calculator bound to campaign Lists and budget fields; model scenarios, generate a summary Doc with charts, and create tasks to adjust budgets and assign owners. Contract Clause Analyzer: Paste text or select a Doc; the app highlights risky clauses, suggests redlines, and opens subtasks for each recommended change, citing sections. KPI Narrative Builder: Read Dashboard widgets; explain trends, anomalies, and risks; propose follow‑up tasks with owners and dates; post a summary to the channel. Spec‑to‑Plan Converter: Pull a Doc, extract milestones, produce a dependency graph and sequenced subtasks, each citing source sections; dry‑run changes, then commit. Bug Triage Console: Intake reports (attachments, text), group by component/severity using workspace fields, mass‑create/update tasks, and publish a triage summary back to Chat. Governance & Safety Admin controls: Enable/disable Brain mini‑apps; define scopes (space/folder/list); approve data bindings and actions; set external sharing rules. Audit & observability: Log prompts, context accessed, data mutations, and app versions; exportable for compliance. Data boundaries: No cross‑workspace leakage; retention and deletion aligned with ClickUp policies; strict permission inheritance. Cost/performance: Rate limits, quotas, resource controls; “dry run” previews for bulk changes. Success Metrics Reduced time‑to‑action from prompt to committed changes. Lower app‑switching; faster decisions in Chat/Tasks/Docs. Improved data quality via structured inputs and governed bulk updates. Adoption of mini‑apps across teams; increased external collaboration.

Problem: Today, auto-scheduling only applies to Personal Notetaker. For teams that want a single, shared set of meeting notes (via Workspace or Shared Notetaker), someone must manually toggle the notetaker type on every individual meeting. At scale, this creates inconsistency: notes get missed when people forget, and if multiple team members enable Personal auto-scheduling for the same meeting, it burns through usage minutes on duplicate notes nobody needs. Proposed solution: Allow workspace admins to set a default notetaker type (Personal, Shared, or Workspace) for auto-scheduled meetings, either at the workspace level or per user. Ideally this would include: A workspace-level setting for admins to define the default notetaker type for all auto-scheduled meetings Rules or filters (e.g. by calendar, keyword in meeting title, or attendee domain) to auto-assign Workspace or Shared Notetaker to specific meetings The ability for individual users to still override the default on a per-meeting basis Who this helps: Agencies and client-services teams who need shared meeting notes across account teams. Today we have 15+ people running client calls daily. Asking each person to manually switch notetaker type per meeting is unsustainable and leads to gaps in documentation. Current workaround: Everyone uses Personal auto-scheduling. Account leads manually switch to Shared for key client calls. Notes frequently get missed or duplicated.

I’ve been using Super Agents to handle the administrative side of my real estate business, and it has honestly been one of the most valuable AI features inside ClickUp—until the credits run out. Instead of creating four or five different Super Agents, I’ve found that having one primary Super Agent that understands my business and can handle multiple administrative functions works incredibly well. My entire business is managed through ClickUp, so being able to have an AI agent assist with tasks, workflows, follow-ups, and other administrative work is a game changer. There are a few improvements I would LOVE to see: Unlimited Super Agent usage with Everything AI We already pay for Everything AI, but Super Agents are the AI feature I use the most. I would love to see Super Agent usage become unlimited—as part of the Everything AI plan. The credit limitation is especially concerning as I grow my real estate team. Ideally, I would like each human agent on my team to have their own virtual executive assistant/Super Agent that can help manage their administrative workload inside our ClickUp system. The value is incredible, but if agents continually run out of credits, it becomes difficult to build Super Agents into our everyday business operations. Voice conversations with Super Agents Please add the ability to have natural back-and-forth voice conversations with Super Agents. As a real estate agent, I spend a significant amount of time driving between appointments, properties, clients, and the office. Being able to simply talk to my Super Agent instead of stopping to type would save an enormous amount of time. I want to be able to say things like, “Create a follow-up task for this client,” “What are my priorities today?” or “Update this transaction task,” and have my Super Agent handle it while continuing the conversation with me. Apple CarPlay integration This would be HUGE for people who work on the road. ChatGPT and Claude have demonstrated how useful voice AI can be while driving. If ClickUp had a CarPlay experience that allowed us to communicate with our Super Agents by voice, I could accomplish a large portion of my administrative work safely while traveling between appointments. By the time I arrived at my next client appointment, tasks could already be created, notes captured, follow-ups organized, and my ClickUp workspace updated. My entire business runs through ClickUp. Super Agents have the potential to become much more than another AI feature—they could essentially become virtual executive assistants for every person on a team. For businesses like mine, that would be an absolute game changer. The biggest obstacle right now is simply running out of credits on the feature that provides the most value.

Artifacts currently have no storage beyond the viewer's own browser, so nothing they produce survives reliably or can be shared between users. Even a simple serial number generator becomes unusable: the counter is lost when the browser cache is cleared, and two people using it get different numbers. Artifacts need access to a database or persistent memory, shared across everyone who opens the artifact.

It would be super helpful if Agents could update the icon of a page in Docs. We use icons to visually classify different groups of pages & subpages - our agent(s) who make new pages can't update these icons, so it is a tedious job that a human has to do...the definition of a job an agent should do.

When doing an AI report on a dashboard of the last month - it cannot read the Time off data to ensure it reports if people were OOO as a reason for not meeting targets etc. This is very frustrating as we used to capture the information in tasks, but changed to the Time Off feature when that came out, but in order to report it seems we need tasks again now.

The AI usage dashboard is a great start, but admins need deeper insights. We can see total credits consumed, but not who used them or what generated the usage. Adding user-level analytics, feature-level breakdowns, filters, exports, and usage alerts would make it much easier to manage AI adoption and credit consumption.

Would be awesome to have a read-aloud button to listen to ClickUp AI Brain responses. This can also be a good setup for a future conversational-style setup where you tap the button and you and ClickUp Brain can talk back and forth.

Deactivating a Super Agent pauses it against future triggers. From the documentation, there is no way to stop a run that is already executing. AI Hub even surfaces a "Runs in Progress" count, so the platform knows what is in flight, but there is no action attached to that number. For teams running agents with write access across a workspace, that is the difference between a safety control and a suggestion. If the only thing that ends a run is the run finishing, the stop condition belongs to the agent rather than to the admin. Today an admin assembles the picture by hand across five read-only surfaces: AI Hub for a live-run count, Activity for what ran and where, Workspace audit logs for configuration change, each agent's profile for its tools and permissions, and the App Center for MCP and credential reach. None of them has a button. The ask: one admin console, with two stop controls. Live roster of every agent: online state, runs in progress, trigger source Where each live run's output is landing right now — which task, doc, channel or DM Tools, locations, MCP connections and credentials per agent, side by side Halt one agent — end its runs now, leave everything else working Freeze the workspace — one action, all agents, all runs Both logged, and both notifying the users whose work was interrupted rather than leaving them to discover a silent stop Per-agent baselines, so an abnormal run rate, cost spike or tool-call burst raises a flag instead of waiting for someone to read a log Related, same root problem (happy to split these into separate posts if that is easier to triage): Re-evaluate permissions and tool grants at each tool call rather than once at dispatch, so revoking access lands inside a live run. Where boundary state is ambiguous, block and escalate rather than proceed. Deny-write by default on agent instructions and persistent memory, with an origin marker showing whether an instruction block was human- or agent-authored. Express agent network reach as an admin-held domain allowlist instead of a yes/no on web access. Skill provenance: pin a content hash at approval and re-verify on load for any external URL a Skill resolves at runtime, plus an inventory and a revocation path tied to offboarding. Enforced cross-agent boundaries: no agent editing another agent's instructions or memory, and inter-agent trigger rights as a narrow explicit grant rather than a default. Full evidence base, with sourcing and an interactive mock of the console: https://2229230.clickup.ai/a/h/240ze-107651/8f1dd54830010ba Happy to walk through any of this with the Super Agents team. There’s sourcing from an IBM security conference discussion along with primary sourcing that really shows this is a serious need for enterprise level deployments.

I would like to be able to take an artifact I have created and move it to a list or folder level.