STEP 01
Connect GitHub once
Add a classic personal access token in the admin. It is encrypted and stored on the server. Nobody you invite ever sees it.
GitHub access, safely delegated
They ask for the change. Let them make it.
Give someone access to exactly the repositories they need, and let them make the edit by asking ChatGPT or Claude. Your GitHub token never leaves the server, and everything they change arrives as an ordinary commit.
Your token stays server-side
Access granted per repository
Every change is a commit
What Aisha asked for
Change the pricing headline to “Simple, honest pricing” and drop the old launch banner.
Files changed
src/pages/pricing.tsx
Edited
content/hero.md
Edited
components/Banner.tsx
Removed
package.json
Untouched
In progress
Deploying — GitHub Action running
run #42
3 ways in
the admin panel, Claude Desktop, or your own custom GPT
Per repo
each person is granted only the repositories you choose
Encrypted
your token is stored server-side and never shown to anyone
Free
while the tool is in beta
How it works
Three steps to stop being the bottleneck.
STEP 02
Grant access per repository
Decide who reaches what. One person gets two repositories, another gets a different three. Change or revoke it at any time.
STEP 03
They edit by asking
From the admin panel, Claude Desktop, or a custom GPT. The change is committed, and your existing GitHub Action rebuilds the site.
Why this is different
Hand over the work, not the keys.
The usual choices are poor ones: add them as a GitHub collaborator and they get far more access than the job needs, or keep making every small edit yourself. This sits in between — one person, the repositories you named, nothing else. Private repositories included.
Private repositories work here on any GitHub plan. Publishing one as a GitHub Pages site needs Pro or Team — but Azure Static Web Apps, Cloudflare Pages, Netlify and Vercel all build from private repositories on their free tiers.
Done
Aisha — company-site
granted
Done
Sam — docs, changelog
granted
In progress
Priya — landing-page
granted
Not started
Everything else
no access
What you get
Built for the person who keeps getting asked.
Edits by conversation
They describe the change in plain words. The assistant finds the file, makes the edit and commits it.
Your token, never shared
Stored encrypted on the server. Collaborators use the tool; they never hold your credentials.
Access, repository by repository
Grant one person two repositories and someone else a different three. Revoke any of it in a click.
Everything is a commit
Each change lands in your history with a message. Read it, revert it, or branch from it as usual.
Your deploy already works
A commit triggers the GitHub Action you already have. GitHub Pages or Azure Static Web Apps, nothing new to configure.
From anywhere
A phone and a chat window is enough. No laptop, no local checkout, no build tools.
Starting a new project
Scaffold a repository, then talk to it.
Stop being the bottleneck.
Connect a repository and invite the person who keeps asking you for changes. Free while the tool is in beta.