I 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-…
Cowork: Claude Code for the rest of your work
101–110 of 593 posts
Re: Cowork: Claude Code for the rest of your work
#102Hi, Felix from the team here, this is my product - let us know what you think. We're on purpose releasing this very early, we expect to rapidly iterate on it. (We're also battling an unrelated Opus 4.5 inference incident right now, so you might not see Cowork in your client right away.)
Deleting vm_bundles lets me open Claude Desktop and switch tabs. Then it hangs again, I delete vm_bundles again, and open it again. This time it opens on the Chat tab and I know not to click the Cowork tab...
Re: Cowork: Claude Code for the rest of your work
#103It's so important to remember that unlike code which can be reverted - most file system and application operations cannot. There's no sandboxing snapshot in revision history, rollbacks, or anything. I expect to see many stories from parents, non-technical colleagues, and students who irreparably ruined their computer. Edit: most comments are focused on pointing out that version control & file system snapshot exists:…
[1]: https://eclecticlight.co/2024/04/08/apfs-snapshots/
[2]: https://eclecticlight.co/2021/09/04/explainer-the-macos-vers...
Re: Cowork: Claude Code for the rest of your work
#104Hi, Felix from the team here, this is my product - let us know what you think. We're on purpose releasing this very early, we expect to rapidly iterate on it. (We're also battling an unrelated Opus 4.5 inference incident right now, so you might not see Cowork in your client right away.)
Re: Cowork: Claude Code for the rest of your work
#105Hi, Felix from the team here, this is my product - let us know what you think. We're on purpose releasing this very early, we expect to rapidly iterate on it. (We're also battling an unrelated Opus 4.5 inference incident right now, so you might not see Cowork in your client right away.)
However, I don't see an option for AWS Bedrock API in the sign up form, is it planned to make this available to those using Bedrock API to access Claude models?
Re: Cowork: Claude Code for the rest of your work
#106Re: Cowork: Claude Code for the rest of your work
#107Re: Cowork: Claude Code for the rest of your work
#108Earlier 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.
Everything on a ZFS/BTRFS partition with snapshots every minute/hour/day? I suppose depending on what level of access the AI has it could wipe that too but seems like there's probably a way to make this work.
Re: Cowork: Claude Code for the rest of your work
#109Earlier quoted context omitted.
Have you ever used any Anthropic AI product? You cannot literally do anything without big permissions, warnings, or annoying always-on popup warning you about safety.
No, of course not. Well.. apart from their API. That is a useful thing. But you're missing the point. It is doing all this stuff with user consent, yes. It's just that the user fundamentally cannot provide informed consent as they seem to be out of their minds. So yeah, technically, all those compliance checkboxes are ticked. That's just entirely irrelevant to the point I am making.
The user is an adult. They are capable of consenting to whatever they want, no matter how irrational it may look to you.
Re: Cowork: Claude Code for the rest of your work
#110Earlier quoted context omitted.
Q: What would prevent them from using git style version control under the hood? User doesn’t have to understand git, Claude can use it for its own purposes.
You can’t easily snapshot the current state of an OS and restore to that state like with git.