Latest CLI version feels like a step backwards

[garrettHensley]

Sessions or threads or whatever feels like just extra bloat.
If you are using CLI then you are probably already using a multilexer like zellij or tmux to resume work - and if you aren't then what are you doing here?
Why not just save the bloatware features for the GUI app, and let CLI be?

[bomtobe-hgkim]

Could you share what feels bloated in practice: extra commands, startup cost, or the session model? Some CLI users may not run a multiplexer. Keeping the one-shot CLI path simple while making session management opt-in could serve both workflows.

[garrettHensley]

I'm talking about feature bloat here, I recognize that smashing in a thousand features is totally the AI way of doing things, except that we should be asking ourselves not if we can but if we should.

It's a GUI feature that really has no place in the CLI app. CLI users value elegance and simplicity- Like being able to consistently close the program by pressing CTRL-C or :q
Not every workflow needs to be supported, keep it simple and let the GUI app handle the more complex stuff

And frankly, having to press more keys to navigate all this session stuff is a pretty big ask after I just flashed three V6s at my local climbing gym.

[garrettHensley]

this is a reply to @bomtobe-hgkim

[bomtobe-hgkim]

That makes sense—the concern is the CLI’s default interaction surface and key flow, not just a few extra commands. Would a strict one-shot CLI path that keeps Ctrl-C/:q behavior intact, with session navigation only behind an explicit opt-in, address it? Or do you see the session model itself as GUI-only?