Frequently asked questions
How to use MakeThemCode, how it works, and why it is the best vibe coding tool ;)
Using MakeThemCode
- How do I start?
- The simplest way is to ask your developer to check this out. If you have a GitHub account with access to the project, you can run the setup yourself.
- 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. You never see the code.
- Do I need to install anything?
- No. Everything happens in your browser: the chat and the running app. There is no terminal, no editor and no setup on your side.
- Can I vibe code from my phone?
- Yes. MakeThemCode works in any mobile browser, on iPhone, Android or iPad, with nothing to install. The chat and your running app are one tap apart, and a session started on your phone can be finished on your computer.
- Can I break the app?
- No. You work on your own copy until you submit, you can ask for review and your developer set what should not be changed.
- Is it the real app or a mockup?
- A copy of your real app, built from its code and running in the cloud. Your production app and its data are never touched until you submit.
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.
- Does it trigger my CI/CD?
- Yes. Changes are ordinary commits pushed to GitHub, so your checks, preview deployments and releases run as they do for any other commit.
- Which stacks are supported?
- Any web app that can run 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.
- Where do my secrets go?
- Your environment variables are stored encrypted and only given to your project's sandboxes, so the app can run as it does on your machine. The people you invite to the project could reach them through the assistant, but no one else can: that is why we recommend development credentials, as you would use locally. Access to your repository is limited too: each pull or push uses a short-lived token that only covers that repository and is never kept in it.
- How is this different from other tools like Lovable?
- MakeThemCode is built for developers and non-tech collaborators working together on the same codebase. Developers can add protection rules and get the changes as pull requests on their own repository. Lovable builds a new app, cannot start from an existing repository, and is used by solo makers most of the time.
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. A token is a small chunk of text, roughly three quarters of a word: the more code the assistant reads and writes, the more tokens a request uses.
- Who pays: me or my collaborators?
- 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 set spending limits?
- Yes. Set a monthly limit for the project and one for each member: the assistant stops when it is reached.
Start making a change.
(Yes this is word play)