# Cursor cloud agent access to github issues

**URL:** <https://forum.cursor.com/t/cursor-cloud-agent-access-to-github-issues/159180>\
**Category:** Help\
**Tags:** github, cloud-agents\
**Created:** [April 27, 2026, 9:08pm UTC](https://forum.cursor.com/t/cursor-cloud-agent-access-to-github-issues/159180 "2026-04-27T21:08:58Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lincoln\_Cannon](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/lincoln_cannon/32/106948_2.png) [@Lincoln\_Cannon](https://forum.cursor.com/u/Lincoln_Cannon)\
**Post date:** [April 27, 2026, 9:08pm UTC](https://forum.cursor.com/t/cursor-cloud-agent-access-to-github-issues/159180/1 "2026-04-27T21:08:58Z")

</div>

Hi Cursor. Should Cursor cloud agents be able to access and read GitHub issues?

* * *

I’ve reinstalled the Cursor GitHub app multiple times, and observed that it claims to be granting read/write access to issues as shown here:

Cursor  
Installed 52 minutes ago Developed by cursor [https://cursor.com](https://cursor.com)  
Connect Cursor to GitHub to allow agents to do work for you in the background.

Permissions  
Read access to actions, commit statuses, deployments, members, metadata, packages, and pages  
Read and write access to checks, code, discussions, issues, pull requests, and workflows

* * *

My Cursor cloud agents keep telling me something like this:

I’m not currently able to read GitHub issues for this repo.

Testing

❌ pwd && git remote -v && gh issue list --limit 5 — GitHub returned GraphQL: Resource not accessible by integration (repository.issues), so the current token lacks issues read permission.

---

<div class="post-metadata">

**Author:** ![mohitjain](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mohitjain/32/100229_2.png) [@mohitjain](https://forum.cursor.com/u/mohitjain)\
**Post date:** [April 28, 2026, 12:31pm UTC](https://forum.cursor.com/t/cursor-cloud-agent-access-to-github-issues/159180/6 "2026-04-28T12:31:58Z")

</div>

Yes, cloud agents should be able to access GitHub issues, but there’s a known gap right now. The GitHub App requests broad permissions at the app level (which is what you see in the installation settings), but the token the agent actually uses in its sandbox is scoped more narrowly and currently doesn’t include `issues` access. That’s why you see the “Resource not accessible by integration” error.

Two workarounds while this is being addressed:

1. Paste issue content directly into the agent prompt — copy the title, description, and key comments rather than asking it to fetch by number.

2. Create a Personal Access Token at [https://github.com/settings/personal-access-tokens](https://github.com/settings/personal-access-tokens) with the needed scopes, and add it as an environment variable `GH_TOKEN=ghp_...` in your cloud environment settings. The `gh` CLI will use that token instead of the built-in one. [Another user confirmed this works](https://forum.cursor.com/t/cloud-agent-cannot-read-github-issues-graphql-resource-not-accessible-by-integration-repository-issues/156790).

Let me know if either of those helps!

---

<div class="post-metadata">

**Author:** ![Lincoln\_Cannon](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/lincoln_cannon/32/106948_2.png) [@Lincoln\_Cannon](https://forum.cursor.com/u/Lincoln_Cannon)\
**Post date:** [April 28, 2026, 1:13pm UTC](https://forum.cursor.com/t/cursor-cloud-agent-access-to-github-issues/159180/8 "2026-04-28T13:13:35Z")

</div>

Thanks for confirming!

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [April 30, 2026, 1:14pm UTC](https://forum.cursor.com/t/cursor-cloud-agent-access-to-github-issues/159180/9 "2026-04-30T13:14:01Z")

</div>

Closed on April 30, 2026, 1:14pm UTC

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.