### What version of the Codex App are you using (From “About Codex” dialog)? `26.707.8168.0` Microsoft Store package: ```text OpenAI.Codex_26.707.8168.0_x64__2p2nqsd0c76g0 ``` The affected Desktop sessions report the embedded runtime as: ```text originator: Codex Desktop runtime version: 0.144.0-alpha.4 model provider: openai model: gpt-5.6-sol reasoning effort: high ``` A separate standalone `codex-cli 0.114.0` is installed on the machine, but it was not used for the affected connector ca

ClickUp connector exposes clickup_create_task_comment but backend returns "Tool ... not found"

Open 💬 0 comments Opened Jul 13, 2026 by umanamente

What version of the Codex App are you using (From “About Codex” dialog)?

26.707.8168.0

Microsoft Store package:

OpenAI.Codex_26.707.8168.0_x64__2p2nqsd0c76g0

The affected Desktop sessions report the embedded runtime as:

originator: Codex Desktop
runtime version: 0.144.0-alpha.4
model provider: openai
model: gpt-5.6-sol
reasoning effort: high

A separate standalone codex-cli 0.114.0 is installed on the machine, but it was not used for the affected connector calls.

What subscription do you have?

Pro ($100/month)

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

Additional OS information:

Microsoft Windows 11 Home
Version: 10.0.26200
Build: 26200
Architecture: 64-bit

What issue are you seeing?

Summary

Codex Desktop advertises and injects the ClickUp connector tool clickup_create_task_comment, but every invocation is rejected by the connector backend with:

MCP error -32602: Tool clickup_create_task_comment not found

The failure is fully reproducible across fresh and existing Codex Desktop sessions.

At the time of this report:

26 calls were observed.
All 26 calls failed.
No calls succeeded.
The exact same Tool clickup_create_task_comment not found error was returned in all 26 cases.
The calls came from 11 separate Codex Desktop sessions.
The observation window was approximately 9 hours and 40 minutes.
The failure rate was 100%.
A newly created Codex Desktop thread reproduced the problem twice.

This does not appear to be a general ClickUp OAuth, Workspace access, task access, network, or connector initialization failure. In the same connector/link context:

clickup_get_task: 131 successful calls, 0 failures.
clickup_update_task: 23 successful calls, 0 failures.
clickup_get_task_comments: 14 successful calls, 0 failures.
clickup_create_task: 48 successful calls, 0 failures.
clickup_get_list: 22 successful calls, 0 failures.

After a representative failed comment write, clickup_get_task_comments succeeded and confirmed that the task still had zero comments. The failed call therefore produced no partial write.

Impact

This causes partial remote state during automated project workflows:

Codex can read a task.
Codex can update the task status.
Codex cannot add the required audit or handoff comment.
The overall workflow therefore appears partially successful while required evidence is missing.

This is especially problematic for workflows where task comments are the required audit trail for implementation decisions, verification results, commits, blockers, or release evidence.

Retries do not help because the advertised operation is rejected as an unknown tool before the normal ClickUp action can execute.

Exposed tool descriptor

The current Codex Apps tool catalog contains an explicit descriptor for this tool:

catalog schema version: 4
catalog tool count: 373
server_name: codex_apps
connector_name: ClickUp
connector_id: asdk_app_69431e6d26b88191b4029488aeb42f5b
tool_namespace: codex_apps__clickup
tool_name: _clickup_create_task_comment
tool.name: clickup.clickup_create_task_comment
tool.title: clickup_create_task_comment
supports_parallel_tool_calls: false
required input fields: task_id, comment_text
optional input fields: workspace_id, notify_all, assignee

The local resource URI also maps this descriptor to the same backend action:

/asdk_app_69431e6d26b88191b4029488aeb42f5b/link_<redacted>/clickup_create_task_comment

The link ID has been removed from this public report.

The ClickUp plugin manifest reports:

plugin: clickup
version: 1.0.0
developer: ClickUp
repository: https://github.com/openai/plugins
app id: asdk_app_69431e6d26b88191b4029488aeb42f5b

The local tool catalog was refreshed at 2026-07-13T07:01:30.195Z, after multiple observed failures, and it still advertised the unavailable tool. Two more calls from a newly created session failed after that catalog timestamp.

