Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Cowork: Claude Code for the rest of your work

claude.com

Post reply on HN
Print view View original

391–400 of 593 posts

Re: Cowork: Claude Code for the rest of your work

#391

Post by Davidzheng »

TeMPOraL wrote: post #356
xlbuttplug2 wrote: post #162

Earlier quoted context omitted.

> They can and most likely will release something that vaporises the thin moat you have built around their product. As they should if they're doing most of the heavy lifting. And it's not just LLM adjacent startups at risk. LLMs have enabled any random person with a claude code subscription to pole vault over your drying up moat over the course of a weekend.

LLMs by their very nature subsume software products (and services). LLM vendors are actually quite restrained - the models are close to being able to destroy the entire software industry (and I believe they will, eventually). However, at the moment, it's much more convenient to let the status quo continue, and just milk the entire industry via paid APIs and subscriptions, rather than compete with it across the board.…

I think the function of a company is to address limitations of a single human by distributing a task across different people and stabilized with some bureaucracy. However, if we can train models past human scales at corporation scale, there might be large efficiency gains when the entire corporation can function literally as a single organism instead of coordinating separate entities. I think the impact of this phase of AI will be really big.

Re: Cowork: Claude Code for the rest of your work

#392

Post by mhitza »

oblio wrote: post #53
seunosewa wrote: post #46

Earlier quoted context omitted.

There's no reason why Claude can't use git to manage the folders that it controls.

Git isn't good with big files. I wanted to comment more, but this new tool is Mac only for now, so there isn't much of a point.

Too hard for AI to make crossplatform tools.

Re: Cowork: Claude Code for the rest of your work

#393

Post by incr_me »

nikkwong wrote: post #58
toddmorey wrote: post #50

Earlier 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.

You can’t easily snapshot the current state of an OS and restore to that state like with git.

Let's assume that you can. For disaster recovery, this is probably acceptable, but it's unacceptable for basically any other purpose. Reverting the whole state of the machine because the AI agent (a single tenant in what is effectively a multi-tenant system) did something thing incorrect is unacceptable. Managing undo/redo in a multiplayer environment is horrific.

Re: Cowork: Claude Code for the rest of your work

#394

Post by __MatrixMan__ »

jryio wrote: post #36

It'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:…

I hope we see further exploration into immutable/versioned filesystems and databases where we can really let these things go nuts, commit the parts we want to keep, and revert the rest for the next iteration.

Re: Cowork: Claude Code for the rest of your work

#395

Post by catoc »

sureglymop wrote: post #138
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-…

That's one thing. Another would be introducing homomorphic encryption in order for companies and people using their models to stay compliant and private. I can't believe it's such an under-researched area in AI.

That is the only implementation I can think of that might make me trust a third party with confidential data. Of course these massive transformers are already insanely computer intensive and adding FHE would make that orders of magnitude worse.

Re: Cowork: Claude Code for the rest of your work

#397

Post by LeafItAlone »

motoboi wrote: post #206
hypfer wrote: post #26

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?

I have my bank statements on a drive on a cloud. We are way past that phase.

What! How can you be so insecure with your data?! You’re willing to upload a file you downloaded from a cloud service to a different cloud service? The horror!!

This is exactly what I expect out of…

Sorry, got interrupted by an email saying my bank was involved in a security incident.

Re: Cowork: Claude Code for the rest of your work

#400

Post by catoc »

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".

According to Anthropic’s privacy policy you collect my “Inputs” and “If you include personal data … in your Inputs, we will collect that information”

Do all files accessed in mounted folders now fall under collectable “Inputs” ?

Ref: https://www.anthropic.com/legal/privacy

Post reply on HN