Cowork: Claude Code for the rest of your work

Post by lijok » Mon, Jan 12, 2026, 11:38 PM UTC

soiltype wrote: post #252

Workaccount2 wrote: post #152

Earlier quoted context omitted.

Frequency vs. convenience will determine how big of a deal this is in practice. Cars have plenty of horror stories associated with them, but convenience keeps most people happily driving everyday without a second thought. Google can quarantine your life with an account ban, but plenty of people still use gmail for everything despite the stories. So even if Claude cowork can go off the rails and turn your digital life…

Considering the ubiquity and necessity of driving cars is overwhelmingly a result of intentional policy choices irrespective of what people wanted or was good for the public interest... actually that's quite a decent analogy for integrated LLM assistants. People will use AI because other options keep getting worse and because it keeps getting harder to avoid using it. I don't think it's fair to characterize that as c…

Post by l9o » Mon, Jan 12, 2026, 11:42 PM UTC

felixrieseberg wrote: post #147

simonw wrote: post #24

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-…

Worth calling out that execution runs in a full virtual machine with only user-selected folders mounted in. CC itself runs, if the user set network rules, with https://github.com/anthropic-experimental/sandbox-runtime . There is much more to do - and our docs reflect how early this is - but we're investing in making progress towards something that's "safe".

Post by simonw » Mon, Jan 12, 2026, 11:44 PM UTC

l9o wrote: post #273

felixrieseberg wrote: post #147

Earlier quoted context omitted.

Worth calling out that execution runs in a full virtual machine with only user-selected folders mounted in. CC itself runs, if the user set network rules, with https://github.com/anthropic-experimental/sandbox-runtime . There is much more to do - and our docs reflect how early this is - but we're investing in making progress towards something that's "safe".

Is it really a VM? I thought CC’s sandbox was based on bubblewrap/seatbelt which don’t use hardware virtualization and share the host OS kernel?

Post by re5i5tor » Mon, Jan 12, 2026, 11:50 PM UTC

oracleclyde wrote: post #142

Flux159 wrote: post #4

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…

Maybe at one time, but it absolutely understands images now. In VSCode Copilot, I am working on a python app that generates mesh files that are imported in a blender project. I can take a screenshot of what the mesh file looks like and ask Claude code questions about the object, in context of a Blender file. It even built a test script that would generate the mesh and import it into the Blender project, and render a…

Post by akurilin » Tue, Jan 13, 2026, 12:01 AM UTC

alexdobrenko wrote: post #268

I've been using Claude Code in my terminal like a feral animal for months. Building weird stuff. Breaking things. Figuring it out as I go. Cowork is the nice version. The "here's a safe folder for Claude to play in" version. Which is great! Genuinely. More people should try this. But!!! The terminal lets you do more. It always will. That's just how it works. And when Cowork catches up, you'll want to go further. The…