
Aaron Faby
114 posts

Aaron Faby
@mfachallenge
VP of Information Security @ TWE Solutions. AI | Cybersecurity | Human factors. Opinions strictly personal. @subagentic









Decision making was the bottleneck all along. Productivity is the rate at which you make open-ended decisions, the rate at which you reduce future paths.


Soon @xai will become a real contender in agentic AI coding, and @cursor_ai may be a big reason why. The two pieces to xAI’s success: 1. Grok Build, xAI’s new coding agent and CLI. 2. Grok V9 1.5T, the next-gen foundation model Elon Musk says is already looking strong before Cursor data is added in supplemental training. Put those together and the path gets interesting: a dedicated coding agent, massive xAI compute, and high-quality real-world coding data from Cursor. That could let xAI close the gap much faster than people expect.


Lossless is a really interesting concept for OpenClaw to have an "infinite" context window/memory. It compacts conversations in blocks that the model can refer to, building a tree to look up past messages.


People freaking out over my AI spend. What nobody sees: Part of what excites me so much about working on OpenClaw is that I'm trying to answer the question: How would we build software in the future if tokens don't matter? We constant run ~100 codex in the cloud, reviewing every PR, every issue. If a fix on main lands, @clawsweeper will eventually find that 6 month old issue and close it with an exact reference. We run codex on every commit to review for security issues (as it's far too easy to miss). We run codex to de-duplicate issues and find clusters and send reports for the most pressing issues. We have agents that can recreate complex setups, spin up ephemeral crabbox.sh machines, log into e.g. Telegram, make a video and post before/after fix on the PR. There's codex that watch new issues and - if it fits our documented vision well, automatically create a PR of it. (that then another codex reviews) We have codex running that scans comments for spam and blocks people. We have codex instances running that verify performance benchmarks and report regressions into Discord. We have agents that listen on our meetings and proactively start work, e.g. create PRs when we discuss new features while we discuss them. We build clawpatch.ai to split all our projects into functional units to review and find bugs and regresssions. We do the same split for security with Vercel's deepsec and Codex Security to find regressions and vulnerabilities. All that automation allows us to run this project extremely lean.





