feat(clickup): /agentric keeps one Agentric task per ticket; /agentric <agent> routes off-Slack (v0.431.0) - #804
Merged
Merged
Conversation
…c <agent> routes off-Slack (v0.431.0) First `/agentric` comment on a ClickUp ticket creates a task (`#<ticket id> <name>`, ticket link + description as body, filed/owned by the commenter) and posts its link back; later `/agentric` comments land in that task's discussion. `/agentric <agent> …` reopens a closed task and puts the agent on it — continuing its run if it owns the task, else dispatching a run bound to the ticket so it can `clickup_reply`. Keyed by a new `tasks.external_key` under a partial unique index. Fix: `/agentric <agent>` was only stripped by Slack; on Discord/Telegram/ClickUp it was read as an agent named "agentric". Shared `CHAT_NAMESPACE_RE` now strips it everywhere. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HA3jrB7rENd2zadgxP56Lu
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by an InstaWP operator. They want to work a ClickUp ticket from a single Agentric task, and
/agentricshould work outside Slack too.ClickUp bridge
/agentric <text>looks up the task keyedclickup:<ticket id>and creates it if missing.<text>goes into that task's discussion, where it reaches the live run and triggers any@mentions. It doesn't start an agent.#<custom id or ticket id> <ticket name>and puts the ticket link and description in the body. The commenting member is recorded as filer and owner; an unmapped commenter shows asclickup. One comment with the Agentric task link is posted back to the ticket./agentriccomments land in the same task's discussion, and the reply is just a 👀 reaction./agentric <agent> <request>reopens the task if it's done or cancelled, then puts the agent on it:clickup_replyanswers on the ticket.tasks.external_keycolumn with a partial UNIQUE index. A racing duplicate webhook re-reads the existing task instead of creating a second one.clickup.task.linked,clickup.task.discussed,clickup.task.failed.Fix
/agentric <agent>only worked in Slack, which strips declared slash commands itself. On Discord, Telegram and ClickUp it was read as an agent namedagentric, even though the roster reply tells people to type exactly that. A sharedCHAT_NAMESPACE_REnow strips it everywhere.Verification
scripts/clickup-task-bridge-test.cjs(27 checks), added totest:governance.npm run test:governance, root build and web tsc + build all pass.Docs:
docs/clickup-task-bridge-plan.mdis marked built and lists where the build deviated from the plan.docs/connectors/clickup.mdhas a new section, and the console's ClickUp help text is updated.⚠ Needs a server restart to take effect, because it touches server, store and edge code and adds a migration.
🤖 Generated with Claude Code
https://claude.ai/code/session_01HA3jrB7rENd2zadgxP56Lu