I’ve always been a CLI person. Lower system resource usage, faster updates, full feature parity—those three things kept the terminal ahead of the desktop app for most of the past year.
But the desktop app is fine now. Honestly fine.
About two or three weeks ago Anthropic overhauled the desktop app. Over 90% of the features now sync with the terminal. The remaining 10% is stuff only advanced developers will ever touch: hooks, certain subagent behaviors, deeper MCP configuration. The desktop app’s update cadence has picked up too. It’s nothing like the once-every-two-weeks rhythm from before.
The newest features still land on the CLI first. But honestly, the newest features have a high chance of being abandoned mid-stream. Anthropic ships new features faster than they maintain the old ones. A regular user has no business chasing things that are still in research preview and full of bugs. Wait for the feature to stabilize, then it migrates into the app—that’s the more comfortable path.
So if you’re a beginner who finds the terminal intimidating, starting from the desktop app is completely fine. Once you’ve gotten used to the flow, figured out which advanced features you actually need, and feel boxed in by the GUI, you can switch over to the CLI. The reverse order—starting with the CLI when you don’t even know what you need it for—costs more.
Why am I still on the terminal? Because I’ve already built workflows around hooks, custom skills, and shell-level mixes with git, ffmpeg, and yt-dlp. Those things are smoother in the CLI. If your day looks more like “I mostly chat with Claude Code, write documents, organize data,” the desktop app is enough.
Put another way: tools aren’t right or wrong, they fit or don’t fit what you need right now. Start with the desktop app, get up and running. Six months later if you find you want more automation, want hooks, want to wire in local scripts, then spend an afternoon learning the terminal. There’s no reason to get blocked by flags and config files on day one.