Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Claude Code 2.0

npmjs.com

Post reply on HN
Print view View original

351–360 of 431 posts

Re: Claude Code 2.0

#351

Post by victorbjorklund »

saberience wrote: post #308
simonw wrote: post #49

Something 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…

Incredibly dangerous to use? Seems like a wild exaggeration. I’ve been using Claude code since launch, must have used it for 1000 hours or more by now, and it’s never done anything I didn’t want it to do. Why would I run it in a sandbox? It writes code for me and occasionally runs a build and tests. I’m not sure why you’re so fixated on the “danger”, when you use these things all the time you end up realizing that th…

It is risky. Just like copy-pasting scripts from the internet is. I have done both and nothing bad ever happened (that I know about). But it does happen. The risk of running code/commands on your computer that you have not checked before is not zero.

Re: Claude Code 2.0

#352

Post by jackstraw42 »

simonw wrote: post #331
saberience wrote: post #308

Earlier quoted context omitted.

Incredibly dangerous to use? Seems like a wild exaggeration. I’ve been using Claude code since launch, must have used it for 1000 hours or more by now, and it’s never done anything I didn’t want it to do. Why would I run it in a sandbox? It writes code for me and occasionally runs a build and tests. I’m not sure why you’re so fixated on the “danger”, when you use these things all the time you end up realizing that th…

You've been safe since launch because you haven't faced an adversarial prompt injection attack yet. You (and many, many others) likely won't take this threat seriously until adversarial attacks become common. Right now, outside of security researcher proof of concepts, they're still vanishingly rare. You ask why I'm obsessed with the danger? That's because I've been tracking prompt injection - and our total failure t…

This right here, it's fine until it's not. And the best-designed threats make sure you don't become aware of them.

Re: Claude Code 2.0

#353

Post by DowsingSpoon »

saberience wrote: post #308
simonw wrote: post #49

Something 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…

Incredibly dangerous to use? Seems like a wild exaggeration. I’ve been using Claude code since launch, must have used it for 1000 hours or more by now, and it’s never done anything I didn’t want it to do. Why would I run it in a sandbox? It writes code for me and occasionally runs a build and tests. I’m not sure why you’re so fixated on the “danger”, when you use these things all the time you end up realizing that th…

Just two days ago, I asked Claude Code (running as a restricted non-admin user) to generate a unit test. I didn’t look too closely at exactly what it wrote before it ran it for me. Unbounded memory use locked the system up so hard it stopped responding to all user input. After a few minutes, the machine restarted automatically. Oof.

Re: Claude Code 2.0

#354

Post by hiatus »

saberience wrote: post #320
guhcampos wrote: post #315

Earlier quoted context omitted.

It is dangerous. Just yesterday my cursor agent made some changes to a live kubernetes cluster even over my specific instruction not to. I gave it kubectl to analyze and find the issues with a large Prometheud + AlertManager configuration, then switched windows to work on something else. When I was back the MF was patching live resources to try and diagnose the issue.

But this is just like giving a junior engineer access to a prod K8s cluster and having them work for hours on stuff related to said cluster... you wouldn't do it. Or at least, I wouldn't do it. In my own career, when I was a junior, I fucked up a prod database... which is why we generally don't give junior/associate people to much access to critical infra. Junior Engineers aren't "dangerous" but we just don't give th…

> Junior Engineers aren't "dangerous" but we just don't give them too much access/authority too soon.

If it is not dangerous to give them this access, why not grant it?

Re: Claude Code 2.0

#355

Post by kid64 »

simonw wrote: post #338
brookst wrote: post #317

Earlier quoted context omitted.

Dangerous how? Claude code literally asks before running any command. I suppose they’re dangerous in the same way any terminal shell is dangerous, but it seems a bit of a moral panic. All tools can be dangerous if misused.

Many people (myself included) run them in YOLO mode with approvals turned off, because it's massively more productive. And that's despite me understanding how unsafe that is more than most! Even with approvals humans will fall victim to dialog fatigue, where they'll click approve on everything without reading it too closely.

Anthropic's official recommendation is to only use YOLO mode in an airgapped container (see "Safe YOLO mode" here: https://www.anthropic.com/engineering/claude-code-best-pract...)

Re: Claude Code 2.0

#356

Post by OisinMoran »

Two feature suggestions: 1. When showing a diff, indicate what function the altered lines are in (Github does this nicely) 2. There are leading spaces when copying some multiline snippets from the output and these make it harder to copy paste

