Frequently asked questions
Everything about MakeThemCode: for the people who use it, for the developers who set it up, and about pricing.
Using MakeThemCode
- Do I need to know how to code?
- No. You describe the change in plain language and look at the result on your real app. When something is unclear, the assistant asks before touching anything.
- Do I need to install anything?
- No. Everything happens in your browser: the chat, the running app and git. There is no terminal, no editor and no setup on your side.
- Can I break the app?
- No. You work on your own copy until you submit, the files your developer protected are restored automatically, and the changes they flagged wait for their review.
- Do I need a GitHub account?
- No. You get an invitation link and work from the browser. Your changes are saved in your name through your team's GitHub connection.
- Is it the real app or a mockup?
- The real app: its code, its components and its data model, running in the cloud. What you see is what ships.
- Who sets it up?
- A developer, once: they connect the repository and choose what you are free to change. It takes about ten minutes.
For developers
- 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 our AI coding agent side by side, and pauses after ten minutes of inactivity.
- Which stacks are supported?
- Any web app that runs in a Docker container with a dev server. We work out how your app starts when you connect the repository.
- Does it work with GitLab or Bitbucket?
- Not yet. MakeThemCode connects to GitHub through a GitHub App.
- 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.
- Does it trigger my CI/CD?
- Yes. Changes are ordinary commits and pull requests pushed to GitHub, so your checks, preview deployments and releases run as they do for any other commit.
- Where do my secrets go?
- The environment variables you declare are injected into the sandbox, so the agent running there can reach them: use development credentials, never production ones. Your GitHub token is only used to clone and push, and never written to disk.
- How is this different from Lovable, v0 or Replit?
- Lovable builds a new app and cannot start from an existing repository. v0 and Replit can open one, but rely on GitHub access and GitHub's own protections. MakeThemCode is built for non-tech collaborators: no GitHub account, and the rules you set on every file are enforced after each turn.
Pricing
- Is there a free plan?
- No, but every new project starts with $1.00 of credit, enough to try your first requests before adding a card.
- What do I pay for?
- The tokens the assistant uses to read your code and write changes, at the prices listed on the pricing page. There is no subscription and no commitment.
- Who pays: me or my collaborators?
- The project. Each project has its own balance, topped up by card, and the usage of every member is deducted from it.
- What happens when the balance runs out?
- The assistant stops until someone tops the project up. Turn on automatic top-up and the saved card recharges it when it gets low.
- Can I cap spending?
- Yes. Set a monthly limit for the project and one for each member: the assistant stops when it is reached.
Make the change yourself.
Create an account, ask your developer to connect your app, and fix the first thing on your list.