Actual result

A representative sanitized result is:

{
  "content": [
    {
      "type": "text",
      "text": "RuntimeException: Error calling MCP tool: [TextContent(type='text', text='MCP error -32602: Tool clickup_create_task_comment not found', annotations=None, meta=None)]"
    }
  ],
  "structuredContent": {
    "error": "RuntimeException: Error calling MCP tool: [TextContent(type='text', text='MCP error -32602: Tool clickup_create_task_comment not found', annotations=None, meta=None)]",
    "error_code": "INVALID_ARGUMENT",
    "error_data": {
      "type": "mcp_tool_execution_error",
      "result": {
        "content": [
          {
            "type": "text",
            "text": "MCP error -32602: Tool clickup_create_task_comment not found"
          }
        ],
        "isError": true
      }
    }
  },
  "isError": true
}

The result contains a Codex-local call ID but does not contain an upstream request ID.

Representative latest identifiers:

session id: 019f5a42-eb00-76d0-9750-de90659299f5
local call id: exec-e0a9f3df-ac12-4ed5-9a89-22d5ad4b5d90
upstream request id: not provided
timestamp: 2026-07-13T07:10:12.206Z

Reproducibility statistics

Calls: 26
Failures: 26
Successes: 0
Exact "Tool ... not found" results: 26
Distinct sessions: 11

First observed call:
2026-07-12T21:30:08.540Z

Last observed call in this snapshot:
2026-07-13T07:10:12.206Z

Minimum failure latency: 381 ms
Median failure latency: 465 ms
Mean failure latency: 488 ms
Maximum failure latency: 1064 ms

The consistently short latency is compatible with rejection at a connector registry/adapter boundary rather than a ClickUp API request timing out. This is an inference from the observed timings, not proof of the exact backend implementation.

Why this appears to be a catalog/registry mismatch

The following layers work:

The ClickUp plugin is installed and discovered.
The ClickUp app connection is authorized.
The connector link can read tasks and comments.
The same connector link can update tasks.
The same connector link can create tasks.
The local Codex Apps catalog advertises the comment tool and its schema.
Codex successfully invokes the exposed wrapper.

The failure happens when the live connector backend resolves the underlying tool name:

Tool clickup_create_task_comment not found

This differs from the errors observed for malformed arguments, unavailable Workspace selection, missing authorization, or ClickUp server failures.

Other ClickUp connector failures found in the local logs had different and action-specific messages, such as input validation errors, multiple Workspace selection, or not_found_or_authorized. Only clickup_create_task_comment produced this exact unknown-tool error, and it did so on every invocation.

This suggests one of the following:

The Codex Apps catalog advertises a stale or unavailable ClickUp tool.
The Codex wrapper-to-backend name mapping is incorrect.
The upstream ClickUp MCP registry no longer registers the canonical name used by the Codex adapter.
Connector capability discovery and execution are reading different tool versions.
The tool is gated upstream, but the capability catalog does not apply the same gate.

Regardless of the exact cause, the invariant currently appears broken:

AdvertisedConnectorTools ⊆ RegisteredExecutableTools

What steps can reproduce the bug?

Install or enable the official ClickUp plugin in Codex Desktop.
Authorize a ClickUp Workspace.
Start a Codex Desktop thread.
Ask Codex to retrieve an existing task.
Confirm that clickup_get_task succeeds.
Optionally call clickup_get_task_comments; it also succeeds.
Ask Codex to add a plain-text comment to the same task.
Codex discovers and invokes:

``text codex_apps / clickup.clickup_create_task_comment``

The invocation has this sanitized shape:

``json { "task_id": "<redacted regular ClickUp task ID>", "workspace_id": "<redacted Workspace ID>", "notify_all": false, "comment_text": "<redacted non-empty plain-text comment>" }``

Observe the result:

``text MCP error -32602: Tool clickup_create_task_comment not found``

Call clickup_get_task_comments again.
Observe that the comment was not created.
Create a fresh Codex Desktop thread and repeat.
Observe the same error.

Observed invocation variants:

25 calls included task_id, comment_text, notify_all, and workspace_id.
1 call included task_id, comment_text, and notify_all, relying on automatic Workspace resolution.
5 calls used comments between 100 and 999 characters.
21 calls used comments of 1000 or more characters.
assignee was omitted because it is optional.
Every variant failed with the same unknown-tool error.

