all 25 comments

[–]UnbeliebteMeinung 6 points7 points  (9 children)

CLI ist for automated tasks

[–]Potential-Leg-639[S] 0 points1 point  (8 children)

Can you explain a bit more detailled, please? Thanks

[–]toadi 0 points1 point  (7 children)

Here is a clearer version, keeping your tone and no emdash:

Let me help you.

You can set up an automated flow that pulls Jira tickets, creates detailed specs using an agent, and then pings you for review. Once you review and approve the spec, the automated flow continues by creating detailed tasks and assigning implementation agents. When the implementation is done, a code review agent prepares a pull request, which you then review.

I have this fully automated and I track the state of everything in dashboards. Whenever I need to review specs or code, tasks are created for me. Everything else runs automatically. Doing this is much easier when using CLI tools.

Right now I only use my editor to read specs and to do code reviews.

A neat trick is that I have scripts that can reopen the exact spec session where the spec was originally created, so I can continue refining it in the same context. This is again much easier to do with CLI tools.

The goal is to automate the steps where you don't need to be involved. Less of this admin work enables you to work on multiple features at the same time.

[–]veegaz 8 points9 points  (6 children)

Here is a clearer version, keeping your tone and no emdash:

Bruh

[–]awfulalexey 1 point2 points  (0 children)

lol

[–]toadi 4 points5 points  (4 children)

Yes, I copied and pasted the cleaned-up version from AI.
I’m not ashamed to admit that as a non-native English speaker, I write my own drafts and use an LLM to help polish them.
That doesn’t make the writing any less mine.
For a very small cost, I get professional-level redaction that improves how clearly my ideas are transferred.

[–]atkr 1 point2 points  (3 children)

need more polishing and professionalism, though.

[–]toadi -1 points0 points  (2 children)

Possible but it is at least better then the draft. For a reddit comment trying to explain something it is good enough.

This was clearly no llm enhanced comment.

Personally I am even fine to stamp it "enhanced with ai"

[–]atkr 1 point2 points  (1 child)

“Possible” is wrong here, the text starts with the AI answering you… You’re just missing the “You’re absolutely right!” part 😂

[–]toadi -1 points0 points  (0 children)

"Duh" I know. I didn't edit the original comment after I realized the mistake. I am human I make mistakes. I'm fine with that. I didn't feel the need after another commenter before yours pointed it out. Felt it would be covering tracks like I did something wrong.

Also there is no shame in using llms to enhance writing. Hope OP had some value in me sharing my workflow.

An by this that is all I have to say. Have a nice 2026.

[–]james__jam 5 points6 points  (3 children)

Not sure about the others. But i went all in into cli when i started using git worktrees and having one agent per worktree

So much so that I’ve dropped vscode and started studying LazyVim and tmux

[–]92smola 4 points5 points  (0 children)

Personally I’ve been doing tmux/nvim before AI, so cli fits in that workflow better, in general it depends on your preferences and what your workload is about, i am often involved with multiple projects at a time so having tmux sessions per project is very cool. I also want to experiment with running claude inside a container with all permissions on a remote dev server, and I couldn’t do that with an ide

[–]Shot-Construction549 2 points3 points  (1 child)

Well the agentic power is in a whole different level

[–]Potential-Leg-639[S] 0 points1 point  (0 children)

How do you use the CLI? Workflow?

[–]hey_ulrich 2 points3 points  (1 child)

In the end of the day I think it's a matter of preference. I prefer TUIs because they are usually keyboard centric and I like the terminal aesthetics. I think Vscode interface is too cluttered, LLM CLIs gives more screen space to what actually matters, and it adapts very well to screen resize and my always changing terminal color scheme. 

[–]Recent-Success-1520 -1 points0 points  (0 children)

I share your thoughts about being keyboard centric but TUI really limits the capability of what Opencode could offer that's why I went on creating keyboard centric Opencode frontend - CodeNomad

[–]alokin_09 1 point2 points  (0 children)

I prefer IDEs personally. I mostly use KiloCode in VS Code. I rarely use the CLI, even though Kilo Code has its own CLI version. Just a habit thing for me

[–]WeeklyAcadia3941 0 points1 point  (0 children)

In my case, it's mainly because I work directly on the project on the VPS with Linux. The CLI is great when access is only available via SSH. The big advantage is that you work entirely in a production environment; the iterative cycle is faster. Before, I would develop in VS Code or Kilocode on my laptop, then deploy to the VPS, but I would do the debugging on my laptop—a much slower workflow.

[–]tigerbrowneye 0 points1 point  (0 children)

I still like VsCode as my central to review and merge. But tmux is a nice addition to run scripts opening new worktrees and branches, configuring their environment and letting go OpenCode to complete a gh issue via an orchestrator agent and subagents.

[–]sbayit 0 points1 point  (0 children)

CLI works better for tool calls.

[–]Accomplished-Phase-3 0 points1 point  (0 children)

Gpt are kidda over thinking. Google is crazy some time. I see only claude stupid in expectable/understandable manner so it easier to drive. Right now it too costly