How should we approach the software factory as a product team? r robert-glaser.de 1 youngbrioche 1 month ago 0 comments
The Elastic Loop: A framework for everyone delegating work to machines e elastic-loop.robert-glaser.de 1 youngbrioche 4 months ago 0 comments
When everyone has AI and the company still learns nothing r robert-glaser.de 390 youngbrioche 6 months ago 273 comments
Make OpenClaw your company's training program for agentic AI r robert-glaser.de 2 youngbrioche 7 months ago 0 comments
How Does Truffle Taste? Strategic Lessons for Introducing Agentic Engineering r robert-glaser.de 1 youngbrioche 8 months ago 0 comments
Agentic Pelican on a Bicycle: Claude Opus 4.5 r robert-glaser.de 1 youngbrioche 11 months ago 0 comments
Claude Skills, anywhere: making them first-class in Codex CLI r robert-glaser.de 3 youngbrioche 1 year ago 0 comments
The End of Shouting: Prompts as Programs in GPT-5 r robert-glaser.de 3 youngbrioche 1 year ago 0 comments
Fire Your Fetch Tool – Let Your Agent Use a Browser r robert-glaser.de 3 youngbrioche 1 year ago 0 comments
The entire "Why This Is Dangerous" section is about the security and data exposure implications of running a personal agent. I discuss the Lethal Trifecta (private data access + untrusted content + external actions), explain why I killed email integration after one experiment, and walk through every mitigation I run — network isolation, sandboxing, egress firewalls, approve-only mode. I also explicitly note that right now, you have to rent frontier intelligence via API — your data leaves your machine for inference. Local models simply aren't good enough yet for this kind of agentic work, and they're significantly more susceptible to prompt injection on top of that. That's a real privacy trade-off I'm making consciously, not ignoring.
The post's angle is deliberately "here's what's possible and here's what's dangerous" rather than "here's why you shouldn't do this." I think we need both perspectives. But I'd push back on the framing that this is worse than social networks — with OpenClaw, your data at rest is Markdown on your own hardware, version-controlled in Git, deletable, portable. That's a fundamentally different posture than handing everything to a platform whose business model is monetizing your attention and data.