AI coding assistants for solo developers

A solo developer can now ask an editor to write the function, or ask a browser to scaffold the app. Those are different risks. This shortlist separates assistants that sit in a codebase you already have from builders that start something new. There is no score and no “fastest model” claim. Last reviewed October 2026.

In the editor you already trust

GitHub Copilot suggests code, explains a selection, and can work through a change in chat. A free plan and paid plans exist. It fits if your work is already on GitHub and you want help inside the editor you use. Suggestions can be insecure or simply wrong. The habit that matters is reading the diff.

Cursor is an editor built around those edits. It can change several files from one prompt and answer questions about the repo. A free tier and paid plans are published. It is not a skin on Copilot. If you are deciding between them, use the Copilot vs Cursor page and a real branch, not a homepage demo.

Amazon Q Developer is AWS’s assistant for writing and changing code, with a free tier and paid plans. It is the one to try when the system you are building is already on AWS and you want the assistant in that context. It does not replace reading IAM changes carefully. Generated infrastructure is still infrastructure.

In the browser, for a first version

Replit lets you write, run, and host from the browser, with an agent that can build from a prompt. It is good for a prototype and a bad place for production secrets. Check compute limits before you leave a client demo running overnight.

v0 is Vercel’s assistant for generating a web UI and, increasingly, a fuller app you then edit. Use it when the job is a web interface and you are willing to clean up the result. A free plan exists. Generated markup still needs an accessibility pass: labels, contrast, keyboard focus.

Bolt builds sites and prototypes from a brief in the browser, with a free plan and paid plans. Treat the output as a starting repo. Look at dependencies, environment variables, and anything that talks to a third party before you point a domain at it.

Rules that are cheaper than another subscription

• One assistant in the editor, not three.
• A branch for generated work. Never a direct commit to the branch customers use.
• No secrets, customer data, or private keys in the prompt.
• Tests you already have must pass. If you have no tests, read the diff slowly instead of pretending the tool tested it.
• If you cannot explain the change, you cannot ship it.

The longer version of those rules is how to use AI coding tools carefully.

What to ignore in the sales page

Ignore claims about a percent faster or a model leaderboard. Your codebase is not the benchmark. Time-box a week. If you are not keeping the tool open on the fourth day, cancel it while the billing period is still honest.