Birbla

Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

Sign in
  • Hacker News
  • I hate it when I ask a questions and claude starting to butchering my source code
    by firemelt
  • Great. Can we have thought traces back?
    by exabrial
  • There's a setting called `showThinkingSummaries` which you can enable to see them (going forward).
    by maxbond
  • Anything that happens on the client, you can capture. You can capture anything delivered to the client that isn’t exposed by downloading the Claude code binary, unpacking it, and patching the nodejs HTTP library fetch call to listen for all traffic, then analyze it and build your own tracing. Or you can MITM with a proxy for a bit more heavy handed approach. It sucks you don’t get it out of the box, but you could literally paste my comment into a Claude prompt and have the tracing you desire in probably less than 30 minutes
    by SOLAR_FIELDS
  • It will require more attention to settings.local.json :)
    by beybol
  • Hmmmm. OK. So yesterday I was accepting all these prompts in the manual mode for a solid hour, then I switched to Auto. Side project, nothing critical (creating ComfyUI workflows with CC and Opus). Walked away from the puter, got notified it was done. It did a good job, and by sheer luck it didn't delete a database or format my drive. But I felt a bit uneasy. Can we trust them now? I don't think I'd switch to Auto for a professional project. Not a chance. But for side projects? Yeah maybe - and only once I'd have validated whatever plan mode had come up with. Setting Auto as default? That's not cool. I'd set Plan mode as default.

    Had a conversation with a friend who's struggling with code, and recently got into AI tools. The one thing that kept him from using Claude Code? Auto mode. My friend was convinced it didn't ask permission before touching his codebase by default.

    Anthropic: careful. We the people trust Claude Code more than some other harness precisely because it asks you before doing anything. If you go full auto, there will be collateral damage. And yeah, I know, you can roll back. But some newcomers aren't familiar with that kind of stuff. Don't do it bro. Let us switch to Auto when we feel safe.

    by dexterlagan
  • my opinion: "trust" is an interesting word to use for a piece of closed source probabilistic software that changes daily (sometimes multiple times), whose lead dev reports they rewrite something like 90% ("almost all", I believe, from recent interview) of the codebase after every new model release
    by mccoyb
  • Doesn't auto mode also auto-accept code changes? Assuming their data is good, I'd be fine trying an auto mode for permission prompts (as the article says, I do eventually get prompt fatigue and stop examining them too deeply). But I absolutely don't want it changing code without my permission.
    by kelnos
  • Most users of coding agents do want the agent to edit their code, and don't want to have to click something before every edit. If you want something different, that's why it's a setting.
    by ameliaquining
  • It will indeed change code. It will also happily do stuff like write into your user's SSH config and leave you with permanently broken SSH until you find and fix it.
    by graceful6800
  • https://xcancel.com/ClaudeDevs/status/2085794862608318627
    by bigwheels
  • Announcement post is https://claude.com/blog/auto-mode-default-in-claude-code, link should probably point there instead of the tweet.
    by ameliaquining
  • "Auto mode runs a classifier on every tool call, which uses a small number of extra tokens.

    As of today, that classifier overhead no longer counts toward your usage limits on Pro, Max, and Team plans. This change will come to Enterprise plans and API users once auto mode is the default for those users, too"

    That seems like a good change if making this the default.

    by Computer0
  • The majority of the times I reject a tool call it's because I can tell the agent is about to go off piste. Eg. adding packages to work around some non-problem is a common one.

    I guess I could try to actively interrupt it in those moments, but that seems less effective.

    More power to those who want to use it like that though, I guess. Perhaps by throwing in extra agentic guardrails, or whatever the idea may be. I don't think it's the best route to a good product or business but let's see.

    by jddj
  • This is a sensible choice.

    Their newer models are heavily trained out of the "whoopsie doopsie I deleted prod, and all backups too" behaviour from last year.

    I've been running it for months in auto mode, heavily, getting it to do sysadmin tasks via SSH across multiple servers for both myself and a client, and there's not even been a whiff of anything dumb/catastrophic -quite the opposite, in fact.

    I'd even say it's more careful than a lot of humans. It's extremely anal about standard "hygiene" stuff like not leaving plaintext secrets lying around, and creating post-deploy scripts to confirm that every file/dir is created with the correct permissions.

    There was one time I carelessly suggested uploading (my own) private data to a random public endpoint when testing OCR options and the model actually stopped, explained the risks and refused to continue until I confirmed I understood. I decided not to.

    I'm not saying it's perfect, and I'm sure HN being HN there'll be someone who responds with an example of their agent doing something dumb/dangerous (give dates/models/context if so, I'm curious!), but I think on balance it's currently more sensible, and more cybersecurity-minded than the bottom 80% of IT professionals.

    This is all true for Claude, I don't know much about Codex but it seems a lot less heavily trained for this kind of stuff.

    by AussieWog93
  • On the dumb side, I think this was 6 August and Opus 5 (though there's a chance it was Opus 4.8), Auto Mode was copying some files into a folder on my machine, and had written a small script to do so: one of those $SRC / $DST situations. And of course, the inevitable happened - it never set $SRC in the bash script, and started copying from the root of my filesystem instead. I'm not sure how I caught it, but I came back to one of those Claude "I need to be honest with you — I caused I problem that I need to clean up" situations.

    It wasn't dire, no data loss (just a nasty cleanup) and Auto Mode has mostly made me more productive - I can finally walk away from the screen for long periods of time and do other things. But I need to watch what the model is doing... which is the exact opposite of what I just typed.

    Honestly, I've actually just downgraded my Claude and started looking for other options. The content filters on American models are now actively interfering with my everyday work, so I think it's time I try the Chinese models more deliberately, now that Kimi & Qwen have caught up to the US.

    by SyneRyder
  • Yeah nah, one of my coworkers was building stuff via TDD yesterday and Claude Code ended up running a test that ran `rm -rf` on his home directory. So dumb shit like this does still happen.
    by sevenseacat
  • I don't disagree with anything you said here, but I find auto-mode is too permissive on the reading side of things.

    I used Claude this morning to convert the financial books for my nonprofit from some export of a proprietary software (Aplos) to plaintext accounting (Beancount), and was surprised to find it had found my personal Beancount ledger elsewhere on my hard drive and modelled its plan on that. That was correct and helpful, but a bit of an overreach in my opinion, enough that I'll be sandboxing agents (with tools like nono, smolmachines, etc) going forward.

    by abound