Stop getting interrupted for changes that don't need you.
Give your clients and teammates the Claude Code experience on your real app — no terminal, nothing to install on their side. Every change runs in a cloud sandbox and lands on a branch in your GitHub repository, merged only when you approve it.
Connect a GitHub repository and invite your first collaborator in minutes.
The ten-minute change that costs you an hour
It is never the change itself. It is the context switch, the round trip, and the line you cannot bill — or the sprint you cannot plan around it.
How it works
Four steps from a repository to a collaborator shipping their first change.
- 1
Connect a GitHub repository
Install the GitHub App, pick a repository and the base branch collaborators start from. Every change ends up in git.
- 2
Set your rules
Declare the files non-technical collaborators must never touch, what requires a review, and the environment variables your app needs to run.
- 3
Invite collaborators
They get a chat interface and the live preview of your real app. Everything in the browser. Simple as that.
- 4
Update, review and merge
A session squashes into a single commit. When a change requires review, we open a pull request and notify you.
What happens under the hood
No magic, and nothing simulated. Three things run behind every session.
One cloud sandbox per session
Built from a Dockerfile generated for your repository, it runs your dev server and a coding agent side by side. It pauses after ten minutes of inactivity and resumes on demand. Your GitHub token is injected for the clone and the push only, never written to disk.
Real branches, real commits
Each session clones your repository on its own branch and commits with the collaborator as author. Nothing is mocked: what you review is the diff that ships.
Your rules enforced every turn
After each turn of the conversation, protected files are restored from the base branch before anything is committed. A pull request is opened when the project requires one, when a flagged file was touched, or when the base branch has moved.
One honest caveat: the environment variables you declare are injected into the sandbox, so the agent running there can reach them. Use development credentials, never production ones.
Lovable, v0 and Bolt generate a brand-new app from a prompt. MakeThemCode changes the app you already ship.
Compare with Lovable in detailQuestions you are about to ask
- Do collaborators need a GitHub account?
- No. They receive an invitation link, choose a password, and work entirely from the browser. Commits are authored in their name and pushed through your GitHub App installation.
- What actually runs the code?
- Each session gets its own cloud sandbox, built from a Dockerfile generated for your repository. It runs your dev server and an opencode agent side by side.
- Which model runs the agent, and who pays for it?
- Claude Sonnet, with nothing to set up: there is no API key to bring. Token usage is measured per project and billed to its owner.
- Can a collaborator break my main branch?
- Not on their own. Every session works on a dedicated branch, protected paths are restored automatically, and merging into your base branch happens on the terms you configured.
- How is this different from Lovable or v0?
- Those build a new app from scratch, inside their own environment. MakeThemCode works on the repository you already ship: your stack, your history, your branches. What comes out is a commit you review, not an app you would have to migrate.
You are probably not the one who will use this day to day. Send them the page written for them.
Hand the keyboard over. Keep the repository.
Create an account, connect a repository, and send your first invitation.