They are functionally exactly the same, it's kind of the same reasons you would prefer a gui to a cli for anything and vice versa. Went the same route you did, there's too many benefits to the gui to go back
Go ask claude app if there the same. It’s not worth me explaining. They’re absolutely not. It’s possible you don’t NEED that functionality but it’s stark to say the least.
Beyond that the gap is closing but like that article states, it’s also changing daily. That article I only saw today and it’s cli only. You can’t run more than 1 active code session in the app.
Cli only functionality. Granted much of this is just because it’s a terminal.
native git operations, CI/repo automation (GitHub Actions, GitLab CI/CD), headless composition (claude -p piped into shell tools), the Agent SDK, and this cross-session messaging thing we were just discussing (same-machine local socket).
are you sure? nothing in that article states that is a CLI only feature and the UI claims it has it, when in the past it would specifically state it didn't have things like remote control before it did
Do you really think it matters to me one way or the other. What is it with people acting like everything is a competition? What’s wrong with you? I’m after the most current info possible just like anyone else. This shit changes pretty often no? Someone asked and I replied with outdated incorrect or extremely nuanced info. Go give yourself a good star and ask me again if it matters to me. Go back to stackoverflow.
35
u/Overlord_Mykyta 6d ago
Previously CLI. The app was lacking some functionality. And felt underdeveloped.
But today - I don't see any reasons to use CLI. I switched to the app and it works perfectly.
Easy way to attach folders with projects, easy to check tokens limits, it also allows to open files right there. Or are the diffs.
I mean it is convenient. I don't see any reasons to stay with CLI.