Funny timing. Written in 10 days just when this took off. https://clawd.bot/
Cowork: Claude Code for the rest of your work
341–350 of 593 posts
Re: Cowork: Claude Code for the rest of your work
#342It'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:…
There was a couple of posts here on hacker news praising agents because, it seems, they are really good at being a sysadmin. You don't need to be a non-technical user to be utterly fucked by AI.
Theoretically, the power drill you're using can spontaneously explode, too. It's very unlikely, but possible - and then it's much more likely you'll hurt yourself or destroy your work if you aren't being careful and didn't set your work environment right.
The key for using AI for sysadmin is the same as with operating a power drill: pay at least minimum attention, and arrange things so in the event of a problem, you can easily recover from the damage.
Re: Cowork: Claude Code for the rest of your work
#343This product barely works. It can't connect to the browser extension and when I share folders for it to access, nothing happens. I love early previews but maybe one more week?
Re: Cowork: Claude Code for the rest of your work
#344Earlier quoted context omitted.
Some do, some don't. The reality is there are some of us who truly just don't care. The convenience outweighs the negative. Yesterday I told an agent, "here's my api key and my root password - do it for me". Privacy has long since been dead, but at least for myself opsec for personal work is too.
> Privacy has long since been dead, but at least for myself opsec for personal work is too. Hacker News in 2026.
Paranoia is justified if it actually serves some purpose. Staying paralyzed and not doing anything because Someone Is Reading Your Data is not serving much of anything. Hint: those Someones have better things to do. LLM vendors really don't care about your bank statements, and if they were ever in a position to look, they'd prefer not to have them, as it just creates legal and reputational risks for them.
Re: Cowork: Claude Code for the rest of your work
#345People 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?
When choosing between convenience and privacy, most people seem to choose convenience
Obviously. Those who chose otherwise have all died out long ago, starving to death in their own apartments, afraid that someone might see them if they ever went outside.
Re: Cowork: Claude Code for the rest of your work
#346A CLI chat interface seems ideal for when you keep code "at a distance", i.e. if you hardly/infrequently/never want to peek at your code. But for writing prose, I don't think chat-to-prose is ideal, i.e. most people would not want the keep prose "at a distance". I bet most people want to be immersed in an editor where they are seeing how the text is evolving. Something like Zed's inline assistant, which I found mysel…
I agree that for writing documents and for a lot of other things like editing csv files or mockups, I want to be immersed in the editor together with Claude Code, not in a chat separated from my editors
I was hoping that zed’s inline assistant could make use of the CC subscription but sadly not; you have to pay for metered API usage.
But for simple writing tasks, I hooked up Zed’s inline assistant to use Qwen3-30B-A3B running on my Mac via llama-server, and it works surprisingly well.
Re: Cowork: Claude Code for the rest of your work
#347It'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?
> I mean, we all know that they're only doing this to build a training data set
That's not a problem. It leads to better models.
> to put your business out of business and capture all the value for themselves, right?
That's both true and paranoid. Yes, LLMs subsume most of the software industry, and many things downstream of it. There's little anyone can do about it; this is what happens when someone invents a brain on a chip. But no, LLM vendors aren't gunning for your business. They neither care, nor have the capability to perform if they did.
In fact my prediction is that LLM vendors will refrain from cannibalizing distinct businesses for as long as they can - because as long as they just offer API services (broad as they may be), they can charge rent from an increasingly large amount of the software industry. It's a goose that lays golden eggs - makes sense to keep it alive for as long as possible.
Re: Cowork: Claude Code for the rest of your work
#348Cowork + litellm proxy + a local vision LLM should work incredibly well for overnight organizing tasks organizing md files, photos etc.
Re: Cowork: Claude Code for the rest of your work
#349Earlier quoted context omitted.
> Privacy has long since been dead, but at least for myself opsec for personal work is too. Hacker News in 2026.
Paranoia is justified if it actually serves some purpose. Staying paralyzed and not doing anything because Someone Is Reading Your Data is not serving much of anything. Hint: those Someones have better things to do. LLM vendors really don't care about your bank statements, and if they were ever in a position to look, they'd prefer not to have them, as it just creates legal and reputational risks for them.
> as it just creates legal and reputational risks for them.
Unfortunately I laughed reading this as there is never neither reputation nor legal consequences in the US of A. They can leak your entire life into my console including every account and every password you have and all PII of your entire family and literally nothing would happen… everything is stored somewhere and eventually will be used when “growth” is needed. some meaningless fines will be paid here and there but those bank statements will make their way to myriad of business that would drool to see them
Re: Cowork: Claude Code for the rest of your work
#350Earlier quoted context omitted.
I did get an answer from a senior executive at one AI lab who called this the "regurgitation problem" and said that they pay very close attention to it, to the point that they won't ship model improvements if they are demonstrated to cause this.
Lol and that was enough for you? You really think they can test every single prompt before release to see if it regurgitates stuff? Did this exec work in sales too :-D
They have a clear incentive to do exactly as said - regurgitation is a problem, because it indicates the model failed to learn from the data, and merely memorized it.