YMMV but TFA page content body didn’t render for me until I disabled my local pihole.
Cowork: Claude Code for the rest of your work
31–40 of 593 posts
Re: Cowork: Claude Code for the rest of your work
#32It's really quite amazing that people would actually hook an AI company up to data that actually matters. I mean, we all know that they're only doing this to build a training data set to put your business out of business and capture all the value for themselves, right?
Re: Cowork: Claude Code for the rest of your work
#33Hi, 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.)
Hi Felix! Simple suggestion: logo should be a cow and and orc to match how I originally read the product name.
OK I couldn't resist that one: https://gist.github.com/simonw/d06dec3d62dee28f2bd993eb78beb...
Re: Cowork: Claude Code for the rest of your work
#34This looks pretty cool. I keep seeing people (an am myself) using claude code for more an more _non-dev_ work. Managing different aspects of life, work, etc. Anthropic has built the best harness right now. Building out the UI makes sense to get genpop adoption
Yeah, the harness quality matters a lot. We're seeing the same pattern at Gobii - started building browser-native agents and quickly realized most of the interesting workflows aren't "code this feature" but "navigate this nightmare enterprise SaaS and do the thing I actually need done." The gap between what devs use Claude Code for vs. what everyone else needs is mostly just the interface.
Re: Cowork: Claude Code for the rest of your work
#35I 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-…
I do get a "Setting up Claude's workspace" when opening it for the first time - it appears that this does do some kind of sandboxing (shared directories are mounted in).
It looks like they have a sandbox around file access - which is great! - but the problem remains that if you grant access to a file and then get hit by malicious instructions from somewhere those instructions may still be able to steal that file.
Re: Cowork: Claude Code for the rest of your work
#36It'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: that's wonderful, but Claude Cowork does not use it.
For those of us who have built real systems at low levels I think the alarm bells go off seeing a tool like this - particularly one targeted at non-technical users
Re: Cowork: Claude Code for the rest of your work
#37It's a little funny how the "Stay in control" section is mostly about how quickly you can lose control (deleting files, prompt injections). I can foresee non-technical users giving access to unfortunate folders and getting into a lot of trouble.
Re: Cowork: Claude Code for the rest of your work
#38Can humans do nothing now? Is it harder to organise your desktop? I thought Apple already organises them into stacks. (edit: Apple already does this) Is it that hard to check your calendar? Also feels insincere to have a meeting of say 30 mins to show a claude made deck that you did it in 4 seconds.
You can still do all these things manually. Now you just have the option not to.
The example they show (desktop organisation) is already automated free of charge, without user action.
Re: Cowork: Claude Code for the rest of your work
#39This looks useful for people not using Claude Code, but I do think that the desktop example in the video could be a bit misleading (particularly for non-developers) - Claude is definitely not taking screenshots of that desktop & organizing, it's using normal file management cli tools. The reason seems a bit obvious - it's much easier to read file names, types, etc. via an "ls" than try to infer via an image. But it a…
Claude Opus 4.5 can understand images: one thing I've done frequently in Claude Code and have had great success is just showing it an image of weird visual behavior (drag and drop into CC) and it finds the bug near-immediately. The issue is that Claude Code won't automatically Read images by default as a part of its flow: you have to very explicitly prompt it to do so. I suspect a Skill may be more useful here.
I've done similar while debugging an iOS app I've been working on this past year.
Occasionally it needs some poking and prodding but not to a substantial degree.
I also was able to use it to generate SVG files based on in-app design using screenshots and code that handles rendering the UI and it was able to do a decent job. Granted not the most complex of SVG but the process worked.
Re: Cowork: Claude Code for the rest of your work
#40[deleted]