Re: Claude Code 2.0

#357

Post by wiesbadener »

simonw wrote: post #331
saberience wrote: post #308

Earlier quoted context omitted.

Incredibly dangerous to use? Seems like a wild exaggeration. I’ve been using Claude code since launch, must have used it for 1000 hours or more by now, and it’s never done anything I didn’t want it to do. Why would I run it in a sandbox? It writes code for me and occasionally runs a build and tests. I’m not sure why you’re so fixated on the “danger”, when you use these things all the time you end up realizing that th…

You've been safe since launch because you haven't faced an adversarial prompt injection attack yet. You (and many, many others) likely won't take this threat seriously until adversarial attacks become common. Right now, outside of security researcher proof of concepts, they're still vanishingly rare. You ask why I'm obsessed with the danger? That's because I've been tracking prompt injection - and our total failure t…

Hi Simon,

I share your worries on this topic.

I saw you experiment a lot with python. Do you have a python-focused sandboxed devcontainer setup for Claude Code / Codex you want to share? Or even a full stack setup?

Claude's devcontainer setup (https://github.com/anthropics/claude-code/tree/main/.devcont...) is focused on JS with npm.

Re: Claude Code 2.0

#358

Post by coldtea »

saberience wrote: post #308
simonw wrote: post #49

Something 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…

Incredibly dangerous to use? Seems like a wild exaggeration. I’ve been using Claude code since launch, must have used it for 1000 hours or more by now, and it’s never done anything I didn’t want it to do. Why would I run it in a sandbox? It writes code for me and occasionally runs a build and tests. I’m not sure why you’re so fixated on the “danger”, when you use these things all the time you end up realizing that th…

>I’ve been using Claude code since launch, must have used it for 1000 hours or more by now, and it’s never done anything I didn’t want it to do.

You know what neighbors of serial killers say to the news cameras right?

"He was always so quiet and polite. Never caused any issues"

Re: Claude Code 2.0

#359

Post by pmarreck »

simonw wrote: post #49

Something 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…

I too am amazed. Real-world example from last week:

After using gpt5-codex inside codex-cli to produce this fork of DOSBox (https://github.com/pmarreck/dosbox-staging-ANSI-server) that adds a little telnet server that allows me to screen-scrape VGA textmode data and issue virtual keystrokes (so, full roundtrip scripting, which I ended up needing for a side project to solve a Y2K+25 bug in a DOS app still in production use... yes, these still exist!) via 4000+ lines of C++ (I took exactly one class in C++), and it passes all tests and is non-blocking, I was able to turn around and (within the very same session!) have it help me price it to the client with full justification as well as a history of previous attempts to solve the problem (all of which took my billable time, of course), and since it had the full work history both in Git as well as in its conversation history, it was able to help me generate a killer invoice.

So (if all goes well) I may be getting $20k out of this one, thanks to its help.

Does the C++ code it made pass the muster of an experienced C++ dev? Probably not (would be happy to accept criticisms, lol, although I think I need to dress up the PR a bit more first), but it does satisfy the conditions of 1) builds, 2) passes all its own tests as well as DOSBox's, 3) is nonblocking (commands to it enter a queue and are processed one set of instructions at a time per tick), 4) works as well as I need it to for the main project. This still leaves it suitable for one-off tasks, of which there is a ton of need for.

This is a superpower in the right hands.

Re: Claude Code 2.0

#360

Post by CuriouslyC »

faxmeyourcode wrote: post #349
CuriouslyC wrote: post #5

Earlier quoted context omitted.

The only real reason to use Claude Code is the inference plan. The agent itself isn't anything special.

Curious that you say that. I feel like the reason I love to use claude code is mostly because of the orchestration around the model itself. Maybe I've been trained by claude to write for it in a certain way. But when I try other clis like codex, gemini, and more recently opencode, they don't seem as well built and polished or even as capable, despite me liking the gemini and gpt-5 models themselves and using their ap…

Claude is highly autonomous. You can yeet short underspecified prompts at it, and it's tuned to produce good vibe code output, though very samey since they've squashed the distribution a bit in order to effectively steer the model. GPT5 is less autonomous and also needs more steering, but the upside of this is that when Codex can't do something, it'll come back to you for feedback, whereas when Claude cant' do something it implements a toy/mock version then typically lies about completing the task successfully in the final summary output.
Post reply on HN