Claude Code alternatives
If Claude Code is not the right fit, these solve similar problems.
Cursor
Editor built around AI, with codebase-wide context rather than single-file autocomplete.
The strongest argument for switching editors rather than adding a plugin. Because it indexes the whole repository, its suggestions follow conventions already in your code instead of inventing new ones, and multi-file edits actually hold together. The cost is real: you are moving your daily environment, and everything you have customised comes with you only if it exists as a VS Code extension.
from $20/mo
GitHub Copilot
The most widely deployed coding assistant, available in most major editors.
The safe institutional choice rather than the most capable one. It lives inside the editor you already use, it is the tool corporate security teams have most often already approved, and it does the everyday job — finishing the line, filling in the obvious — without asking you to change anything about how you work. Where it is behind is agentic, repository-wide work, which is exactly where the newer entrants concentrate.
from $10/mo
Devin Desktop (Windsurf)
The renamed Windsurf editor, now combining a full IDE with a command center for coding agents.
Positioned between an editor and an agent: you get a normal editing experience plus a mode that will go away and carry out a multi-step change. That combination is genuinely useful, and it is also the category's most crowded position — the practical question is not whether it works but whether it works better than the tool you already have open.
from $20/mo
ChatGPT
The most widely used assistant, with image generation and a large plugin ecosystem.
The default entry point to this whole category, and still the broadest one — it does text, images, code, data analysis and voice in one place, which is why most people never need a second tool. Being the default is also its weakness in specific work: for a task you do daily, a focused competitor is usually better at that one thing. Judge it on breadth, not on any single capability.
from $20/mo
Claude
Assistant known for long-context reasoning and writing that needs less editing.
Strongest on long documents and on writing that has to sound like a person wrote it. The large context window is the practical differentiator — you can put a whole contract, a long transcript or several files in at once and ask about them together, which changes what kinds of work are possible rather than just making them faster. Less of an all-in-one than its main competitor.
from $20/mo
Gemini
Google's assistant, tightly integrated with Search, Gmail and Workspace.
Its real argument is not the model in isolation but where it sits: inside Gmail, Docs and the rest of Workspace, with access to what is already there. If your working day happens in those tools, that proximity is worth more than a few benchmark points. If it does not, the case is much weaker and comes down to ordinary model comparison.
from $20/mo
Codex CLI
OpenAI's open-source terminal coding agent, rewritten in Rust.
The obvious choice if your team already pays for ChatGPT, because the agent comes with the plan rather than as another line item. The client being open source matters more than it sounds: you can read what it sends and pin a version. What you are buying is the model behind it, not the tool, and that is worth being clear about — switching away from OpenAI means switching tools too.
from $20/mo
Claude CoWork
Claude working on your files in the background instead of waiting for prompts.
Worth trying if you already pay for Claude, since it costs nothing extra — and that is genuinely the strongest thing about it. The interesting shift is that work happens against files rather than in a chat log, which suits recurring document tasks better than conversation does. The caution is the same one that applies to any tool granted folder access: scope the folders narrowly and check the output, because background work is by definition work you were not watching.
from $20/mo
Gemini CLI
Google's open-source terminal agent, with the most usable free tier of the group.
The cheapest way to find out whether a terminal agent fits how you work, because the free tier is large enough for real tasks rather than a demo. Treat that as its main role: an evaluation path and a second opinion, rather than the tool you standardise a team on. Free quotas at this size have historically been the first thing to change, so do not build a workflow that breaks when it does.
Free tier available
opencode
Open-source terminal coding agent that runs on whichever model you point it at.
The right default when vendor independence is an actual requirement rather than a preference — you can move to a different model without changing how you work. The cost of that freedom is that nobody has tuned the prompts for the model you chose, so quality varies more between setups than it does with a first-party tool. Budget some time for configuration you would not spend elsewhere.
Free