LatchLoop’s GitHub integration lets the app read your code, open pull-requests (PRs), and keep tasks up-to-date as your work is merged or deployed.
Below is an overview of what happens at every step, the controls you have, and a few FAQs.
Whenever LatchLoop asks for a repository (for example while creating a project or enriching a task):
main
) and optionally list folders to ignorenode_modules,.git,dist
).What happens next
• LatchLoop downloads a lightweight file-tree (names only, not file contents) and saves it in Supabase.
• That tree is used by the AI to understand your project’s structure when answering questions or generating code.
• If you link the repo to a task, a reference to the same file-tree is stored with the task.
When the AI needs actual code (not just the file list) it asks the GitHub API for the file’s content. Only the file requested is fetched, never the entire repo.
• Each “Build” or “Apply Patch” action creates one branch per task (if it doesn’t already exist).
• Branch names include the task’s short ID so they’re unique and easy to find, e.g.
latchloop/feat-LL9conKjz99-my-feature
.
• The AI’s changes are committed to that branch.
When the AI has pushed at least one commit and there is no open PR yet, LatchLoop will:
When a PR opened by LatchLoop is merged or closed, GitHub sends a webhook that:
If your CI/CD pipeline reports a deployment status (e.g. Vercel, Netlify, GitHub Actions), LatchLoop will store a deployment message in the task’s activity feed – useful for quick access to preview links.
Tokens refresh automatically. If you ever see a “token expired” message, just click “Reconnect GitHub App” in Settings – no code or PRs are lost.
Settings → GitHub → Disconnect instantly stops LatchLoop from making new API calls. The GitHub App remains installed, but unused.
Q: Does LatchLoop ever push directly to main
?
A: Never. All changes go to a task-specific branch and must be merged via a PR.
Q: Can the AI see private repositories?
A: Yes – but only the repos you granted the GitHub App permission for.
Q: What permissions does the GitHub App request?
A: Contents: Read & write
, Pull requests: Read & write
, Deployments: Read
. No access to Issues, Wikis, or Actions secrets.
Q: How large a repository can I connect?
A: There is no hard size limit, but extremely large repos (50k+ files) may take longer to fetch the initial file-tree.
Q: Can I switch the repository linked to a task?
A: Yes. Open the “Connect repository” dialog again, pick a different repo, and LatchLoop will replace the link.
If anything in this guide isn’t clear or you hit a snag:
Happy coding!