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.)
What probability would you give for Linux support for Claude Desktop in 2026?
Cowork: Claude Code for the rest of your work
291–300 of 593 posts
Re: Cowork: Claude Code for the rest of your work
#292Basic ideas are minimal privilege per task in a minimal and contained environment for everything and heavy control over all actions AI is performing. AI can performs tasks without seeing any of your personal information in the process. A new kind of orchestration and privacy layer for zero trust agentic actions.
Redactsure.com
From this feed I figured I'd plug my system, would love your feedback! I beleive we are building out a real solution to these security and privacy concerns.
While the entire field is early I do believe systems like my own and others will make these products safe and reliable in the near future.
Re: Cowork: Claude Code for the rest of your work
#293Earlier quoted context omitted.
Sorry not related - your blog is awesome. Cool to see you here on HN!
I'm starting to suspect some of these comments might be AI generated and it is all an experiment. guy is the top comment in every other HN thread.
Re: Cowork: Claude Code for the rest of your work
#294Earlier quoted context omitted.
It's kind of wild how dangerous these things are and how easily they could slip into your life without you knowing it. Imagine downloading some high-interest document stashes from the web (like the Epstein files), tax guidance, and docs posted to your HOA's Facebook. An attacker could hide a prompt injection attack in the PDFs as white text, or in the middle of a random .txt file that's stuffed with highly grepped wo…
The only truly secure computer is an air gapped computer.
Re: Cowork: Claude Code for the rest of your work
#295I 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-…
Re: Cowork: Claude Code for the rest of your work
#296Earlier quoted context omitted.
Operating systems should prevent privilege escalations, antiviruses should detect viruses, police should catch criminals, claude should detect prompt injections, ponies should vomit rainbows.
I don't think those are all equivalent. It's not plausible to have an antivirus that protects against unknown viruses. It's necessarily reactive. But you could totally have a tool that lets you use Claude to interrogate and organize local documents but inside a firewalled sandbox that is only able to connect to the official API. Or like how FIDO2 and passkeys make it so we don't really have to worry about users typin…
Re: Cowork: Claude Code for the rest of your work
#297It'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?
Reality is good ideas and a few SOPs do not make a successful business.
Re: Cowork: Claude Code for the rest of your work
#298Earlier 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.
Didn't actually check out the app, but some aspects of application state are hard to serialize, some operations are not reversible by the application. EG: sending an email. It doesn't seem naively trivial to accomplish this, for all apps. So maybe on some apps, but "all" is a difficult thing.
Re: Cowork: Claude Code for the rest of your work
#299It'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:…
TimeMachine has never been so important.