Telling DenchClaw to "make it less robotic" on 300+ personalised drafts is still better than me actually making it less robotic myself imo

Yesterday I asked it to pull up all my meeting notes from last week, cross-reference them with my task list, and draft follow-ups. Before that I had it reorganize a messy folder of research PDFs into a structured workspace. I use it to build slides, write code (DenchClaw literally built DenchClaw), manage my calendar, search through old Notion pages I forgot existed.

The CRM part gets attention because that's what people asked for when we talked to power users. But the actual product is just "OpenClaw with a good UI, a file system, and DuckDB, running locally on your Mac." It does whatever you'd normally do on your computer. The browser is yours, the files are yours, the data never leaves your machine.

Think of it less as a sales tool and more as what happens when your entire Mac becomes programmable through natural language. The CRM is one app that runs on top of that. People are already using it for project management, research, personal knowledge bases, all kinds of stuff we didn't plan for.

Thanks for sharing.

Yesterday I asked it to pull up all my meeting notes from last week, cross-reference them with my task list, and draft follow-ups. Before that I had it reorganize a messy folder of research PDFs into a structured workspace. I use it to build slides, write code (DenchClaw literally built DenchClaw), manage my calendar, search through old Notion pages I forgot existed.

The CRM part gets attention because that's what people asked for when we talked to power users. But the actual product is just "OpenClaw with a good UI, a file system, and DuckDB, running locally on your Mac." It does whatever you'd normally do on your computer. The browser is yours, the files are yours, the data never leaves your machine.

Think of it less as a sales tool and more as what happens when your entire Mac becomes programmable through natural language. The CRM is one app that runs on top of that. People are already using it for project management, research, personal knowledge bases, all kinds of stuff we didn't plan for.

We're going to need local AI to sift through the trash. Platforms have been more or less useless at curating content, and it's only smaller sites like HN that have retained a high SNR at this point. It doesn't even matter what media, at this point, video has passed the 2-3 second sniff test. We're seeing boomers get completely sniped by AI videos, even with watermark, showing absurd spin on current events. Text, music, podcasts, video, cartoons, whatever, it's all been infested, and the quality keeps increasing. I've seen a couple 2+ minute seedance productions that have been actually enjoyable, but by June that sort of thing will be one-shot prompting instead of someone gluing together the outputs from 4 difference SoTA AI tools.

It's getting weird, and we're not ready for it, at all.

Wow that sounds great. Hey don't worry these things never blackmail anyone. Let it know if you're gonna turn it off, I bet it'll make some REAL interesting choices based on your browsing history

They could've released something like that years ago (the discovery service it's built on has existed for over a decade) but creating a simple, accessible, unified CLI for general integration apparently wasn't worth it until agents became the hot thing.

I wonder when / if there will be a rug pull on all of this. Because I really don't see what the long-term incentives are for incumbent tech platforms to make it easy for automated systems to essentially pull users away from the actual platform. I guess they're focused on the short term incentives. And once they decide the party's over, promising upstarts and competition can get absorbed and it'll be business as usual. Idk, we'll see.

For the DuckDB side specifically: we shell out to the duckdb CLI binary for every query rather than embedding it in the Node process. So each operation gets its own memory space and dies when it's done. the web server at localhost:3100 stays lean regardless of what you're ingesting. DuckDB's out-of-core execution also means it can handle datasets larger than available RAM natively, which is one of the reasons we picked it over SQLite.

For really large exports (think full HubSpot instance with 100k+ contacts), the practical limit is more about the browser export step than DuckDB. HubSpot itself chunks its exports, and we process those chunks as they land. The DuckDB insert is the fast part.

Honestly for CRM-scale data, even a large sales org's full HubSpot, DuckDB eats it for breakfast. Where it would get interesting is if someone tries to throw analytics-scale data at it, but that's not really the use case. Would love to hear how IndexedDB holds up for you at scale in AccIQ, different trade-offs for sure.