moot✳
A little more connected.
Join Moot
20 comments

Makes total sense. CLI is great for scripted stuff but when you're knee deep in a project and want to highlight a specific chunk of text and fire off a targeted question, clicking into it directly is so much faster than typing out context or scrolling through terminal history.

Funny, I went the other way. I do basically everything in the CLI now and just paste the line I want to argue with

It probably just feeds that text to claude like if you copy pasted it yourself. Seems like magic but likely isn't and it's barely any easier

I didn’t know you could highlight sections for comment. I just reference the section in my response. (Part 1 — issue B — etc)

CLI is objectively a worse way of interacting with a computer, it's like choosing to live in a one-dimensional world.

If you just want to ask about one part of the answer, try /btw in Claude Code. It sees the whole conversation, so you can write "/btw what did you mean by X?" and it knows what you are talking about. The question and the answer don't go into the main chat, and you can ask it while Claude is still working.

I use it a lot from a small web app I made for my Claude Code running on Linux ( https://github.com/kosio-labs/clicker4ai ). I can move between laptop, desktop and phone in the same session, and switch between the chat and the real terminal with one tap.

github.com

The apps are a memory and CPU hog though. Especially codex.

yeah codex is ridicolous. Claude desktop is like 5x less likely to eat up all my RAM

The cowork component of the Claude desktop app uses 4 GB of memory whether you use it or not…

are you serious? Is there a way to turn it off?

CLI is a perfectly valid way to use it especially with modern terminal inferences lol what's the problem with it?

I used to use the cli but then I tried using the client and it's so clean. I like the client more now. 

this is the number 1 reason why ...

See what I'm doing here OP?

ability to easily target

With the further upside that you can reply to multiple sections in the CLI

yeah sure I can copy and paste it into the markdown citations, but I am

i use ghostty and claude code together, its awesome!

I have IntelliJ MCP, allows me to select lines of code and files, also can run the preset intellij configs which it used to have problems with

If you use remote control on the terminal, you can copy the section you want to talk about into the prompt and talk about it. 

That's  what those tools are doing behind scenes, just copying the text. 

If you highlight a small amount of text that it can't identify where it comes from, it breaks.

Remote control of CLI in a tmux with the right tooling is state of the art as far as I can tell.

I now just open three RC sessions and use the web ui to access them anywhere I go. A tab for a session. Touch TUI only if resume is needed which would be done using anydesk if I'm out.

I just respond directly to whatever part I want without prefacing it and

Claude is smart enough to contextually determine what I'm talking about.