1. Connect GitHub
In RepoMesh Desktop, open Repositories → GitHub Remote → Connect GitHub. GitHub opens a browser confirmation using Device Flow. You approve the one-time code.
RepoMesh Desktop 0.0.51 · GitHub Remote
RepoMesh gives you a reusable, local repository context layer for the agents you already use. With GitHub Remote, you can index an authorized public or private repository directly from GitHub, then find relevant code, symbols and dependencies. No separate GitHub App to create and no personal access token to paste.
RepoMesh uses your GitHub account and asks only for read-only repository access.
In RepoMesh Desktop, open Repositories → GitHub Remote → Connect GitHub. GitHub opens a browser confirmation using Device Flow. You approve the one-time code.
Click Install App. Choose a personal account or organization and authorize the repositories RepoMesh can index. If organization approval is required, ask an administrator to approve access.
Click Refresh repositories, pick an authorized repository and branch, then Add & Index. Open Explore Context to ask where a feature is implemented.
RepoMesh remains the repository context layer—not a coding agent that writes or changes your code.
The GitHub App requests Contents and Metadata read-only permissions. RepoMesh doesn't need write access to your repositories or their secrets.
After indexing, the bounded, redacted snapshot is stored on your computer. You can explore it without keeping a network session open.
Search paths, symbols and related code through Explore Context or the compatible MCP github_context tool when your agent uses the same RepoMesh home.
No. RepoMesh Desktop includes the public application identifier. Sign in with GitHub and choose which repositories to authorize.
Yes, if you have access and install the RepoMesh GitHub App on the account or organization that owns them. The app needs read-only repository access.
No. RepoMesh reads a selected commit, applies source exclusions and redaction, and stores a local indexing snapshot. It does not create a Git working copy.
Compatible MCP clients can use github_context to read a snapshot when they share the same RepoMesh home. Automatically fetching new private commits from an MCP agent via github_index still needs its own GITHUB_TOKEN or GH_TOKEN; the Desktop login isn't shared with agents.
No. The indexing and context engine run locally. GitHub is the source for the repository content, and RepoMesh does not require an AI API key or paid cloud model.