René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[BUG] MCP server: pull_request_read.get_review_comments omits thread node id, making resolve_review_thread unusable","articleBody":"### Preflight Checklist\n\n- [x] I have searched [existing issues](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20state%3Aopen%20label%3Abug) and this hasn't been reported yet\n- [x] This is a single bug report (please file separate reports for different bugs)\n- [x] I am using the latest version of Claude Code\n\n### What's Wrong?\n\nn Claude Code Sessions (CCR), the Anthropic-hosted GitHub MCP server at https://api.anthropic.com/v2/ccr-sessions/\u003csession\u003e/github/mcp exposes a pair of tools that don't compose:\n\nmcp__github__pull_request_read with method get_review_comments returns review threads with no id field.\nmcp__github__resolve_review_thread (and pull_request_review_write method resolve_thread) require a GraphQL thread node ID (PRRT_kwDO…) and explicitly say in their description to \"Get thread IDs from pull_request_read with method get_review_comments.\"\nResult: the /review skill can post replies after addressing comments but cannot programmatically resolve the threads. Every session in this environment leaves stale unresolved threads requiring manual UI clicks.\n\nThe actual response shape from get_review_comments for each thread:\n\n{\n  \"is_resolved\": true,\n  \"is_outdated\": true,\n  \"is_collapsed\": true,\n  \"comments\": [ { \"body\": \"...\", \"path\": \"...\", \"author\": \"...\",\n                  \"created_at\": \"...\", \"updated_at\": \"...\", \"html_url\": \"...\" } ],\n  \"total_count\": 1\n}\nNo id, no databaseId, no node identifier at the thread or comment level. So the threadId required by the resolve tools cannot be obtained or derived in-session.\n\n### What Should Happen?\n\nget_review_comments should include the GraphQL id (and ideally databaseId) on each review_threads[] entry, matching what resolve_review_thread and pull_request_review_write.resolve_thread document as their input source. Expected shape:\n\n{\n  \"id\": \"PRRT_kwDOQKV1Cs6-U6j9\",\n  \"databaseId\": 12345678,\n  \"is_resolved\": false,\n  \"is_outdated\": false,\n  \"is_collapsed\": false,\n  \"comments\": [ ... ],\n  \"total_count\": 1\n}\nWith that one field present, the existing resolve tools become usable, the /review skill's resolve-after-fix step works end-to-end, and there is no consumer-side change needed (the resolve tools already accept this exact node-ID format).\n\nSteps to reproduce\nIn any Claude Code Session scoped to a repo with a PR that has review threads, call:\nmcp__github__pull_request_read({\n  method: \"get_review_comments\",\n  owner: \"videofactsai\",\n  repo: \"portfolio-paths\",\n  pullNumber: 205,\n  perPage: 3\n})\nInspect any element of the returned review_threads[] array.\nObserve that the keys are exactly is_resolved | is_outdated | is_collapsed | comments | total_count — no thread id.\nTry to call mcp__github__resolve_review_thread — there is no value available to pass as threadId.\nVerified across perPage 3 / 5 / 100, page 1 / 2 / 3, and after an MCP server reconnect within the same session. Any PR with review threads reproduces.\n\nWorkaround\nNone in this environment. CCR sessions have no gh CLI, no GITHUB_TOKEN, and no direct GitHub API access — all confirmed in env. Other Claude environments fall back to gh api graphql to fetch the missing node IDs; that path is unavailable here. Manual resolution in the GitHub UI is the only option until fixed.\n\nEnvironment\nClaude Code: 2.1.131\nModel: Claude Opus 4.7 (claude-opus-4-7[1m]); reproduces independent of model\nSurface: Claude Code Session (CCR) on Anthropic infrastructure\nMCP server URL pattern: https://api.anthropic.com/v2/ccr-sessions/\u003csession\u003e/github/mcp\nMCP server ID: 735f0525-e70b-533b-8355-c868c8e04799\nRepo scope: videofactsai/portfolio-paths (any repo reproduces)\nPlatform: Linux 6.18.5\n\n### Error Messages/Logs\n\n```shell\n\n```\n\n### Steps to Reproduce\n\nIn any Claude Code Session scoped to a repo with a PR that has review threads, call:\nmcp__github__pull_request_read({\n  method: \"get_review_comments\",\n  owner: \"videofactsai\",\n  repo: \"portfolio-paths\",\n  pullNumber: 205,\n  perPage: 3\n})\nInspect any element of the returned review_threads[] array.\nObserve that the keys are exactly is_resolved | is_outdated | is_collapsed | comments | total_count — no thread id.\nTry to call mcp__github__resolve_review_thread — there is no value available to pass as threadId.\nVerified across perPage 3 / 5 / 100, page 1 / 2 / 3, and after an MCP server reconnect within the same session. Any PR with review threads reproduces.\n\nWorkaround\nNone in this environment. CCR sessions have no gh CLI, no GITHUB_TOKEN, and no direct GitHub API access — all confirmed in env. Other Claude environments fall back to gh api graphql to fetch the missing node IDs; that path is unavailable here. Manual resolution in the GitHub UI is the only option until fixed.\n\n### Claude Model\n\nOpus\n\n### Is this a regression?\n\nNo, this never worked\n\n### Last Working Version\n\n_No response_\n\n### Claude Code Version\n\nClaude Code 2.1.131, model Claude Opus 4.7 (claude-opus-4-7[1m])\n\n### Platform\n\nAnthropic API\n\n### Operating System\n\nmacOS\n\n### Terminal/Shell\n\nTerminal.app (macOS)\n\n### Additional Information\n\n_No response_","author":{"url":"https://github.com/bellaura","@type":"Person","name":"bellaura"},"datePublished":"2026-05-06T19:40:57.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/56791/claude-code/issues/56791"}