Viewing profile — kxbnb

I built webact while experimenting with browser control for LLM agents and kept running into the same problem: token usage. Most tools wrap Playwright and return huge accessibility…

Fair question. Those three are hosting services for stock OpenClaw — you sign up, they spin up an instance, you get a Telegram bot. That's it. We built something different. Every a…

I run OpenClaw agents for a bunch of different things. The agents are great, the infra around them is not. So I built Claw42. You get a full browser, shell, and tools out of the bo…

I built Axiomo because every AI code review tool I tried kept solving the wrong problem. They all want to be a second developer on your PR, catching lint issues and suggesting refa…

The framing of craft vs. slop misses something important: most production software quality problems aren't about aesthetics or elegance, they're about correctness under real-world …

[dead]

Cool project. The agent shorthand/jargon detection is a unique angle - I haven't seen other tools focus on that specifically. Re: your question about observability pain points - th…

The "output validation not just input validation" point is underrated. Most guardrails focus on what goes into the model, but the real risk is what comes out and gets executed. We'…

Nice execution on the replay testing with semantic diff - that's a pain point that's hard to solve with just metrics. One thing I've noticed building toran.sh (HTTP-level observabi…

Your framing of the problem resonates - treating the LLM as untrusted is the right starting point. The CAR spec sounds similar to what we're building at keypost.ai. On canonicaliza…

Interesting approach to the instruction bloat problem. The composable skills idea makes sense - 500 tokens vs 10K is a real difference. One thing I'd be curious about: how do you t…

The insight about environment attacks vs. model attacks is critical. "The model functioned correctly, yet the overall agent system remained compromised because it trusted its tools…

Nice work - the "deploy-friendly guardrails" framing resonates. Too many MCP tools assume local dev only. To your question about what bites first: in our experience at keypost.ai, …

The middleware proxy approach unop mentioned is the right pattern - you need an enforcement point the agent can't bypass. At keypost.ai we're building exactly this for MCP pipeline…

We're building this at keypost.ai - the enforcement point is a proxy that sits between the agent and MCP servers. Tool calls go through the proxy, get evaluated against policy, and…

Nice approach - fail-closed decision logging is the right default. Too many systems treat audit as best-effort, which defeats the purpose when you're investigating an incident. The…