No OAuth tokens, ClickUp secrets, or raw comment contents were inspected or extracted during diagnosis.

What is the expected behavior?

When Codex advertises clickup_create_task_comment as available:

The backend should have a registered executable tool matching the advertised descriptor.
The comment should be created exactly once.
The tool should return the created comment identifier or another explicit success result.
A subsequent clickup_get_task_comments call should return the new comment.

If the upstream tool is not actually available, Codex should instead:

Not advertise it to the model.
Refresh or invalidate stale connector capability metadata.
Mark the connector as degraded if only some tools are executable.
Return a specific capability mismatch diagnostic instead of a generic INVALID_ARGUMENT.
Include an upstream request/correlation ID for support.
Distinguish between:

invalid tool input;
connector authorization failure;
ClickUp API failure;
stale capability metadata;
wrapper/backend name mismatch;
upstream tool not registered.

A connector tool should not be model-visible unless the runtime can execute its mapped upstream operation.

Additional information

Official ClickUp documentation

ClickUp currently documents task comment creation as supported in both its MCP tool set and HTTP API:

Supported MCP tools:

https://developer.clickup.com/docs/mcp-tools

Create Task Comment API endpoint:

https://developer.clickup.com/reference/createtaskcomment

ClickUp's own public feedback item refers to the exact clickup_create_task_comment MCP tool and its comment_text input:

https://feedback.clickup.com/feature-requests/p/support-rich-text-formatting-in-clickup-create-task-comment

The API endpoint is:

POST https://api.clickup.com/api/v2/task/{task_id}/comment

This report does not claim that Codex calls this endpoint directly. The documentation is included to show that task-comment creation is a supported ClickUp capability and that the exact MCP tool name is publicly referenced by ClickUp.

Related Codex reports

The exact ClickUp tool name and exact ClickUp error were searched in openai/codex on 2026-07-13. No ClickUp-specific issue was found.

There are, however, highly similar reports for other Codex Apps connectors:

BioRender app connector exposes tools but backend returns Tool ... not found:

https://github.com/openai/codex/issues/31026

Duplicate/related BioRender report:

https://github.com/openai/codex/issues/31173

Notion connector exposes a tool in schema but runtime says it is not found:

https://github.com/openai/codex/issues/19924

Those reports appear to describe the same general failure class at an app-connector capability or name-translation boundary. This issue adds a ClickUp-specific reproduction with:

a write operation;
26 failures across 11 sessions;
a complete control matrix showing that related ClickUp reads and writes work;
the current catalog descriptor;
a verified absence of side effects;
a full timestamp and latency timeline.

<details>
<summary>Full sanitized failure timeline — 26 calls across 11 sessions</summary>

