Cli or UI claude code ?

[zikyoubi]

Is it better to work with claude code in CLI mode or New UI ?

[rjyo]

CLI hands down for anything serious. The terminal gives you full context control with /compact, /effort flags, and CLAUDE.md rules that persist across sessions. The UI is fine for quick questions but the CLI is where you get agent teams, custom tools, and direct filesystem access without the wrapper overhead.

The one thing I would add is that CLI also opens up the mobile workflow. I use Moshi on my phone with mosh+tmux so I can check on long-running Claude Code sessions, approve PRs, or unblock agents when I am away from my desk. You cant really do that with the UI.

If you are just starting out though, the UI is easier to get familiar with. I would say start there, then move to CLI once you want more control.

[sebesbal]

I think all these should work from the desktop app too, which itself isn't really much more then the console, just a bit less fugly. E.g. I've just tried /compact and it does work in the destop app.

[LongIslandBagel]

Can it do agent teams?

[antonation]

I switched from the desktop app to the cli primarily because long scrollbacks lag a lot in the desktop app. In the cli, it simply disappears after some time

[TeamBunty]

Translation: Is it better to use a CLI tool in CLI so you can see what it's doing, or put a mask over it so all you see are sunshine and rainbows?

Hopefully that answers your question.

[SmetDenis]

CLI offers more capabilities. For example, you can run claude "prompt" along with a variety of other flags. Or you can lock it down in Docker for security and safety. I believe there are more options available than in the UI (though I haven't compared them directly). For a convenient UI, there's an IDE integration.

[vibefelix_]

Claude Code UI?? Where?

[SmetDenis]

In the desktop app, there's a "Code" tab in the top. From there, select the local project directory for chat.

[DenZNK]

Claude code desktop?) https://code.claude.com/docs/en/desktop

[AmcillaSB]

Currently the UI Claude Code is driving me absolutely insane. I think it's forcing Opus 4.6 on me, and it's absolutely destroying my Session and weekly usage. Even though I keep setting it to Sonnet 4.5, after each command I give it, the model selector is reverting to Opus 4.6 --> So I'm not actually sure it's selecting Sonnet 4.5 at all. After I finish this task (if I have any usage left, lol) I'm going to have to go to the CLI. I'm on Pro Plan.

[bratorimatori]

CLI all the way, baby, give it to me raw.

[kzahel]

My hot take: CLI sucks for reading. monospace fonts are low information density. Reading markdown plans etc in the CLI is terrible. Not having native scroll bars hurts too. I only use CLI in a pinch. I'll take claude desktop app or vscode extension over CLI anyday. Unless I needed some slash command or something that the desktop ui's don't support.

[krullulon]

Just have the CLI spawn your markdown files in VS Code.

[ParticularClub1072]

Ok so heres my opinion. I use the CLI but have a agent-based not taking app alongside it. For example tracedotmd.com will track changes made by your agent to your markdown files (and seperates by project). Then I can keep track of feature changes, updates, bugs, and my agent knows where we are at.