Cursor error
Cursor: Agent can't access repository
Agent can't access repositoryStatus: WorkaroundLast verified 3 documented fixes1 source
What it means
Cloud Agents or Bugbot cannot reach a GitHub repository through the Cursor GitHub app (documented troubleshooting symptom).
Causes
- The Cursor GitHub app is not installed with access to the repository.
- Repository permissions for private repos.
- GitHub account permissions.
How to fix it
- Fix 1.
Install the GitHub app with repository access, check repository permissions for private repos, and verify your GitHub account permissions.
- Fix 2.
For "Permission denied for pull requests": grant the app write access to pull requests, check branch protection rules, and reinstall if the app installation expired.
- Fix 3.
If the app is not visible in GitHub settings, check whether it is installed at organization level, reinstall from github.com/apps/cursor, or contact support if the installation is corrupted.
More Cursor errors
All 18 Cursor errorsAgent Execution Timed OutStatus: WorkaroundTimeout waiting for EverythingProviderStatus: Workaround<filename> is too large (4MB limit)Status: By designCursor is damagedStatus: Workaroundsuspicious activityStatus: Workaroundxcrun: error: unable to find utility "mcpbridge"Status: Workaroundmissing tabIdentifierStatus: WorkaroundPrivate worker limit exceededStatus: By design
Related reading
- Do Your Agent Hooks Fail Open? Claude Code vs Codex vs Cursor vs Gemini CLIA guard hook that crashes, times out or points at a missing script lets the tool call through by default in Claude Code. v2.1.295 adds onFailure: block. Here is what each coding agent does when your policy hook breaks, with real test runs.
- How to Keep API Keys Away From Your AI Coding Agent: Claude Code vs Codex vs Cursor vs Gemini CLIA deny rule on .env stops cat but not a Python one-liner. Here are the three layers that actually keep secrets out of a coding agent's context - file rules, environment scrubbing and credential masking - and what Claude Code, Codex, Cursor and Gemini CLI give you for each, with real test runs.
- Cursor Removes Dollar Costs From Usage Page: Tokens OnlyCursor removed dollar costs from its Usage page on July 31: self-serve plans see tokens only and the dashboard API zeroes cost fields, history included.
- AI Coding Agent Security Models Compared 2026: Permissions, Sandboxing, and Threat Models for Every Major ToolAI coding agent security models compared: how Claude Code, Cursor, Codex, Copilot, Aider and Windsurf handle permissions, sandboxing and prompt injection.
- HalluSquatting Makes AI Coding Agents a Supply-Chain ProblemHalluSquatting uses hallucinated repo and skill names to deliver promptware to AI coding agents. How the attack works and the harness controls that stop it.
- Securing AI Coding Agents: A Practical Threat Model for 2026Securing AI coding agents: a practical threat model for prompt injection, sandbox escapes, and hallucinated dependencies, with defenses ranked by effort.
FAQ
What does "Agent can't access repository" mean in Cursor?
Cloud Agents or Bugbot cannot reach a GitHub repository through the Cursor GitHub app (documented troubleshooting symptom).
How do I fix "Agent can't access repository"?
There are 3 documented fixes. Start with the first: Install the GitHub app with repository access, check repository permissions for private repos, and verify your GitHub account permissions.
Is this Cursor error fixed?
Status: Workaround. No release removes the cause. The documented fixes work around it.
Sources
Last verified against 1 source: official docs, maintainer replies and release notes.
Newsletter
Fixes for the tools you use, weekly
One email per week. New coding agent releases, what broke, and how developers are working around it.