| Timestamp UTC | Session ID | Duration | Result |
|---|---|---:|---|
| 2026-07-12T21:30:08.540Z | 019f5832-944f-7270-9986-57fd22411e8e | 485 ms | INVALID_ARGUMENT / Tool not found |
| 2026-07-12T21:43:02.604Z | 019f5841-7e58-7270-bc6e-d104003bb92d | 421 ms | INVALID_ARGUMENT / Tool not found |
| 2026-07-12T22:26:33.316Z | 019f585f-be8f-78c1-96fe-4e30993fbe2d | 414 ms | INVALID_ARGUMENT / Tool not found |
| 2026-07-13T00:10:48.531Z | 019f5877-854b-7ac0-a621-9a652ea90072 | 455 ms | INVALID_ARGUMENT / Tool not found |
| 2026-07-13T00:53:04.150Z | 019f58ea-6465-7c82-80a2-bba69594cc9a | 461 ms | INVALID_ARGUMENT / Tool not found |
| 2026-07-13T01:36:47.173Z | 019f590a-01dc-7492-8d61-446dcd7833fd | 450 ms | INVALID_ARGUMENT / Tool not found |
| 2026-07-13T01:37:40.008Z | 019f590a-01dc-7492-8d61-446dcd7833fd | 446 ms | INVALID_ARGUMENT / Tool not found |
| 2026-07-13T03:34:51.496Z | 019f592e-132d-7322-b295-d6f91ebc0cb0 | 434 ms | INVALID_ARGUMENT / Tool not found |
| 2026-07-13T03:34:52.030Z | 019f592e-132d-7322-b295-d6f91ebc0cb0 | 510 ms | INVALID_ARGUMENT / Tool not found |
| 2026-07-13T03:34:52.530Z | 019f592e-132d-7322-b295-d6f91ebc0cb0 | 478 ms | INVALID_ARGUMENT / Tool not found |
| 2026-07-13T03:34:53.026Z | 019f592e-132d-7322-b295-d6f91ebc0cb0 | 470 ms | INVALID_ARGUMENT / Tool not found |
| 2026-07-13T03:34:53.535Z | 019f592e-132d-7322-b295-d6f91ebc0cb0 | 483 ms | INVALID_ARGUMENT / Tool not found |
| 2026-07-13T03:54:37.226Z | 019f592e-132d-7322-b295-d6f91ebc0cb0 | 469 ms | INVALID_ARGUMENT / Tool not found |
| 2026-07-13T05:22:06.571Z | 019f59c2-d266-7081-bcdf-3313bf7b1f07 | 470 ms | INVALID_ARGUMENT / Tool not found |
| 2026-07-13T05:22:07.020Z | 019f59c2-d266-7081-bcdf-3313bf7b1f07 | 419 ms | INVALID_ARGUMENT / Tool not found |
| 2026-07-13T05:22:31.303Z | 019f59c2-d266-7081-bcdf-3313bf7b1f07 | 407 ms | INVALID_ARGUMENT / Tool not found |
| 2026-07-13T06:16:11.202Z | 019f5a10-3120-7151-82cf-ea9743f023d8 | 627 ms | INVALID_ARGUMENT / Tool not found |
| 2026-07-13T06:16:11.611Z | 019f5a10-3120-7151-82cf-ea9743f023d8 | 381 ms | INVALID_ARGUMENT / Tool not found |
| 2026-07-13T06:27:34.099Z | 019f5a10-3120-7151-82cf-ea9743f023d8 | 433 ms | INVALID_ARGUMENT / Tool not found |
| 2026-07-13T06:27:34.601Z | 019f5a10-3120-7151-82cf-ea9743f023d8 | 476 ms | INVALID_ARGUMENT / Tool not found |
| 2026-07-13T06:50:06.929Z | 019f5a32-fe6e-7e71-9208-c29636b23fa2 | 397 ms | INVALID_ARGUMENT / Tool not found |
| 2026-07-13T06:50:07.341Z | 019f5a32-fe6e-7e71-9208-c29636b23fa2 | 381 ms | INVALID_ARGUMENT / Tool not found |
| 2026-07-13T06:50:36.485Z | 019f5a32-fe6e-7e71-9208-c29636b23fa2 | 1064 ms | INVALID_ARGUMENT / Tool not found |
| 2026-07-13T07:00:36.986Z | 019f5a32-fe6e-7e71-9208-c29636b23fa2 | 596 ms | INVALID_ARGUMENT / Tool not found |
| 2026-07-13T07:10:11.648Z | 019f5a42-eb00-76d0-9750-de90659299f5 | 513 ms | INVALID_ARGUMENT / Tool not found |
| 2026-07-13T07:10:12.206Z | 019f5a42-eb00-76d0-9750-de90659299f5 | 534 ms | INVALID_ARGUMENT / Tool not found |

</details>

<details>
<summary>Full ClickUp connector action outcome matrix from the same local log set</summary>

| Action | Calls | Failures | Successes | Exact comment-tool-not-found errors |
|---|---:|---:|---:|---:|
| clickup_create_document | 5 | 5 | 0 | 0 |
| clickup_create_folder | 1 | 0 | 1 | 0 |
| clickup_create_list_in_folder | 8 | 0 | 8 | 0 |
| clickup_create_task | 48 | 0 | 48 | 0 |
| clickup_create_task_comment | 26 | 26 | 0 | 26 |
| clickup_get_folder | 4 | 0 | 4 | 0 |
| clickup_get_list | 22 | 0 | 22 | 0 |
| clickup_get_task | 131 | 0 | 131 | 0 |
| clickup_get_task_comments | 14 | 0 | 14 | 0 |
| clickup_get_workspace_hierarchy | 16 | 8 | 8 | 0 |
| clickup_search | 58 | 5 | 53 | 0 |
| clickup_update_list | 1 | 0 | 1 | 0 |
| clickup_update_task | 23 | 0 | 23 | 0 |

