Hi ClickUp team,

I’d like to report what appears to be a platform-level issue with AI Agent task creation from DM/chat context.

Summary

I created an AI Agent with a very simple workflow:

accept plain-text task titles, one per line

create one ClickUp task per line in the active sprint

leave the task description empty unless explicitly provided

do not attach, copy, quote, summarize, or link the triggering thread/comment/DM into the created task

Despite repeated instruction updates, the created tasks are still getting the originating thread/comment attached.

Why this seems like a product issue

This behavior persisted even after multiple attempts to harden the agent configuration:

explicitly forbidding comments on created tasks

explicitly forbidding copying or linking the source thread

restricting the workflow to DM only

disabling @mentions

reinforcing the same rule in trigger-specific instructions

Because the behavior remains unchanged, this does not appear to be a normal prompt-following issue. It looks more like the task-creation flow is inheriting conversation context automatically.

Expected behavior

When the agent creates tasks from a DM or chat instruction:

each task should be created cleanly from the provided title

the task should not inherit the source thread/comment unless explicitly requested

the agent’s instruction to avoid attaching thread context should be respected

Actual behavior

The created tasks still include or attach the source thread/comment context, even when the agent is specifically instructed not to do so.

Why this matters

This is one of the most basic and valuable agent workflows:

capture tasks from chat

convert them into ClickUp tasks

keep the tasks clean and production-ready

If source-thread attachment cannot be prevented, it makes this workflow unreliable and creates noise in the resulting tasks.

Request

Please investigate whether task creation initiated from DM/chat-based AI Agent workflows is automatically attaching source conversation context outside the agent’s prompt control.

If this is intended behavior, there should be a way to disable it.

If it is not intended, it should be treated as a bug because it breaks a very common task-capture use case.

Thanks.