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

531–540 of 593 posts

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

#531

Post by lossyalgo »

raptorraver wrote: post #506
itake wrote: post #419

Earlier quoted context omitted.

"Move fast and break things" I could spend an extra 5 minutes doing it "right" or I can get what I need done and have a 0.001% chance of there ever being a problem (since there are other security measure in place, like firewalls, api key rotation, etc.) Even when security gaps are exploited, the fallout tends to be minimal. Companies that had their entire database of very sensitive information leaked are still growin…

> Companies that had their entire database of very sensitive information leaked are still growing users and at worst paid a tiny fine. Or end up bankrupt with criminal charges for CEO: https://yle.fi/a/74-20027665

Bankrupt? I didn't read about any financial penalties in that article. The board fired him back in 2020 when they found out, and then he blamed 2 IT people. Instead, he got 3 months suspended sentence (in a Finnish jail, which is not exactly like a US jail). The company still exists btw.

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

#532

Post by lossyalgo »

falloutx wrote: post #83
exitb wrote: post #15

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.

Now they can start saying 90% of the meetings will be done by Claude agents by 2027 (And we will all get free puppies)

We won't even need to have meetings (or managers) in this happy AI future, because AI agents will be doing everything, so we can all sit at home watching TV because UBI will become mandatory (I hope you are right about puppies but somehow I think we will become the puppies in some sick and twisted Hunger Games episode).

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

#533

Post by scottLobster »

Yeah, unless there's some automatic backup/snapshot implemented before any actions are taken, hard pass on this. Or at least I won't be using it on anything I'm not willing to 100% lose. Maybe give it read-only access and have it put results in a designated output folder?

Particularly in a work environment, one misfire could destroy months or years of important information.

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

#534

Post by bheadmaster »

scottLobster wrote: post #533

Yeah, unless there's some automatic backup/snapshot implemented before any actions are taken, hard pass on this. Or at least I won't be using it on anything I'm not willing to 100% lose. Maybe give it read-only access and have it put results in a designated output folder? Particularly in a work environment, one misfire could destroy months or years of important information.

It's funny how easy Plan 9 would make all this. Just mount the work dir as readonly in Cowork's filesystem namespace and mount a write-only dir for output.

We can still do this via containers, though. But it does have some friction.

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

#535

Post by k-o-n-t-o-r »

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

Might be useful for testing the DNS vector:

https://github.com/k-o-n-t-o-r/dnsm

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

#536

Post by TeMPOraL »

aroman wrote: post #433
TeMPOraL wrote: post #356

Earlier quoted context omitted.

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

> the models are close to being able to destroy the entire software industry Are you saying this based on some insider knowledge of models being dramatically more capable internally, yet deliberately nerfed in their commercialized versions? Because I use the publicly available paid SOTA models every day and I certainly do not get the sense that their impact on the software industry is being restrained by deliberate c…

I don't mean the companies are hoarding more powerful models (competition prevents that) - just that the existing models already make it too easy for individuals and companies to build and maintain ad-hoc, problem-specific versions of many commercial software services they now pay for. This is the source of people asking, why haven't AI companies themselves done this to a good chunk of software world. One hypothesis is that they're all gathering data from everyone using LLMs to power their business, in order to do just that. My alternative hypothesis is that they already could start burning through the industry, competing with whole classes of existing products and services, but they purposefully don't, because charging rent from existing players is more profitable than outcompeting them.

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

#539

Post by tstrimple »

Wowfunhappy wrote: post #122
ElatedOwl wrote: post #13

Earlier quoted context omitted.

I keep seeing “Claude image understanding is poor” being repeated, but I’ve experienced the opposite. I was running some sentiment analysis experiments; describe the subject and the subjects emotional state kind of thing. It picked up on a lot of little detail; the brand name of my guitar amplifier in the background, what my t shirt said and that I must enjoy craft beer and or running (it was a craft beer 5k kind of…

I regularly show Claude Code a screenshot of a completely broken UI--lots of cut off text, overlapping elements all over the place, the works--and Claude will reply something like "Perfect! The screenshot shows that XYZ is working." I can describe what is wrong with the screenshot to make Claude fix the problem, but it's not entirely clear to what extent it's using the screenshot versus my description. Any human with…

This is my experience as well. If CC does something, and I get broken results and reply with just an image it will almost always reply with "X is working!" response. Sometimes just telling it to look more closely is enough, or sometimes I have to be more specific. It seems to be able to read text from screenshots of logs just fine though and always seems to process those as I'd expect.
Post reply on HN