The failures for clickup_create_document, clickup_get_workspace_hierarchy, and clickup_search had different errors, including input validation, Workspace selection, server errors, or not_found_or_authorized.

None of those actions returned Tool clickup_create_task_comment not found.

</details>

<details>
<summary>Sanitized Codex Apps catalog descriptor</summary>

schema_version: 4
total_catalog_tools: 373

server_name: codex_apps
supports_parallel_tool_calls: false

connector:
  name: ClickUp
  id: asdk_app_69431e6d26b88191b4029488aeb42f5b
  link_id: <redacted>

exposed_tool:
  namespace: codex_apps__clickup
  tool_name: _clickup_create_task_comment
  runtime_name: clickup.clickup_create_task_comment
  title: clickup_create_task_comment

description:
  Creates a comment on a specified task, with support for both
  standard and custom task IDs. Use this to add text comments,
  optionally assign the comment to a user, and choose whether
  to notify all task assignees, with optional workspace override.

input_schema:
  required:
    - task_id
    - comment_text
  optional:
    - workspace_id
    - notify_all
    - assignee

resource_uri:
  /asdk_app_69431e6d26b88191b4029488aeb42f5b/link_<redacted>/clickup_create_task_comment

</details>

<details>
<summary>Diagnostic source coverage and privacy handling</summary>

The following local diagnostic sources were inspected:

Codex session rollout JSONL files

Source of all 26 mcp_tool_call_end events.
Source of session IDs, timestamps, durations, invocation key sets, and structured error results.
Raw prompts, task identifiers, Workspace identifiers, and comment contents were not included in this report.

Codex logs_2.sqlite

Contains 6 textual matches for the exact error across 3 threads.
Targets:
codex_core::stream_events_utils: 3 DEBUG records.
codex_core::stream_events_utils: 3 INFO records.
The SQLite log retains fewer textual copies than the authoritative session event stream.

Codex Desktop package log

The current Desktop log did not contain the actual MCP error -32602 runtime result or mcp_tool_call_end records.
It contained only a prompt that referred to the earlier failure.
This may itself be a diagnostics gap: the structured session trace contains the backend error, while the Desktop log does not.

Codex Apps tool catalog

Confirms that the ClickUp comment tool is advertised.
Catalog schema version: 4.
Catalog size: 2,817,993 bytes.
Last modified: 2026-07-13T07:01:30.195Z.

ClickUp plugin manifest

Plugin version: 1.0.0.
App ID: asdk_app_69431e6d26b88191b4029488aeb42f5b.
Plugin directory last modified: 2026-07-11T02:51:14.954Z.

Post-failure control read

clickup_get_task_comments succeeded.
Returned comment count: 0.
Confirms no comment was created by the failed request.

The following values were intentionally excluded:

ClickUp Workspace ID.
ClickUp task IDs.
ClickUp connector link ID.
Comment contents.
Repository name and path.
Local Windows username.
OAuth credentials, cookies, access tokens, refresh tokens, or secret values.
Full raw session files, because they contain task content and project context.

No authentication files were opened. No OAuth or secret values were copied. No ClickUp API token was extracted. No cache files were deleted or modified during evidence collection.

</details>

Requested investigation

Please check the capability and name mapping for:

Codex-facing wrapper:
clickup.clickup_create_task_comment

Advertised title:
clickup_create_task_comment

Backend tool requested:
clickup_create_task_comment

Connector app id:
asdk_app_69431e6d26b88191b4029488aeb42f5b

In particular:

Does the current ClickUp connector backend register clickup_create_task_comment?
Does the connector adapter translate the Codex-facing wrapper to the correct canonical upstream name?
Can the Apps capability catalog be generated from the same live registry used for execution?
Can capability validation remove unavailable tools before they are injected into a thread?
Can the error include an upstream request ID and a specific missing_upstream_tool classification?
Is this the same underlying connector registration issue as the BioRender and Notion reports linked above?

View original on GitHub ↗