ClickUp connector read calls fail after disconnect and reauthentication

Environment

• Codex Desktop 26.727.40816 (build 6067)
• macOS 27.0 (build 26A5406e)
• Bundled ClickUp connector/plugin
• ClickUp account is the workspace owner

Reproduction

1. Delete the previously connected ClickUp user.
2. Uninstall the ClickUp plugin.
3. Disconnect the bundled ClickUp connector separately.
4. Sign in to ClickUp as the workspace owner.
5. Reinstall and reconnect the plugin and connector.
6. From a new verification task, run read-only workspace-members, hierarchy, and search calls.

Actual behaviour

The ClickUp tools are visible, but authenticated-principal identity, workspace access, and successful read acceptance cannot be established:

• No current-user or whoami tool is exposed.
• Explicit and implicit get_workspace_members calls return:

  Resource not found
  

• get_workspace_hierarchy returns the same error when the optional max_depth field is omitted:

  Resource not found
  

• A harmless workspace search returns:

  Must join workspace to have access
  

The failures persist after uninstalling, disconnecting, reauthenticating, reinstalling, reconnecting, and testing in a new/current task.

No ClickUp writes were made. No personal email, workspace ID, names, task content, tokens, logs, or session transcripts are included.

Expected behaviour

After reconnecting as a workspace owner, read-only workspace members, hierarchy, and search calls should succeed. The connector should also expose a safe way to inspect the authenticated principal, so tool visibility, authentication, workspace access, and read acceptance can be distinguished.

Duplicate check

Exact-error searches in openai/codex found no matching open ClickUp report for either error.

Start by reproducing the reconnect sequence, then run the workspace-members, workspace-hierarchy, and workspace-search calls described in the issue, including hierarchy without max_depth. Trace the bundled ClickUp connector's authentication and workspace-access entry points. Done means a reauthenticated workspace owner can complete those read-only calls and safely verify the authenticated principal.