Live data from Hacker News

Clawdbot - open source personal AI assistant

github.com

51–60 of 274 posts

Re: Clawdbot - open source personal AI assistant

#51

something feels off to me about the clawdbot hype About the maintainer's github: 688 commits on Nov 25, 2025... out of which 296 commits were in clawdbot, IN ONE DAY, he prolly let lose an agent on the project for a few hours... he has more than 200 commits on an average per day, but mostly 400-500 commits per day, and people are still using this project without thinking of the repercussions) Now, something else i re…

It seems wildly trivial. Chat completion loop with toolcalling over a universal chat gateway. What's the innovation here? Local model? That was always possible. Toolcalling? Been around a couple years now... It's like 5 minutes of vibe coding at most. There's likely 1,000s of similar projects already on GitHub

And when you can use claude-code from basically any device (termux on phone via ssh), Why even bother?

I had 3 friends ping me yesterday to tell me how this is going to eat their job....

but i don't see how this is different from claude-code + some chat interface + mcp servers

Re: Clawdbot - open source personal AI assistant

#52

Clawdbot finally clicked for me this week. I was renting out an apartment and I had it connect to FB messenger, do the initial screening messages and then schedule times for viewings in my calendar. I was approving it's draft messages but starting giving it some automatic responses as well. Overall it did 9/10 on this task with a couple cases where it got confused. This is just scratching the surface but this was som…

i can see some devs using this to automate bumble/tinder as well lmao

Re: Clawdbot - open source personal AI assistant

#53

something feels off to me about the clawdbot hype About the maintainer's github: 688 commits on Nov 25, 2025... out of which 296 commits were in clawdbot, IN ONE DAY, he prolly let lose an agent on the project for a few hours... he has more than 200 commits on an average per day, but mostly 400-500 commits per day, and people are still using this project without thinking of the repercussions) Now, something else i re…

