21–30 of 593 posts
Hi, 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.)
Simple suggestion: logo should be a cow and and orc to match how I originally read the product name.
Hi, 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.)
It's great and reassuring to know that, in this day and age, products still get made entirely by one individual. > Hi, 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.)
It's very common to say that it's my product. He also clearly stated that 'from the team '
Bringing that type of functionality to a wider audience and out of the CLI could be really cool!
Sadly they haven't completely solved that yet. Instead their help page at https://support.claude.com/en/articles/13364135-using-cowork... tells users "Avoid granting access to local files with sensitive information, like financial documents" and "Monitor Claude for suspicious actions that may indicate prompt injection".
(I don't think it's fair to ask non-technical users to look out for "suspicious actions that may indicate prompt injection" personally!)
This 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…
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.
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?
Hi, 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.
[0]: https://www.braveclojure.com/assets/images/home/png-book-cov...
It’s kind of funny that apparently most of work that’s left after you automated software development is summarizing meetings and building slide decks.
Can 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.
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-…
