working-with-task-comments

Call the posthog:exec tool with a command like "call tasks-comments-list {}" to list open comment roots, then use tasks-comments-retrieve with a root_comment_id to read full threads. Comment tools are inner tools behind exec, not top-level MCP tools.

tasks-comments-list is an inner tool routed through the posthog:exec dispatcher, not a separately registered MCP tool. Run exec with "search ^tasks-(artifacts-list|comments-(list|retrieve))$" to confirm the inner tools exist before concluding comments are unavailable.

Call tasks-artifacts-list through exec to get artifact and canvas ids, then pass the desired id as artifact_id to tasks-comments-list. This returns only the comment roots attached to that target.

No. The tasks-comments inner tools are read-only and cannot create, reply to, resolve, edit, or delete comments. They also expose no task id, and the server rejects cross-task access.

List bodies are bounded excerpts and detail responses cap total comment-body bytes. When an entry has content_truncated set to true, call tasks-comments-retrieve again with that entry's id as comment_id and its content_next_offset as content_offset until content_next_offset is null.