e244ecf4-f6cf-4ffc-8a3b-5cdf7bb75a7f

[giscus[bot]]

e244ecf4-f6cf-4ffc-8a3b-5cdf7bb75a7f

Discover why AI-powered CLI tools like GitHub Copilot CLI, OpenCode, and Claude Code can boost productivity and deliver better quality results than IDE extensions.

https://www.ssw.com.au/rules/ai-cli-tools

[JeanThirion]

I think using Web interfaces or other integrated interfaces (Claude Desktop) makes so much more sense in may scenarios: deep research across multiple devices, "writing" tasks, Anything that requires more than just text (diagrams, code examples, etc...).

Obviously CLIs are AWESOME when you want context awareness or when you want to pilot stuff from code though.

Claude Code is my personal favourite <3

My 2cts on the future: tools like OpenCode will not survive because models are going to be more and more "locked" to their stacks (e.g. anthropic models only usable on Antrophic products) just because AI companies will need to recoup their extraordinary R&D costs and will need to capture clients more than with just models (which get out of fashion really fast).

[stephanfakossw]

As a non dev, I haven't found a scenario where a CLI would work for me. It's still great to see that you can give AI more context to cut some corners 😊

[danielmackay]

I love using AI CLI tools as my daily driver. I will jump back into IDE AI tools sometimes if I want more fine grained control over the MCPs I'm using for a specific task.

AI CLI tools are great for many things:

• Planning work
• Implementing work
• Investigating legacy repositories
• Brainstorming solutions.

[TobyChurches]

I havent really given AI CLI tools a proper go... I generally opt for the easier UI but it does seem to have some major advantages - Looking forward to giving Claude Code a run

[Calinator444]

I've found cli tools to be the most useful when your code changes involve integrating with external systems. For example I tend to use Radix UI in most of my projects, so if I'm asking an agent to write some front end code for me doing it via the CLI is better because it will be able to install the necessary components using NPM.

[miichaelsmedley]

I’ve been vibe coding for about two years, but in the last three months the quality has jumped massively. I’ve shipped small tools and apps I use in my own life—things I simply wouldn’t have been able to build before.

I pretty much always have a terminal open now. I use OpenCode with OpenRouter, Claude Code, Gemini and Codex—sometimes all at once, depending on the problem. And it’s not just for code. With enough context, these tools will generate PowerPoints, Word docs, organise files and structure work end-to-end.

It’s a genuine unlock.

[sam-s-maher]

I wasn't aware of CLI Tools until now, but as a terminal lover I'll be sure to give it a whirl!

[joshbermanssw]

I'm yet to start battle testing CLI tools in my own daily development. I've seen devs I work with often seem to prefer Claude Code and it's something I've definitely wanted to try.

[suiyangqiu]

I haven't quite had a proper go at trying out AI CLI tools, but I can definitely see the benefits of them versus browser versions, very interested in giving Claude Code a go and trying out the sub-agents.

[designbyalex]

I haven’t tried AI CLI tools yet, but I’m really curious about the extra capabilities they offer.

I usually stick to GUIs out of convenience (and a bit of ignorance), but the deeper context and flexibility of CLI tools has definitely made me keen to have a tinker.

[kulesy]

During development, I mostly just use ChatGPT for everyday tasks. But when I want my AI Agent aware of the context of my files and able to run CLI commands, I use Claude Code.

[Username-must-be-unique]

CLI-based tools are ideal when you want to avoid the overhead of web or desktop interfaces. They enable efficient parallelization by spawning multiple AI agents simultaneously, and pair especially well with Git worktrees - allowing you to run and coordinate multiple agents in parallel without friction.

I am surprised that this page does not explore tools like Auto Claude or Vibe Kanban

While they present a UI layer, both rely heavily on CLI-driven agents under the hood to execute and manage multiple tasks in parallel. Omitting them feels like a missed opportunity to highlight how CLI-first architectures can scale agentic workflows effectively even when surfaced through a UI.

[bahjatalaadelssw]

