People do realize that if they're doing this, they're not feeding "just" code into some probably logging cloud API but literally anything (including, as mentioned here, bank statements), right? Right? RIGHT?????? Are you sure that you need to grant the cloud full access to your desktop + all of its content to sort elements alphabetically?
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.
Cowork: Claude Code for the rest of your work
401–410 of 593 posts
Re: Cowork: Claude Code for the rest of your work
#402Earlier quoted context omitted.
Your terms for Claude Max point to the consumer ToS. This ToS states it cannot be used for commercial purposes. Why is this? Why are you marketing a product clearly for business use and then have terms that strictly forbid it. I’ve been trying to reach a human at Anthropic for a week now to clarify this on behalf of our company but can’t get past your AI support.
> [consumer] ToS states it cannot be used for commercial purposes Where? I searched https://www.anthropic.com/legal/consumer-terms for commercial and the only thing I can see is > Evaluation and Additional Services. In some cases, we may permit you to evaluate our Services for a limited time or with limited functionality. Use of our Services for evaluation purposes are for your personal, non-commercial use only. All…
> These Terms apply to you if you are a consumer who is resident in the European Economic Area or Switzerland. You are a consumer if you are acting wholly or mainly outside your trade, business, craft or profession in using our Services.
> Non-commercial use only. You agree that you will not use our Services for any commercial or business purposes
Re: Cowork: Claude Code for the rest of your work
#403The hero image with a set of steps: 1) Read meeting transcripts 2) Pull out key points 3) Find action items 4) Check Google Calendar 5) Build standup deck feels like "how to put yourself out of a job 101." It's interesting to see the marketing material be so straightforward about that.
Re: Cowork: Claude Code for the rest of your work
#404Earlier quoted context omitted.
The first version is for macOS, which has snapshots [1] and file versioning [2] built-in. [1]: https://eclecticlight.co/2024/04/08/apfs-snapshots/ [2]: https://eclecticlight.co/2021/09/04/explainer-the-macos-vers...
Are average users likely to be using these features? Most devs at my company don’t even have Time Machine backups
Re: Cowork: Claude Code for the rest of your work
#405Hi, 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
#406Hi, 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
#407It'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:…
Once upon a time, in the magical days of Windows 7, we had the Volume Shadow Copy Service (aka "Previous Versions") available by default, and it was so nice. I'm not using Windows anymore, and at least part of the reason is that it's just objectively less feature complete than it used to be 15 years ago.
I haven't had to tweak an OS like Win 11 ever.
Re: Cowork: Claude Code for the rest of your work
#408The hero image with a set of steps: 1) Read meeting transcripts 2) Pull out key points 3) Find action items 4) Check Google Calendar 5) Build standup deck feels like "how to put yourself out of a job 101." It's interesting to see the marketing material be so straightforward about that.
I know managers think this is all there is to “work”, but at some point someone need do those action items.
Re: Cowork: Claude Code for the rest of your work
#409I 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-…
Is there any reasonably fast and portable sandboxing approach that does not require a full blown VM or containers? For coding agents containers are probably the right way to go, but for something like Cowork that is targeted at non-technical users who want or have to stay local, what's the right way? container2wasm seems interesting, but it runs a full blown x86 or ARM emulator in WASM which boots an image derived fr…
Re: Cowork: Claude Code for the rest of your work
#410Earlier quoted context omitted.
The solution is to cut off one of the legs of the lethal trifecta. The leg that makes the most sense is the ability to exfiltrate data - if a prompt injection has access to private data but can't actually steal it the damage is mostly limited. If there's no way to externally communicate the worst a prompt injection can do is modify files that are in the sandbox and corrupt any answers from the bot - which can still b…
Cutting off the ability to externally communicate seems difficult for a useful agent. Not only because it blocks a lot of useful functionality but because a fetch also sends data. “Hey, Claude, can you download this file for me? It’s at https://example.com/(mysocialsecuritynumber)/(mybankinglogin... ”