Top chip manufacturer TSMC is ready to invest $1 billion in Anthropic and OpenAI. That would give the Taiwanese chipmaker direct stakes in leading AI developers, even as its own contract chipmaking business has profited enormously from the AI data center buildout.
The chipmaker’s board approved plans to invest up to $500 million in OpenAI preferred stock reserved for large investors and another $500 million to purchase Anthropic common shares at the latter’s expected IPO price, according to Reuters. Such an investment may give markets “a shot of confidence as the artificial-intelligence trade shows signs of strain,” The Wall Street Journal reported.
But analysts also warned that such circular financing among investors, suppliers, and customers has made it difficult to evaluate real market demand for AI-related hardware and services, according to the Journal.
Amazon is betting that many Ring customers will also want an AI-powered security drone and robot patrolling their homes or offices. But the company’s upcoming Ring Robotic products are also certain to intensify privacy concerns previously raised around a prior Amazon attempt to popularize a flying security camera.
The Ring Rover Cam and Ring Drone Cam are expected to reach customers starting at the end of 2026 and in early 2027, respectively, according to an Amazon announcement posted on November 10. Amazon describes the devices as relying on an AI Pilot system that uses each device’s cameras along with “specialized vision models, on-device sensors and cloud processing” to plan patrol routes while autonomously navigating around obstacles such as furniture.
Both devices also use that AI Pilot system to digitally map the floor plan of the customer’s home or business. This setup process occurs after the customer carries the Ring drone through their indoor spaces or allows the Ring Rover to do some autonomous exploration.
I’m Kirsty, an Engineering Manager at Human Made, where I look after a team of engineers working on projects for enterprise clients.
There have been a lot of conversations about AI recently. A lot of them are understandably focused on technical skills, productivity and making sure we still own our output.
I’ve noticed that when AI comes up in conversations with engineers, the discussion often gravitates towards technical solutions: writing skills, generating code, automating tasks, building tools and making things faster.
Those things are interesting, but they’re not where I’ve personally found the biggest benefit.
I recently read a LeadDev article called AI made me a better engineering leader, which made me think about whether I was measuring the right things. It also made a good point about using AI to get imperfect thinking onto the page, rather than waiting until an idea is fully formed.
That connected with a recent internal discussion at Human Made about readability and our use of AI, particularly the importance of editing AI-generated content and thinking about the audience rather than just accepting whatever it produces.
Both got me thinking about my own use of AI.
I haven’t used AI to vibe-code a revolutionary new tool, and I’m certainly not 1000% more productive. I am still mulling over building a dashboard for my team, though 😉
What I do think is that AI has made me a better Engineering Manager.
Not because it makes decisions for me, or because it has somehow removed the thinking from my job. It has removed some of the bad friction around doing the job.
It’s made it easier for me to get thoughts out of my head, turn conversations into useful documentation, make sense of large amounts of information and communicate things that I probably wouldn’t have got around to communicating before.
TL;DR
AI hasn’t removed the thinking from my job. It’s removed some of the friction around doing it well.
I use it to communicate more clearly, turn conversations into documentation, analyse information, and challenge my own thinking.
I still own the thinking, the decisions and the final output.
There are plenty of ways I use AI, but I’ll focus on three examples where I’ve found the difference particularly noticeable:
Writing – Getting ideas out of my head and into something I can actually share
Documentation – Turning conversations and existing information into something the team can use
Performance reviews – Using AI to help me see the bigger picture across a whole review period
There are plenty of other examples I could give, but these are three where I’ve found the difference particularly noticeable. If you’re mainly interested in the practical examples, feel free to skip straight to them.
The tools I use
I use a few different tools, and I’ve found they each have slightly different strengths.
ChatGPT is the one I tend to reach for when I’m writing. I’ve found the output generally fits my own writing style better, which means I spend less time fighting with the tone of voice and more time actually editing the content. It’s the tool I use most for internal blog posts and generally turning my messy thoughts into something readable.
Claude is particularly useful when I need to work across multiple sources, pull together a lot of information, create technical documentation or build a framework for analysing something. It’s also the tool I tend to use for things like performance reviews, where I’m asking it to find themes across a large amount of information rather than produce something I’m going to publish directly.
Granola sits slightly differently. I use it to capture conversations and meetings, which gives me much better source material to work from afterwards. The important bit for me is that, while I will publish meeting summaries – edited for accuracy of course – I generally go back to the original transcript, rather than relying on the AI-generated meeting summary for bigger tasks.
I’m sure other people have very different experiences with these tools, and I suspect a lot of this comes down to how you prompt them and what you’re asking them to do. These are just the combinations that I’ve found work well for me.
1. Writing: things I actually want to share
One of the biggest changes for me has been writing posts for our internal blog.
As an engineer, I used to love writing documentation. If you’ve ever had me code review something you’d written, you’ll probably remember just how many comments I would leave trying to make things easier to follow and remove assumptions.
Writing things for the wider company was different.
I would agonise over the wording, structure and tone, and whether I’d explained something properly. I wanted things to be perfect.
The inevitable result was that writing took forever, and a lot of things never got published at all.
AI has changed that.
I now start in my markdown notepad, Bear, writing down all my thoughts, arguments, examples and things I think are important. I don’t worry about structure or making it readable. I just get the thinking out of my head.
I then give that to ChatGPT and ask it to turn it into a draft, usually with some guidance about the audience, structure and what I want people to take away.
That’s not normally the finished piece. I’ll edit it myself, changing anything I disagree with, adding what’s missing and removing what’s unnecessary. Then I’ll give it back to ChatGPT to look for repetition, improve awkward sentences or flag anything that doesn’t sound like me.
The important distinction is that the ideas, opinions and decisions are mine. AI is helping me get them into a form other people can actually read.
And I think the results speak for themselves.
Since around July 2025, I’ve written more internal blog posts than I did in all my previous years as an engineer. These aren’t AI-generated thoughts; they’re things I wanted to say but previously struggled to find the time and headspace to communicate.
They’ve covered everything from introducing new tech lead handover documentation and getting better at team communication, to onboarding freelancers into an existing engineering organisation and what we learned from growing the team.
What works for me
Get my actual thoughts down before worrying about the prose.
Tell the AI who the audience is and what I want them to take away.
Edit the output myself, including checking facts and anything important.
Use AI again to refine the final version, but make sure it still sounds like me.
The things I try to avoid are pretty simple: letting AI decide what I think, publishing something just because it sounds polished, or using “AI can write it for me” as an excuse not to think about what I actually want to say.
2. Documentation: turning conversations into something useful
The same approach has been incredibly useful for documentation.
When we onboarded five freelancers into my team, for example, we realised our onboarding documentation needed some serious improvement. As a result, we now have a much more robust team wiki that covers onboarding, our approach to project visibility, communication and more.
More recently, one of our engineers had ended up with a huge amount of technical knowledge about a new client project. We had an audit to refer to, but much of the migration work had been done by them and we didn’t yet have much project documentation. Then, unexpectedly, they needed to step away for a few months.
This could have been a serious problem, so I got them on a call and we talked through everything that someone taking over the project would need to know. That conversation was recorded in Granola.
I took the original transcript, not the AI-generated summary, and used Claude to help turn that conversation into a structure for useful project documentation. I then reviewed it, added any information I could from notes they had left, asked Claude to pull in anything relevant from the GitHub repository and the original audit, and then used ChatGPT to make some of the language easier to read without removing the technical detail.
That gave the team a useful starting point much faster than trying to write everything from scratch.
It wasn’t perfect, and that’s important.
I’m not the engineer working on that project, so I couldn’t personally verify every technical detail. I asked engineers in the team to review it, and the expectation is that the documentation continues to evolve as people use it.
AI got us from “all of this information is in one person’s head” to “we have something we can work with” very quickly.
I’ve used similar approaches elsewhere. Conversations about handling support requests on small retainers became a documented support process for one client, which has since evolved into a broader team approach and client-facing documentation. In cases like this, one conversation can end up producing useful documentation for more than one project.
What works for me
Start with the original source material wherever possible.
Give AI enough context to understand what the documentation is actually for.
Get people with the relevant subject-matter knowledge to review it.
Treat the first version as a starting point and keep updating it as you learn more.
The main thing I try to avoid is treating an AI summary as a substitute for the original conversation, or letting documentation become “AI-generated and therefore nobody’s responsibility”.
3. Performance reviews: finding the bigger picture
This one is a little less visible because the output isn’t something I’m publishing.
Performance reviews are something I take seriously. I want to understand what has happened over the whole review period, whether someone has genuinely progressed, how that compares with their previous review and where they should focus next.
Historically, that meant manually going through 1:1 notes, project conversations, Slack messages and meeting notes.
Granola has made it much easier to have meaningful conversations without simultaneously worrying about capturing every detail, and I now use Claude to analyse the meeting transcripts and relevant Slack conversations from the review period.
I don’t ask whether someone has had a good review. I ask it to identify themes and pull out the specific conversations so I can review them myself. The judgement and feedback remain mine.
That gives me a much better starting point for asking myself:
What’s the story of this review period?
It helps me avoid over-weighting whatever happened most recently or whatever conversation happens to be freshest in my head.
AI just helps me see the forest rather than spending all my time looking at individual trees.
And, yes, I also occasionally ask it to make my review shorter because apparently I am physically incapable of writing a small amount of text.
What I’ve learned
1. Give AI something real to work with.
The better the raw material, the better the output.
2. Don’t outsource the thinking.
I want AI to help me communicate what I think, not decide what I think.
3. Treat the output as a starting point.
I expect to edit it, challenge it and have other people validate it where appropriate.
4. Be careful what you put into these tools.
Think about what you’re sharing, which tools you’re using, and what your organisation’s policies say. “AI is useful” isn’t a reason to ignore confidentiality, privacy or security.
I’ve been careful throughout to keep things within the tools Human Made has approved, and private where they need to be.
So, has AI made me a better Engineering Manager?
I think it has.
But not because it has made me faster at doing the job. It’s helped me do more of the things I already believed were important.
I communicate more. I document more. I capture more of what we learn. I’m more consistent in things like performance reviews. I’m able to challenge my own thinking more often. And, perhaps most importantly, I’m less likely to have a good idea and then never do anything with it because the friction of writing it down feels like a monumental task.
One of the things from the LeadDev article that has stuck with me is the warning not to confuse feeling faster with actually improving our work. I’m not particularly interested in how many words AI helped me write, how many minutes it saved me, or how many things I can get through in a day.
The improvements I care about are harder to measure:
Am I communicating things I wouldn’t otherwise have communicated?
Are we capturing knowledge that might otherwise be lost?
Are my reviews better because I have more time to look at the bigger picture?
Are decisions clearer for the people who need to act on them?
Ultimately, AI hasn’t replaced my judgement. It has made it easier for me to apply it.
So rather than asking “What can AI do for us?”, I’m increasingly interested in asking:
“What good work am I currently not doing because the friction around it is too high?”
That’s where I’ve found the biggest gains.
And for those of you who think I still haven’t answered the most important questions: yes, AI helped me write this, yes, I did ask it to shorten it (this is the best it could do), and no, I still haven’t built that team dashboard.
As AI tools and agents have continued their march across all aspects of digital life, many companies are trying to use LLMs to improve the experience of purchasing goods and services on the Internet. Thus far, though, a vanishingly small number of people seem to be taking advantage of those capabilities, at least when it comes to using the popular food delivery app DoorDash with an outside AI agent.
In a third-quarter earnings call Thursday, DoorDash co-founder and CEO Tony Xu responded to an analyst question by noting that "AI agents are generating several hundred orders [on DoorDash] across the time that they've been up and running." In a marked understatement, Xu called this a "very low use case" for a company that handled just shy of 1 billion orders total in the third quarter of 2026 alone.
Speaking generally, Xu said he sees the potential for AI agents to be genuinely helpful for "long consideration purchases" and major decisions where agents would be "doing work on your behalf proactively in the background." However, Xu added, "when it comes to a task that's as simple as ordering food, we tend to see that come directly to DoorDash."
President Donald Trump has declared the imports of foreign-made factory robots to be a national security threat—ordering new US negotiations with trading partners while holding out the possibility of imposing new tariffs on such robot imports in the future.
Issued on October 28, Trump’s presidential proclamation represents heightened government scrutiny of foreign-made industrial robots that could complicate the manufacturing operations of major US corporations that rely on such robots. Those companies include Detroit automakers General Motors and Ford, electric vehicle manufacturer Tesla, and aerospace and defense giants like Boeing and Lockheed Martin.
Trump’s proclamation describes industrial robots and machinery as being crucial for producing US military weapon systems along with representing a “driving force” behind all critical infrastructure sectors within the US economy. The proclamation cites an investigation under US Secretary of Commerce Howard Lutnick as having found that US imports of such robots “pose[] risks to the United States industrial base and threatens the long-term competitiveness of the United States in a sector that is increasingly vital to national security.”
US chip champion Intel was so confused by the US government ban on foreign-made robots that it requested and received a waiver “out of an abundance of caution.” The tech company wanted to make sure that it could continue using certain robotic vehicles in its US chip fabs.
The uncertainty surrounding the Federal Communications Commission ban on certain foreign-made robots was revealed in the agency’s decision to grant Intel’s waiver request. On October 22, the FCC published its order allowing Intel to continue using the foreign-made robots in US semiconductor manufacturing facilities for a period of one year.
The robots in question are automated guided vehicles operating on “tracks or predefined paths” while often requiring operator oversight, according to Intel’s website. They help to move materials and items around within warehouses and factory floors.
When it comes to deciding the fate of the planet, Colleen Golja always thought science and reason would have a seat at the table. That was until one morning last September in London, when the climate researcher took part in the first in a series of war games. The goal: to prevent an uncontrolled global race to develop a technology aimed at cooling the planet but that comes with vast, unknown risks that could reshape life on Earth.
“I thought that would be such an easy thing. Like, we can all agree to do ethical research and make sure it's for the better of all humans,” she told WIRED. “And boy, was I wrong.”
The simulation, titled Exploring Geopolitical Tipping Points and Climate Cooling Strategies, saw a couple dozen foreign-relations experts, scientists, military personnel, and former government officials from across the world convene in a meeting room at Queen Mary University of London. After making introductions over coffee and little yogurts, they sat at tables arranged in a square with the name of the country or organization each person was playing: national governments, climate NGOs and nonprofits, indigenous groups, and tech companies. Golja was assigned to provide technical advice to help participants make scientifically literate decisions.
A polished portfolio used to get you hired. Now AI makes polished work cheap, and clients want proof you can solve problems, communicate clearly, and deliver today.
Artcraft got its start last year as a "controllable AI for artists" that allows for precise post-generation editing of AI-crafted images and videos. Over the weekend, though, the brand debuted its pivot to a suite of seven open source apps recreating the user interface and tools found in Adobe's Photoshop, Illustrator, Premiere, Lightroom, After Effects, InDesign, and Acrobat Pro.
In announcing those new apps on Reddit earlier this week, software developer Brandon Thomas said he used Anthropic's Claude Opus 5.5 to create "clean-room replacements" for Adobe's closed source software in Rust (with WebAssembly versions available for use in a browser). And while commenters on Hacker News and elsewhere have taken pains to point out the new software's many current shortcomings, Thomas makes the grandiose promise that the current "super early alpha" state will soon lead to something just as functional as anything Adobe has ever put out.
For decades, web designers obsessed over perfecting menus, tabs, and dropdowns. Now a single empty prompt box is quietly replacing them all. As AI turns websites into conversations, we're gaining incredible speed—but we may be losing something unexpected: the joy of discovery.
AI isn't killing web development—it’s killing the boring parts. The real winners won't be the people who can memorize another framework. They'll be the builders who can spot opportunities, solve business problems, and launch products that once required entire teams. The age of the one-person software company has arrived.
Today starts as normal with Obi’s poo walk along the canal, then he has his breakfast, while we walked to The Black Country Cafe for ours. This is a cheap cafe, the largest full English breakfast is £12 including Tea/Coffee, It comes on a very large plate with a mountain of food and the 3 slices of buttered toast on another plate. Unusually for me I could not finish it all.
Early start for Sonia and our visitors today as Sonia eldest two children Nick and Jason are both running in the Stratford-On-Avon ½ marathon and 10K respectfully. Sonia went along to provide moral support for them and help with the children (that is her superpower). For me, I went back to bed, or to be truthful just turned over and tried to sleep while they got ready, then after it was…
The ampersand is nearly 2,000 years old. yet designers still can’t agree on what it should look like. From ancient Roman *et* to hundreds of wildly different & designs, the story behind typography’s favorite squiggle is stranger than you might expect.
Today started at Knighton Visitor Moorings, this was beautiful quiet place, with some tree cover to keep us cool. Very poor 4G connection, but we have Star-Link up and running at the moment, Obi had his poo walk while I cooked breakfast which today it was a bacon and egg sandwich. It was a bit of a slow, as we had to pass lots of moored residential boats, it started to feel like almost…
This town has started to grow on us, yesterday I found Jones’s Coffee House, and today after Obi’s poo walk we are going there for breakfast, I am cycling as I will be carrying back any shopping, while Sonia walks (She is not a keen cyclist). The coffee was excellent, probably the best we have had this trip, they use the same Lavazza coffee we use at home.
The day started well, Obi when for his poo walk with Sonia, while I cooked breakfast and made the coffee, after breakfast I wanted to get back to finding the problem we have with our alternators. The problem is that we had the normal high pitched buzz during starting the engine, once started one of the battery warning lights flickered and the buzzer buzzed, but at only about ¼ of the…
AI promised to turn every developer into a 10x machine—but instead, it’s quietly frying our brains. We’re shipping faster than ever while thinking less, reviewing more, and losing the focus that made us good in the first place. The real cost of AI isn’t in the code—it’s in what it’s doing to our minds.
A practical guide to the terminal coding agent landscape in early 2026.
Just a year ago, most conversations about AI-powered development tools started and ended with Claude Code. Today, every major AI company has a coding agent, open source alternatives are flourishing, and new entrants seem to appear every week.
That’s exciting for developers. It’s also made choosing a tool significantly harder.
Before we get into the list, it’s worth clarifying the scope of this article. This isn’t a guide to every AI development tool on the market. It’s specifically a look at terminal-based coding agents: tools that can inspect repositories, edit files, run commands, and increasingly act like autonomous software engineering assistants.
That’s a very different category from IDE extensions, AI-native editors, chat applications, and desktop assistants. Those deserve their own comparison.
Things are moving ridiculously quickly, so treat this as a snapshot of the first half of 2026 rather than a definitive ranking. A new model release can completely change the picture overnight!
First-party agents
These are the tools built by the companies behind the models themselves. If you’re already paying for a specific provider, this is usually the most obvious place to start.
Vendor: Google Model: Gemini Desktop app: Yes Free version: Yes Open source: No
Google’s replacement for Gemini CLI, announced at Google I/O 2026. It gives developers access to the Gemini ecosystem through a supported first-party coding agent.
As of early 2026, Gemini isn’t generally considered the strongest option for coding work compared with Anthropic and OpenAI, but if you already have access to Gemini it’s well worth trying.
Vendor: Anthropic Model: Claude Desktop app: Yes Free version: No Open source: No
The benchmark most other coding agents are compared against. Claude Code is widely used, well understood, and tightly integrated with Anthropic’s models.
If you’re paying for a Claude Code subscription, this is the tool you should use. Trying to route that subscription through another tool could put your account at risk, so it’s generally not worth getting clever.
Vendor: OpenAI Model: OpenAI Desktop app: Yes Free version: No Open source: Yes
OpenAI’s answer to Claude Code. Codex has improved rapidly and is now a serious contender for developers already invested in ChatGPT or OpenAI’s wider ecosystem.
If you’re already using OpenAI models heavily, Codex is one of the most obvious alternatives to Claude Code.
Vendor: xAI Model: Grok Desktop app: VS Code and supported IDEs Free version: No Open source: No
xAI’s coding agent is still relatively early. Access currently depends on higher-tier Grok plans, and the tooling isn’t yet as established as Claude Code or Codex.
Teams evaluating Grok should think carefully about governance, neutrality, and whether the model’s behaviour aligns with their organisation’s requirements.
Open source agents
This is where things start to get interesting.
Open source agents support multiple providers, local models, and highly customised workflows. The trade-off is that you’re often responsible for more of the setup and configuration yourself.
Vendor: Open source Model: Multiple providers Desktop app: No Free version: Yes Open source: Yes
One of the strongest open source alternatives to Claude Code. Opencode supports Claude, OpenAI, local models and more through API access rather than through Claude Code or ChatGPT subscriptions.
If you’re paying by API and want flexibility across providers, this is one of the first tools I’d look at.
Vendor: Qwen Model: Qwen Desktop app: VS Code Free version: No Open source: Yes
A Qwen-focused coding agent built on Gemini CLI foundations.
Qwen’s open models have improved dramatically over the last year, especially for teams interested in local or lower-cost workflows. As of early 2026, though, the strongest Anthropic and OpenAI models still tend to perform better on complex engineering tasks.
Vendor: Kilo Model: Multiple providers Desktop app: VS Code, PHPStorm and others Free version: Yes Open source: Yes
A fork of Opencode with deeper integrations into the Kilo ecosystem.
Like Opencode, it supports multiple providers through API access and gives developers a lot of flexibility. Kilo’s focus on integrations and enterprise readiness makes it particularly interesting for larger teams.
Agent platforms and ecosystems
These tools sit somewhere between terminal agents, IDE integrations, and broader developer platforms. They’re included here because they all offer CLI coding-agent workflows, even if they’re better known for graphical products.
Vendor: GitHub Model: Multiple providers Desktop app: VS Code and supported IDEs Free version: Yes Open source: Source available
Copilot has evolved a long way from autocomplete.
GitHub’s biggest advantage is reach. Millions of developers already use GitHub every day, making Copilot one of the easiest tools to adopt across an organisation.
Vendor: Cline Model: Multiple providers Desktop app: VS Code and supported IDEs Free version: Yes Open source: Yes
Cline started life as a Claude-focused tool but has grown into a broader agent platform.
One of its more interesting features is the ability to manage work visually, including Kanban-style workflows, while still supporting coding-agent behaviour underneath.
Platform-specific agents
Some agents are built around a specific ecosystem rather than trying to be general-purpose development tools.
Vendor: Atlassian Model: Claude and OpenAI Desktop app: Jira Free version: Yes Open source: No
Rovo brings coding-agent functionality into the Atlassian ecosystem.
If your team already lives in Jira and Confluence, that context can be valuable. It’s less about being the best standalone coding agent and more about bringing AI directly into existing delivery workflows.
Vendor: Automattic Model: Claude Desktop app: No Free version: Yes Open source: Yes
A WordPress-focused coding agent available through WordPress Studio.
It’s still rough around the edges, but it’s interesting because it points towards a future where coding agents are deeply aware of the platforms they’re working with.
Apple Silicon users already have access to a lightweight local AI model through Apple Intelligence, and tools such as Apfel make it possible to interact with that model directly.
The context window is tiny compared with modern frontier models, so don’t expect it to tackle large software engineering tasks any time soon.
Many coding agents can connect to Ollama, allowing you to run models locally.
That’s attractive for privacy, security, and cost control, although local hardware remains the limiting factor. Open models are improving fast, but they’re still behind the frontier labs for complex coding work.
The agent matters less than the model
It’s easy to spend all your time comparing interfaces, but the underlying model usually matters more.
Most coding agents are wrappers around Claude, OpenAI, Gemini, Grok, Qwen, or local models. A brilliant interface wrapped around a weaker model will still struggle with complex engineering work.
Benchmarks are imperfect, but they’re useful signals. DeepSWE has attracted attention because it focuses on realistic software engineering tasks rather than narrow coding puzzles.
As of today, the broad picture is that Anthropic and OpenAI remain ahead for serious coding work. Open models have improved dramatically, but they’re still behind the frontier labs on complex engineering tasks.
That doesn’t mean open models are useless. They’re often excellent for constrained tasks, local workflows, experimentation, and teams with strict data requirements. But if your primary goal is coding performance, model choice matters more than the shell wrapped around it.
The same applies to Gemini. If you already have access to it, it’s worth exploring. If you’re spending money specifically for coding, though, the current benchmark picture suggests Anthropic and OpenAI are stronger bets.
The important thing to remember is that these rankings change fast. What looks true today may not be true six months from now.
What enterprise teams should consider
For enterprise teams, the most impressive demo isn’t always the best choice.
Before standardising on a coding agent, ask:
Where is code sent and stored?
Is customer or proprietary code used for training?
Can usage be audited?
Does the tool work with existing AI provider agreements?
Are developers using subscriptions correctly, or trying to route them through unsupported tools?
Can the organisation switch providers later?
Does the workflow fit existing security and compliance requirements?
For many teams, the key decision isn’t just which agent is best. It’s whether you want to commit to a single vendor’s ecosystem or keep enough flexibility to move as the market changes.
Which terminal coding agent should you choose?
If you’re paying for a Claude Code subscription, use Claude Code.
That’s the clean, canonical answer. It’s what the subscription is for, and trying to use that subscription through other tools may create account risk.
If you’re paying through API access, the picture gets much more interesting.
Opencode, Kilo, Pi, Oh My Pi, Crush Charm and similar tools give you the freedom to switch between providers, compare models, and build workflows around your own preferences.
If you’re already paying for Gemini, try Google’s tooling, but don’t assume it’ll outperform Claude or OpenAI on coding tasks. If you’re evaluating Grok, think about governance and neutrality as well as raw capability. If you’re interested in open models, test them seriously, but be realistic about the current gap between them and the frontier labs.
There’s no single winner for every team. There are simply too many workflows, pricing models, governance requirements, and personal preferences for that.
One thing’s clear: Claude Code isn’t the only game in town anymore. The terminal coding agent landscape is bigger, stranger, faster-moving, and more competitive than ever. For developers, that’s a very good thing.