I've see and heard good things about Claude Code

[andrewwaltosssw]

Looking forward to giving CLI a go. It seems to have similar functionality to Cursor but as its in the terminal, it makes me feel more like a hacker so that's cool.

[ricksu978]

I don’t have a strong preference for CLI tools.
They all feel pretty similar to me. In my view, the AI model matters more because it has a much bigger impact on the quality of the output.

[uly1]

I de-duplicated my photo library

[RobJT-wq]

I haven't used an AI CLI before but I'm interested in trying it out

[AntPolkanov]

I've been using Copilot_here for the last several months and it's been a blast!
Can do more in a day with it!

[PennyWalker]

As a non-dev, I haven't used a Code CLIs, but I can definitely see the benefit - why use a slower system when there is a better way! I'll stick to my desktop apps for now! Claude and ChatGPT all the way! :D

[jernejk]

I quite often use Warp, Copilot CLI, Gemini CLI and OpenCode CLI interchangeably, depending on what model I need and how much budget I have left, load-balancing between different providers.

The CLI tools are great for "I don't care how you solve it" but when it's important how things are solved, I go for IDE approach like VS Code or Antigravity.

[Marxoz]

I love Claude Code, but that said, I started using Gemini CLI on smaller personal projects and I am really impressed!

[SamBWagner]

CLI is fundamentally a place for developers. Then these tools are really awesome.

If you're a non-developer, don't bother. The CLI is already so horrifying to begin with.

The they exist is pretty awesome though.

[ZenoWang1999]

From an intuitive standpoint, GUIs are more user-friendly than CLIs. However, as IDEs continue to accumulate features and plugins, an IDE overloaded with elements is not necessarily easier to understand than a CLI.
From another perspective, I have been using Claude Code extensively and have observed that the CLI consumes fewer tokens than the extension. I have also seen similar views on Reddit: https://www.reddit.com/r/ClaudeAI/comments/1o1ccfz/claude_code_via_extension_consumes_more_tokens/

[thom-wang]

I didn't really use AI CLI before; I'm just using the Copilot Chat panel in VS Code all the time. It's strong enough to make all the changes I wanted to make, and all I need to do is review all the changes he made and delete the unrelated stuff :-)

[yaqi-lyu]

I tried Claude Code for a short time before. I found it not that easy to read large amounts of text there, so I switched to using the VS Code extension instead. It’s powerful, but I haven’t explored it much yet. I saw they’re providing agent skills now, so I might try these CLIs again.

[tino-liu]

Woop! First few minutes of reading this got me hooked in. I'm so gonna try this!

[babakamyljanovssw]

I haven't used AI CLI tools before, so don't have preference which one is the best. But definitely going to try one of them out and decide if it worth to switch to AI CLI over IDEs.

[jimmidier]

Claude Code -

❌Flexibility - Similar to GitHub Copilot, Claude Code locks you in to one provider - in Claude's case; Anthropic.

Not sure what this means but Claude Code can actually point to different providers if supported.
Here's an example output of connecting to Kimi K2 from Claude Code

Version: 2.1.7
Session name: /rename to add a name
Session ID: 291cecf3-1f30-4886-8af6-e93a2ad77329
cwd: /Users/zhenghaorui/codes
Auth token: none
API key: ANTHROPIC_API_KEY
Anthropic base URL: https://api.kimi.com/coding/

Model: kimi-k2-0905-preview
Memory:
Setting sources:

[MarcusIrmscherSSW]

I have heard a lot about Claude Code, I think Ï may have to give it a go.

[edkranz]

I think the video is a bit outdated! The Gemini Web UI is very good now, and has a lot of benefits over CLI. E.g. canvas, docs integration, and video integration.

They are different tools for different purposes.

Additionally, for quickly prototyping UI's or other small code projects, the Web UI's (Gemini, ChatGPT, Claude), can make sharing these projects easier as they are already "deployed".

But I definitely see the value of CLIs for running quick questions, and for people who work primarily in the CLI and devs. For that, it's a no brainer.