He explicitly disavowed any crypto / coin endorsement (I don't _love_ his vibes on Twitter, but he seems like a very reasonable guy generally, and the project seems awesome)

The project is okay but i don't understand the crazy hype

Re: Clawdbot - open source personal AI assistant

#54

This seems like a nightmare. I wanted to be interested, I'm still interested I guess, but the onboarding experience is just a series of horrible red flags. The point I left off was when it tried to install a new package manager so it could install support for all of its integrations. Hell no.

[deleted]

Re: Clawdbot - open source personal AI assistant

#55

Earlier quoted context omitted.

It seems wildly trivial. Chat completion loop with toolcalling over a universal chat gateway. What's the innovation here? Local model? That was always possible. Toolcalling? Been around a couple years now... It's like 5 minutes of vibe coding at most. There's likely 1,000s of similar projects already on GitHub

And when you can use claude-code from basically any device (termux on phone via ssh), Why even bother? I had 3 friends ping me yesterday to tell me how this is going to eat their job.... but i don't see how this is different from claude-code + some chat interface + mcp servers

The whole world is about bundling (and unbundling).

Not saying it really is useful, but there are values bundling an easier interface to CC with battery included.

Re: Clawdbot - open source personal AI assistant

#56

I ran the install and got these errors: npm warn deprecated npmlog@6.0.2: This package is no longer supported. npm warn deprecated are-we-there-yet@3.0.1: This package is no longer supported. npm warn deprecated gauge@4.0.4: This package is no longer supported. npm warn deprecated tar@6.2.1: Old versions of tar are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the cur…

That's not an error, its an ignorable warning from upstream dependencies

Re: Clawdbot - open source personal AI assistant

#57

Earlier quoted context omitted.

It seems wildly trivial. Chat completion loop with toolcalling over a universal chat gateway. What's the innovation here? Local model? That was always possible. Toolcalling? Been around a couple years now... It's like 5 minutes of vibe coding at most. There's likely 1,000s of similar projects already on GitHub

And when you can use claude-code from basically any device (termux on phone via ssh), Why even bother? I had 3 friends ping me yesterday to tell me how this is going to eat their job.... but i don't see how this is different from claude-code + some chat interface + mcp servers

> termux on phone via ssh

I agree, but it also rhymes a lot with the infamous “why use Dropbox when you can just use rsync” comment. Convenience can be a game changer.

Re: Clawdbot - open source personal AI assistant

#58
post #55

Earlier quoted context omitted.

And when you can use claude-code from basically any device (termux on phone via ssh), Why even bother? I had 3 friends ping me yesterday to tell me how this is going to eat their job.... but i don't see how this is different from claude-code + some chat interface + mcp servers

The whole world is about bundling (and unbundling). Not saying it really is useful, but there are values bundling an easier interface to CC with battery included.

When someone is pushing 500 commits a day, i don't think they have time to review any code, and it was likely written in full YOLO mode.

So it's not just batteries-included, it's probably 100-vulnerabilities-included as well

Re: Clawdbot - open source personal AI assistant

#59
I installed it a couple of days ago on a Proxmox VM on my home lab server to play with it. The key features are that it has local memory, generates cron jobs on its own and can be the one to initiate a conversation with you based on things that it does. Here are a few simple things I tried:

1. Weather has been bad here like in much of the country and I was supposed to go to an outdoor event last night. Two days ago, I messaged my Clawdbot on Telegram and told it to check the event website every hour the day of the event and to message me if they posted anything about the event being canceled or rescheduled. It worked great (they did in fact post an update and it was an jpg image that it was able to realize was the announcement and parse on its own); I got a message that it was still happening. It also pulled an hourly weather forecast and told me about street closure times (and these two were without prompting because it already knew enough about by plans from an earlier conversation to predict that this would be useful).

2. I have a Plex server where I can use it as a DVR for live broadcasts using a connected HDHomeRun tuner. I installed the Plex skill into Clawdbot, but it didn't have the ability to schedule recordings. It tried researching the API and couldn't find anything published. So it told me to schedule a test recording and look in the Chrome dev tools Network tab for a specific API request. Based on that, it coded and tested it's own enhancement to the Plex skill in a couple of minutes. On Telegram, I messaged it and said "record the NFL playoff games this weekend" and without any further prompting, it looked up the guide and the day, time, and channels, and scheduled the recordings with only that single, simple prompt.

3. I set up the GA4 skill and asked it questions about my web traffic. I asked it to follow up in a couple of days and look for some specific patterns that I expect to change.

4. I installed the Resend skill so it could send email via their API. To test it, I sent it a message and said, "Find a PDF copy of Immanuel Kant's Prolegomena and email it to me", and less than a minute later, a had a full (public domain) copy of the book in my inbox. Notably, the free version of Resend limits sending to your own email address, which might be a feature not a flaw until when/if I grow to trust it.

So right now it's on a fairly locked down VM, and it doesn't have access to any of my personal or business accounts or computers, at least not anything more than read-only access on a couple of non-critical things. Mostly just for fun. But I could see many uses where you want have keep an eye on something and have it proactively reach out when a condition is met (or just with periodic updates) and schedule all of this just by messaging it. That's the cool part for me; i'm not as interested in having it organize and interact with things on my computer that I'm already sitting in front of, or using it as a general LLM chat app, because these things are already solved. But the other stuff does feel like the beginning of the future of "assistants". Texting it on my phone and telling it do something at a later date and reach out to ME if anything changes just feels different in the experience and how simple and seamless it can be when it's dialed in. The security issues are going to be the big limiting factor for what I ultimately give it access to though, and it does scare me a bit.

Re: Clawdbot - open source personal AI assistant

#60
post #55

Earlier quoted context omitted.

The whole world is about bundling (and unbundling). Not saying it really is useful, but there are values bundling an easier interface to CC with battery included.

When someone is pushing 500 commits a day, i don't think they have time to review any code, and it was likely written in full YOLO mode. So it's not just batteries-included, it's probably 100-vulnerabilities-included as well

I agree. It is basically claude code running dangerously all the time. That is actually how I use CC most of the time, but I do trust Anthropic more than random github repo.

(I have the same sentiment about manifest v3 and adblocker, but somehow HN groupthink is very different there than here)

Edit: imagine cowork was released like this. HN would go NUTS.

Post reply on HN