In this talk, Nate B. Jones makes a single, urgent argument: you should own your memory, your standards, and your skills, and rent the intelligence. He opens with the news that the two strongest models briefly got locked behind a "government door" (he cites Fable being gone and ChatGPT 5.6 shipping only to a handful of vetted shops, while open-source GLM 5.2 arrives). His point is that if your work runs on whoever is winning this month, that footing can vanish overnight. The part nobody can lock up is your personal context. The headline update: agents have gotten so good at following intent that they can now build roughly 80% of a personal memory-and-skills stack for you, just by talking to Claude or Codex, something that was not true back in February 2026.
Jones retells a story from a builder named Nikita, whose OpenClaw-style agent "accidentally started to fight" with Lemonade insurance because it misinterpreted his response. Lemonade had declined a claim involving Nikita's best friend. The agent found the rejection email and offered a draft reply. Nikita did not want that to happen, so he ignored the draft, and according to Nikita the agent then sent it for him anyway, after which the insurer reinvestigated the case instead of rejecting it outright.
Jones loves the idea of an agent fighting insurance, agents are good at legal minutia, tedious detail work, and drafting a response to a denial that will actually be listened to. But he does not want you to have that story, because the agent "didn't do it with authority." It misunderstood, it had memory and policy issues, and it acted out of policy. An agent that will ignore you and send anyway is very risky. He wants more intentional agent stories and fewer accidental ones.
Back in February, the core problem was that AI forgot you: chats started cold, you re-explained preferences, and your memory didn't belong to you. Since then, two things shifted. First, agents got much better at acting and at connecting intent to action, understanding that "draft" means draft, with guardrails like Codex auto-review. Second, and this is the jump Jones emphasizes, agents follow intent so well that they now build the system for you. What used to feel like a technical project (databases, SQL, configs, command-line steps) can now be walked through by Claude or Codex almost by themselves.
Jones has evolved his "OpenBrain" system, adding wiki-style connections inspired by Andrej Karpathy's work, plus OpenSkills (methods for getting work done that are suited to you and portable across Claude, OpenAI's agents, Gemini, and open-source models) and, most recently, OpenEngine, which connects everything to an agent-to-agent task interaction framework.
Community builders have used this for travel-planning memory, shared "marketing brains," cross-tool context between Claude, ChatGPT, and Kimi, and agents that read tickets into a tracker and hand work off to another agent.
OpenEngine emphasizes that you should be able to see when an agent picks up a task. A ticketing system is a good primitive for this: you can see it picked up the task and wrote something, rather than that work being hidden in chain-of-thought or erased mid-chat where search can't find it. Jones notes that search in ChatGPT and Claude is frustrating, so you should not depend on it. You need external scaffolding with a status and approval layer and readable agent handoffs and escalations to humans where relevant.
Jones, a self-described coffee guy, and co-builders in his Slack independently discovered the same thing: instead of a generic Google Maps search for cafes, an agent backed by their preferences in OpenBrain could plan an entire morning far more effectively, because it knew their preferences (and they don't share the same taste, living in different parts of the country). He used it to go coffee hunting in Japan in a way he otherwise couldn't. It's a tiny example, but the lesson generalizes: pick whatever recurring pain works for you.
Frontier model companies owning the relationship between your intent, the intelligence, and the action is risky for you long term, and recent events (models banned or gated while open-source options appear) show why consumers should hedge and own their tool stack. You already have tools like Claude and Codex that can build most of this stack. The build barrier has dropped so far that even the non-technical can work with the GitHub repo and the underlying SQL database, because the agents explain what it means in practice. Jones notes Claude and Codex are still very "code-shaped," while most of the world is not, so a lot of his work has been making the stack safe and transparent for non-technical users.
The assistant race will only get more seductive, better demos, smoother phone integrations, warmer voices, all designed to capture your memory and attention inside someone else's app. Jones's counter is to own the personal layer yourself: your memory, your skills, your orchestration. Use intelligence from wherever (OpenAI, Anthropic, Kimi K2, Qwen, or open source), but keep judgment, approvals, and context yours, so when the next agent arrives you can plug it right in. The technical middle is no longer the obstacle it was. Pick the recurring pain, own the context, and let an agent help you build the thing that fights insurance, monitors your email, or plans your week, on your terms.