<span class="vcard">/u/docybo</span>
/u/docybo

The Hugging Face incident: two failures, and we’re only talking about one

Everyone's focused on the sandbox escape, which is fair, it's the dramatic part. But that was a zero-day in internally hosted software. Containment bugs are old news. We know how to think about them: egress rules, microVM isolation, no ambient …

OxDeAI: I built a deterministic pre-execution authorization boundary for AI agents (fail-closed, signed artifacts, adapters for LangGraph/CrewAI/AutoGen, etc…), looking for feedback.

Hey everyone. I'm the author of OxDeAI, an open-source protocol (Apache 2.0). Posting it here because I want critical feedback from people building real agents, not applause. The problem I keep hitting: as agents move from generating text to doing …

The gap between decision and exécution

I’ve been thinking about a support automation story I read recently. A team replaced a simple rules engine with an LLM classifier. The model was around 92% accurate. Sounds good. Until you realize that at 100 tickets a day, that’s roughly 8 mistakes ev…

We added cryptographic approval to our AI agent… and it was still unsafe

We’ve been working on adding “authorization” to an AI agent system. At first, it felt solved: – every action gets evaluated – we get a signed ALLOW / DENY – we verify the signature before execution Looks solid, right? It wasn’t. We hit a few problems a…

Built a demo where an agent can provision 2 GPUs, then gets hard-blocked on the 3rd call

Policy: – budget = 1000 – each `provision_gpu(a100)` call = 500 Result: – call 1 -> ALLOW – call 2 -> ALLOW – call 3 -> DENY (`BUDGET_EXCEEDED`) Key point: the 3rd tool call is denied before execution. The tool never runs. Also emits: – …

This OpenClaw paper shows why agent safety is an execution problem, not just a model problem

Paper: https://arxiv.org/abs/2604.04759 This OpenClaw paper is one of the clearest signals so far that agent risk is architectural, not just model quality. A few results stood out: – poisoning Capability / Identity / Knowledge pushes attack success fro…

LLM agents can trigger real actions now. But what actually stops them from executing?

We ran into a simple but important issue while building agents with tool calling: the model can propose actions but nothing actually enforces whether those actions should execute. That works fine… until the agent controls real side effects: APIs infra…

What actually prevents execution in agent systems?

Ran into this building an agent that could trigger API calls. We had validation, tool constraints, retries… everything looked “safe”. Still ended up executing the same action twice due to stale state + retry. Nothing actually prevented execution. It on…

Where should the execution boundary actually live in Agent systems?

following up on a discussion from earlier a pattern that keeps showing up in real systems: most control happens after execution – retries – state checks – monitoring – idempotency patches but the actual decision to execute is often implicit if the agen…

AI agents can trigger real-world actions. Why don’t we have execution authorization yet?

While experimenting with autonomous agents recently, I keep running into a pattern that feels oddly familiar from distributed systems history. A lot of current discussion around agent reliability focuses on: better prompting model alignment sandboxed …