kumar_abhirup
Joined 6 years ago
Joined 6 years ago
Now instead of bundling and patching from inside it, we just ship alongside OpenClaw so you can use the latest OpenClaw CLI separately yourself.
Telling DenchClaw to "make it less robotic" on 300+ personalised drafts is still better than me actually making it less robotic myself imo
Responding to some HN comments, I understand the focus on Sales Automation and Outreach can be worrysome.
But for me personally, this is where I do all knowledge work. For me it acts like Cursor, Happenstance, News Aggregator, Fun games creator like Pacman (it has an App Store), I can import Notion into editable MD files, create reports and presentations, etc.
Ideally for these pursposes, I would ALWAYS use Claude Opus 4.6 for this stuff, personally I have never seen it do unintended things to that extent.
Also, when the browser opens you can supervise it doing the thing, since you can see what its doing, you can always stop it if it ever goes wrong.
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.
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.
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.