We are building an ecosystem of ClickUp Super Agents, starting with Absencia and Onboardia, and need natural participation in ongoing Chat threads without repeated mentions. Submitted following Niko's recommendation in ClickUp Support ticket #2769821.

Expected behaviour

• Once an agent is @mentioned, clearly addressed by its plain-text name, or joins a conversation, it follows that thread within its permitted scope.

• It receives and reads later replies, including contextual follow-ups such as “What do you think?” with no name or @mention. It then answers the latest relevant question, or acknowledges it with an appropriate native emoji or brief reply.

• This also works between agents. When one agent directly addresses another, the recipient acknowledges that message. Acknowledgments are terminal; they must not create an endless agent-to-agent loop.

• Replies remain in the original thread, authored by the actual native Super Agent, with genuine recipient mentions where appropriate. Following a thread must not expand permissions or grant operational authority.

Requested native capability

Please provide durable Super Agent thread subscriptions and a reliable “reply posted in a followed thread” event, independent of repeat mentions. Ideally this should include automatic enrollment, permitted-channel controls, follow/unfollow or mute controls, restart/catch-up behaviour, deduplication, native reply/reaction support, and bounded agent-to-agent acknowledgment. Reading every new message in a followed thread should be separate from deciding whether to interrupt or reply.

How this differs from Ambient Replies

ClickUp Support explained on 5 October 2026 that Ambient Replies covers follow-ups from the same person after a real @mention. The remaining gaps are replies from other thread participants, automation-started conversations, plain-name enrollment, lasting subscriptions and subscription controls, and bounded agent-to-agent acknowledgments. Support also explained that a guard may leave follow-ups unanswered and selects one agent per message. We need each relevant subscribed agent to receive the event, with a separate relevance decision and loop limits controlling its response. This request extends native conversation delivery beyond the current Ambient Replies scope.

Working external workaround

We currently use a small Python background worker on Render with one instance and persistent SQLite state. Within explicitly permitted channels, the ClickUp Chat API discovers roots and reads thread replies and native tagged users. Mentions, clear names and native participation establish durable per-agent subscriptions. New messages enter a deduplicated persistent outbox keyed by workspace, channel, thread, source message and agent. Polling is bounded and rate-limited, with a grace period for native handling.

Where delivery is needed, the worker sends a technical envelope with source identifiers to the native agent's verified private invocation DM. The agent fetches the real thread context and replies or reacts in the original thread. Reasoning stays with the native ClickUp Super Agent; there is no external LLM. Employee narratives are not copied into the envelope or stored in the relay database/logs. Delivery intent is recorded before sending, uncertain outcomes are reconciled before retries, and native replies/reactions are independently verified. Human questions take priority, and self-messages and terminal acknowledgment loops are suppressed.

We have verified unnamed follow-up replies by both native agents in our configured shared channel, restart deduplication, and bounded mutual acknowledgment. Coverage is scoped, not workspace-wide. We are retaining this relay for now and deferring migration to native handling.

Why native support matters

This should not require customers to operate extra hosting, credentials, polling, persistent state and deployments. A native implementation should preserve permissions, privacy and original-thread context while making event delivery observable and reliable. Acceptance should cover same-user and different-user follow-ups without re-mentioning, automation-origin threads, more than one relevant agent, restart/catch-up without duplicates, and terminal agent-to-agent acknowledgments. We would be happy to test native support so we can eventually retire the external relay.