Many times in various projects I needed context from a different github repo other than I am currently working on.
This includes for example:
A repo with an API that doesnt have docs.
A repo with an SDK.
A repo with a feature that I want to recreate in the current project.
Currently I need to open github copilot on github, where i can attach a github repo as context, source of information, ask a question, and then copy the response to cursor. Other option is to clone the repo, open it in cursor, ask it to create a documentation in .md format and then copy the .md file to the project we want the context in.
If I could reference a github repo (even private one) right in cursor’s chat, that would me much more convinient.
Adding my +1. The workaround we use right now is exposing a github PAT or fine-grained read token to remote cursor background agent’s environment secrets that give it access to those private repos and simply tell the agent to use the gh CLI to clone those private repos using the access token. Use at your own risk, because quite often background agents can loop-out and vanish when having to due too much over the terminal or where situations exist a terminal call could timeout.
This is a huge pain for me as well - we have packages we maintain in private repos which we want to use but run into an LLM context block with not being able to easily whitelist them to review that repo’s content. Agents are easily able to clone the private package into the current project but that’s definitely something we don’t want (since clones are essentially forks of the source and will go out of sync/we don’t get the benefits of managing dependencies in package.json). Anyone have a better solution for this yet?