{"slug": "why-github-access-isn-t-the-same-as-local-repository-access", "title": "Why GitHub Access Isn't the Same as Local Repository Access", "summary": "A developer known as Lukie-81 has built RepoRelay, an open-source tool that gives AI coding assistants like ChatGPT access to a local repository without exposing the entire machine. The tool uses a secure MCP tunnel to expose only an explicitly approved local repository, with a deliberately small tool surface that blocks sensitive files. The project aims to align AI permissions with the task at hand, distinguishing between read-only code review and broader implementation access.", "body_md": "AI coding tools increasingly integrate directly with GitHub.\n\nRepoRelay:Give ChatGPT access to your local repo — not your machine.\n\nGitHub:[https://github.com/Lukie-81/RepoRelay]\n\nFor many workflows, that's enough.\n\nBut there's an important difference:\n\nThe code on GitHub isn't always the code on your computer.\n\nImagine you're halfway through implementing a feature.\n\nOn GitHub, you might have:\n\n`main`\n\nbranchBut locally, you might have:\n\nNow suppose you want to ask an AI:\n\nDoes this implementation make sense before I commit it?\n\nA GitHub integration may not be able to see the code you actually want reviewed.\n\nYou could create a temporary branch and push everything:\n\n**Edit → Commit → Push → Review → Fix → Commit again**\n\nThat works.\n\nBut for quick code review, it adds friction to something that should be simple.\n\nAnother solution is giving an AI coding agent direct filesystem or shell access.\n\nThat solves the visibility problem — but it creates another one.\n\nIf the task is simply:\n\nRead these files and review my code.\n\nWhy does the AI need permission to:\n\nFor a reviewer, the useful capabilities are much narrower:\n\nThis suggests a simple principle:\n\n## The tool surface should match the task surface.\n\nA **code reviewer** and an **implementation agent** don't necessarily need the same permissions.\n\nThis is the idea behind an open-source project I've been building called **RepoRelay**.\n\nInstead of exposing the entire computer, RepoRelay exposes **one explicitly approved local repository** through MCP.\n\nThe architecture is roughly:\n\n**ChatGPT Web → Secure MCP Tunnel → RepoRelay → Approved Local Repository**\n\nBy default, RepoRelay provides a deliberately small tool surface for inspecting that repository.\n\nIt does **not** provide:\n\nSensitive files are also blocked instead of being blindly exposed to the model.\n\nThe objective isn't to make an AI agent less capable.\n\nIt's to give it **only the capabilities required for the job**.\n\nA GitHub integration essentially answers:\n\nWhat code exists in this remote repository?\n\nLocal repository access answers:\n\nWhat does my project look like right now?\n\nThat distinction matters.\n\nA lot of software development happens in the space between **editing code** and **committing code**.\n\nAnd that unfinished working tree is often exactly what you want reviewed.\n\nI think AI development tools will increasingly need to distinguish between different levels of access.\n\nFor example:\n\nThose permissions shouldn't automatically be treated as equivalent.\n\nIf an AI is reviewing code, **bounded read access may be enough**.\n\nIf it's implementing an entire feature autonomously, broader permissions may make sense.\n\nThe important part is making that decision deliberately.\n\nAs coding agents become more capable, the question shouldn't always be:\n\nHow much access can we give the AI?\n\nA better question is:\n\nWhat's the minimum access required for this task?\n\nThat's the trade-off I'm exploring with **RepoRelay**: giving an AI enough context to be genuinely useful without automatically giving it everything the machine can do.\n\nRepoRelay is open source, so if you're interested in the idea — or want to criticize the security model — the implementation is available here:\n\n**GitHub:** [Lukie-81/RepoRelay](https://github.com/Lukie-81/RepoRelay)\n\nI'd be interested in hearing how others think about permission boundaries for AI coding tools.", "url": "https://wpnews.pro/news/why-github-access-isn-t-the-same-as-local-repository-access", "canonical_source": "https://dev.to/lukie81/why-github-access-isnt-the-same-as-local-repository-access-o76", "published_at": "2026-08-20 03:28:52+00:00", "updated_at": "2026-08-20 04:16:39.304582+00:00", "lang": "en", "topics": ["ai-tools", "developer-tools", "ai-agents", "ai-safety"], "entities": ["RepoRelay", "ChatGPT", "GitHub", "Lukie-81"], "alternates": {"html": "https://wpnews.pro/news/why-github-access-isn-t-the-same-as-local-repository-access", "markdown": "https://wpnews.pro/news/why-github-access-isn-t-the-same-as-local-repository-access.md", "text": "https://wpnews.pro/news/why-github-access-isn-t-the-same-as-local-repository-access.txt", "jsonld": "https://wpnews.pro/news/why-github-access-isn-t-the-same-as-local-repository-access.jsonld"}}