Launching today

gitroots
Path-level GitHub access for developers and AI agents
20 followers
Path-level GitHub access for developers and AI agents
20 followers
gitroots is a governance layer for GitHub. Give each developer and AI agent access to only the paths they need, route their changes through approvals, and keep a searchable audit trail. Widen access to your code without handing over the whole repository.






Free Options
Launch Team

Render Sandboxes: a computer for every agentGive every agent its own machine. Starts in under a second
Promoted
Hi Product Hunt, I'm Shawki from gitroots.
We started gitroots while working with Odoo development teams that rely on contractors and outside partners. The same problem kept coming up: to let someone work on one part of a project, you ended up giving them far more of the repository than the job needed. AI coding agents have made the same problem bigger.
gitroots sits on top of GitHub and lets you set the boundary per developer, team or agent:
Path-level access: a collaborator gets only the paths they need, and the rest of the repository stays with your Git provider
Approval workflows: changes come back as requests that you approve from the web, the mobile app or the CLI
Audit history: who did what, in which repository, and when, searchable and exportable
AI agents: Claude Code, Codex and other agents go through the same checks and approvals as people
It works with GitHub today. The Starter plan is free with no card, and paid plans start at $19 a month.
I'd like to hear how your team handles contractor and agent access now, and where gitroots falls short for you.
Secure it to the root, scale with confidence.
The case I keep running into with agents is the shared file. Today an agent of mine added two pages in its own folder, and the job wasn't done until it regenerated one index file that every other page also lives in. With path rules that is either a block or a hole. Do you treat generated files like that as their own kind, or does the change go through the approval route like any other path outside the boundary?
@heinrich_neb Good example, Heinrich. Path rules apply to generated files too. If the shared index is outside the agent’s allowed paths, the index update needs approval. The agent can still work on the two pages within its folder, and a reviewer can check the index diff before approving it.
In your workflow, would you want to approve the page changes and the regenerated index together in one request?