Incorrect user attribution in a task suggestion involving the GitHub MCP integration
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 12/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- github
- Domain
- ai, authentication
Research direction
The report does not name any file, test, or entry point, so the first step is to reproduce it: check which account the GitHub MCP tools authenticate as and how they resolve the authenticated user's comment history. Whether the cause sits in suggestion generation, session context, or the MCP server is unknown and needs a maintainer's guidance. Done would mean the origin of the misattribution is identified or a fix direction is agreed on.
Written by the indexing model from the issue text.
Description
Description
While using ChatGPT with the GitHub MCP integration, I received an automatic suggestion to review [growthbook/growthbook#7309](https://github.com/growthbook/growthbook/pull/7309), a repository I do not recognize as related to my work.
The suggestion claimed that I had already replied “Fixed.” to a review comment at 19:38 UTC. However, verification through the GitHub MCP tools showed that the comment was written by a different account.
Verified evidence
- My authenticated GitHub account:
williambelini-maker. - Actual author of “Fixed.”:
allileong, the PR author. - Comment timestamp: October 14, 2026, at 19:38:16 UTC.
- Comment: https://github.com/growthbook/growthbook/pull/7309#discussion_r4275400567
- Original review comment: https://github.com/growthbook/growthbook/pull/7309#discussion_r4274526740
The reply addressed a Cursor bot review requesting that a description be truncated to 80 characters. It was not posted by my authenticated account.
Actual behavior
The automatically suggested task presented another user's activity as my own and instructed the assistant to continue work on that PR.
The assistant began reading the repository through the GitHub MCP integration before I clarified that I did not recognize the task. No code changes or comments were submitted.
Expected behavior
- Verify account identity before attributing GitHub activity to the user.
- Explain why a repository or PR is relevant to a personalized suggestion.
- Avoid presenting another account's comments as the authenticated user's history.
Investigation requested
Please investigate why this PR was suggested to my session and why activity by allileong was attributed to williambelini-maker.
The incorrect attribution is confirmed. Its technical origin is unknown: I cannot determine whether it originated in suggestion generation, context handling, or the GitHub MCP integration. This report does not establish a data leak or cross-account access.
- Dominant language
- Go
- Stars
- 34.2k
- Forks
- 5.3k
- Avg merge
- 5d 18h
- Merged PRs (30d)
- 13
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github/github-mcp-server
-
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
github/github-mcp-server#3760 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
github/github-mcp-server#3758 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
github/github-mcp-server#3729 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
github/github-mcp-server#3722 ·
Maintainers usually reply within 2 days
-
Insiders Feedback: PR created UI doesn't link to the PRPossibly taken @genius-0963 claimed this 5 days ago. Openbug insiders user-experience
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
github/github-mcp-server#3658 ·
Maintainers usually reply within 2 days
All issues in github/github-mcp-server
Similar issues
-
ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
hexlet-basics/hexlet-basics#962 ·
Maintainers usually reply within 1 day
-
imapproxy closeForMaintenance grace timer calls clientConn.Close() before closeMaintenanceTransportPossibly taken @dejanstrbac claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
renovate-health
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Netcracker/qubership-network-latency-exporter#267 ·
Maintainers usually reply within 1 day
-
Network capture does not workPossibly taken @KSpaceer claimed this today. Openkind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
aquasecurity/tracee#5395 ·