Claude Code 2.0
101–110 of 431 posts
Re: Claude Code 2.0
#102Earlier quoted context omitted.
> why does it default to full screen? Pardon my ignorance, but what does this mean? It's a terminal app that has always expanded to the full terminal, no? I've not noticed any difference in how it renders in the terminal. What am i misunderstanding in your comment?
A tui does not have to start full screen, v1 of claude did not take over the entire terminal, it would only use a bit at the bottom and scroll up until it was full screen. I just downgraded to v1 to confirm this.
pretty sure your old behavior was the broken one tho - i vaguely remember fugling with this to "fullscreen correctly" for a claude-in-docker-in-cygwin-via-MSYS2 a while ago
Re: Claude Code 2.0
#103Has anyone figured out how to do claude sub agents without using claude? some sort of opensource cli with openrouter or something? I want to use subagents on differnt LLMs ( copilot,selfhost ).
Re: Claude Code 2.0
#104It's first time I started get hit by "ERROR Out of memory" in CC - after about an hour of use. I'm on Mac Pro M4 Max with 128 GB RAM...
Re: Claude Code 2.0
#105Earlier quoted context omitted.
They're only as dangerous as the capabilities you give them. I just created a `codex` and `claude` user on my Linux box and practically always run in yolo mode. I've not had a problem so far. Also, I think shellagent sounds cooler.
That's a great way to run this stuff. I expect the portion of Claude Code users who have a dedicated user setup like this is pretty tiny!
Not the exact setup, but also pretty solid.
Re: Claude Code 2.0
#106To those lamenting that the Plan with Opus/Code with Sonnet feature is not available, check the charts. Sonnet 4.5 is beating Opus 4.1 on many benchmarks. Feels like it's a change they made not to 'remove options', but because it's currently universally better to just let Sonnet rip.
Sure but I want to review the ripping plan so it tears along the correct lines.
Re: Claude Code 2.0
#107Something I realized about this category of tool (I call them "terminal agents" but that already doesn't work now there's an official VS Code extension for this - maybe just "coding agents" instead) is that they're actually an interesting form of general agent . Claude Code, Codex CLI etc can effectively do anything that a human could do by typing commands into a computer. They're incredibly dangerous to use if you d…
Re: Claude Code 2.0
#108Earlier quoted context omitted.
is Plan mode any different from telling Claude "this is what I'd like to do, please describe an implementation plan"? that's generally my workflow and I have the results saved into a CLAUDE-X-plan.md. then review the plan and incrementally change it if the initial plan isn't right.
There's a bit of UI around it where you can accept the plan. I personally stopped using it and instead moved to a workflow where I simply ask it to write the plan in a file. It's much easier to edit and improve this way.
To be honest, Claude is not great about moving cards when it's done with a task, but this workflow is very helpful for getting it back on track if I need to exit a session for any reason.
Re: Claude Code 2.0
#109Earlier quoted context omitted.
This enables the /resume command that lets you start mid-conversation again. Storing the data is not the same as stealing. It's helpful for many use cases. I suppose they should have a way to delete conversations though.
That's not just them saving it locally to like `~/.claude/conversations`? Feels weird if all conversations are uploaded to the cloud + retained forever.
Re: Claude Code 2.0
#110Something I realized about this category of tool (I call them "terminal agents" but that already doesn't work now there's an official VS Code extension for this - maybe just "coding agents" instead) is that they're actually an interesting form of general agent . Claude Code, Codex CLI etc can effectively do anything that a human could do by typing commands into a computer. They're incredibly dangerous to use if you d…
[flagged]
I was under the impression that Docker container escapes are actually very rare. How high do you rate the chance of a prompt injection attack against Claude running in a docker container on macOS managing to break out of that container?
(Actually hang on, you called me out for suggesting containers like Docker are safe but that's not what I said - I said "a safe container" - which is a perfectly responsible statement to make: if you know how to run them in a "safe container" you should do so. Firecracker or any container not running on your own hardware would count there.)