Posted by KuzeyAbi 1/26/2026
Isn't this just a basic completion loop with toolcalling hooked up to a universal chat gateway?
Isn't that a one shot chatgpt prompt?
(Yes it is: https://chatgpt.com/share/6976ca33-7bd8-8013-9b4f-2b417206d0...)
Why's everyone couch fainting over this?
Two main things worry me about the 'always-on' agent approach:
1. Security & Surface Area: Giving an LLM broad permissions (Email, Calendar, etc.) while it's also scraping arbitrary web content is a prompt injection nightmare. The attack surface is just too wide for production use.
2. Token Economics: Seeing reports of '$300 in 2 days' is a massive red flag. For recurring tasks, there has to be a smarter way than re-processing the entire state every time.
I built Daigest to approach this differently. Instead of an autonomous agent wandering around, it's 'document-centric.' You connect your trusted sources, set a heartbeat, and the AI only processes what's changed to update a structured document. It's less 'magical' than a full agent, but it's predictable, auditable, and won't bankrupt you.
For 'gather and summarize' workflows, a structured document often beats a chat-based agent.
I'm able to juggle the competing priorities in my life without the need of an AI assistant, and I guess I'm just gonna enjoy that for as long as I can because I assume at some point it will become assumed of me.
The key to productivity is doing the _right_ things, not doing everything. Tools that make more possible frequently miss the point entirely.
I told it my local mqtt broker hostname and it figured out I have some relays using tasmota, then told it should remember how to toggle those lights and it did. I used Z.ai GLM 4.7 through OpenRouter as its brain.
It’s definitely worth checking it out, but keeping in mind the amount of things it can run by having a whole computer to itself.
I’ll keep playing with it on a VM and see where this goes.
So anyway long story short I made something like Clawdbot but in the cloud: https://stumpy.ai/
Didn't occur to me to design it to run locally and leave running on my machine. You can't close your laptop or Clawdbot dies? It can read all your files? Rather run agents in the cloud. I gave them sandboxes (Fly sprites) so you can still have them do software development or whatever.
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 current version. Please update. Support for old versions may be purchased (at exhorbitant rates) by contacting i@izs.me npm warn deprecated node-domexception@1.0.0: Use your platform's native DOMException instead
It looks far too risky to use, even if I have it sequestered in its own VM. I'm not comfortable with its present state.
It sounds interesting to me, I might install it on a cheap Mini PC with Ubuntu. This can't come at any worst time as storage and RAM has gotten astronomical. I feel bad for people who are just starting to build their first rig and an alt rig for this.
While I have not interfaced my AI with all the services that Clawdbot does (WhatsApp, Slack, etc.) I don't think that is too much of a stretch from my very simple build.
You point it at your email, and you've opened a vector for prompt injection and data exfiltration - all as an integral part of the features you want (read my emails, send some emails).
Your local LLM won't protect you there.
You could probably write some limited tools (whitelist where mail could be sent) - but it goes against the grain of "magically wonderful ai secretary".
Security is not a convenience.