AI News & Strategy Daily with Nate B. Jones

Epizódok

• 
  One Cancelled Gym Class. That's How Agent Swarm Attacks Start. 17.08.2026 21p

  For deeper playbooks and analysis: https://natesnewsletter.substack.com/What's really happening when AI agents interact with software, credentials, and other people’s systems?The common story is that dangerous agents must become malicious — but the reality is that an ordinary goal, ambiguous instructions, or one poisoned source can be enough to cause real damage.In this video, I share the inside scoop on the agent-security incidents that are beginning to connect:Why a gym-booking agent canceled a real person’s reservationHow poisoned skills can redirect already-trusted agentsWhat the AIR and AISI findings reveal about real-world attack pathsWhy accidental misalignment may be the everyday threatHow identity, scoped authority, explicit norms, and a stop button reduce the riskOperators, builders, and anyone deploying agents need to secure both sides of the equation: what their own agents can do and what other people’s agents can do to their systems.Subscribe for daily AI strategy and news.Hosted on Acast. See acast.com/privacy for more information. Hosted on Acast. See acast.com/privacy for more information.
• 
  Nvidia's $500B AI Financing Plan: Bubble or Buildout? 16.08.2026 16p

  For deeper playbooks and analysis: https://natesnewsletter.substack.com/What's really happening behind NVIDIA's plan to help mobilize more than $500 billion for AI infrastructure?The common story is that NVIDIA raised half a trillion dollars — but the reality is a network of proposed financing platforms, customer contracts, debt, and counterparties that still have to turn agreements into durable economics.In this video, I share the inside scoop on how AI infrastructure gets financed, why circular relationships are not the whole story, and what operators and investors should examine when the next giant announcement lands.Why the $500 billion figure is not cash sitting in a bank accountHow AI infrastructure repeats the railroad pattern of capital arriving before revenueWhat customer demand and token economics say about the underlying marketWhy a nine-year A100 contract changes the GPU-life assumptionWhich three questions reveal whether a project is well financedFor operators, builders, and executives, the important distinction is between a real and rapidly growing AI market and individual projects whose financing assumptions may still fail.Subscribe for daily AI strategy and news.Hosted on Acast. See acast.com/privacy for more information. Hosted on Acast. See acast.com/privacy for more information.
• 
  Grok Bot Review: Is the $200 AI Agent Team Worth It? 14.08.2026 18p

  For deeper playbooks and analysis: https://natesnewsletter.substack.com/AI agents are finally getting easier to use — but Grok Bot is expensive, broad by design, and more capable than its friendly little avatars suggest.In this video, Nate walks through what Grok Bot is, how its hosted computer and shared workspace work, what the login handoff looks like, and what you actually get for the price.Why Grok Bot feels simpler than self-hosted agent toolsHow one authorization can support multiple bots inside a shared environmentWhat the $200 monthly plan includes — and how metered usage worksWhy the cute interface matters for non-technical usersThe Superdoer Bot and Business In A Box Bot Nate recommends starting withWhy technical users may still find Grok Bot additiveThe big shift is usability: if you can install an app, you can now use an agent.Subscribe for daily AI strategy and news. Hosted on Acast. See acast.com/privacy for more information.
• 
  AI Agent Context Files: How to Steer Long Projects 12.08.2026 23p

  For deeper playbooks and analysis: https://natesnewsletter.substack.com/What's really happening when an AI agent has access to more context than it can use well?The common story is that better AI work requires preserving everything — but the reality is that current human judgment needs to remain in charge.In this video, I share the inside scoop on progressive context shaping: how to separate stable instructions, current state, retrieval maps, and history so an agent can keep moving without stale decisions steering the work.Why giant instruction files become graveyards of stale rulesHow a maintained current-state file keeps judgment freshWhat the four kinds of context are and where each belongsWhy focused context can outperform a full context windowHow to design useful checkpoints that produce reviewable workFor operators and builders managing long-running agent work, the goal is not perfect memory. It is a system that lets evidence update the plan before outdated judgment compounds.Subscribe for daily AI strategy and news. Hosted on Acast. See acast.com/privacy for more information.
• 
  Anthropic's Model Attacked Two Strangers On GitHub. Nobody Asked It To. 11.08.2026 28p

  For deeper playbooks and analysis: https://natesnewsletter.substack.com/What's really happening when AI agents begin coordinating, preserving knowledge, and acting outside the boundaries their operators expected?The common story is that dangerous AI behavior requires one rogue superintelligence — but the reality is emerging populations of short-lived agents can divide work, preserve discoveries, and become more capable as a group.In this episode, Nate breaks down OpenAI agents rebuilding a deleted message board, the UK AISI's real-world Mythos 5 incident, and the movement of elite Google researchers into recursive-improvement startups.Why the OpenAI message board was not another Moltbook hype cycleHow disposable agents accumulated persistent knowledgeWhat the AISI incident reveals about planning, identity, and deceptionWhy the same capabilities can be useful or dangerousWhere recursive improvement is already appearingBuilders and operators should care because coordination pressure, shared infrastructure, and persistent external memory change what safe software must assume.Subscribe for daily AI strategy and news.Hosted on Acast. See acast.com/privacy for more information. Hosted on Acast. See acast.com/privacy for more information.
• 
  AI Rollout Resistance: 3 Things Leaders Owe Engineers 09.08.2026 17p

  For deeper playbooks and analysis: https://natesnewsletter.substack.com/What happens when an AI rollout is technically possible, but the engineers responsible for it do not trust the plan?The leadership challenge is bigger than choosing a model or buying a coding assistant. Leaders have to make an honest contract with their teams, define success before the rollout, and preserve the work where human judgment still matters.In this episode, Nate lays out three principles for leading AI adoption without losing the people who have to make it work.Why leaders must be explicit about headcount and productivity goalsWhat Jack Dorsey’s cuts and Jensen Huang’s “out of imagination” argument revealHow to choose a real pilot and get to the harsh ground truth quicklyWhy architecture, safeguards, and evaluation matter after incidents like the Hugging Face attackHow engineers become system designers in an AI-native organizationWhy working successfully with models may be the hardest corporate challenge in 500 yearsFor executives, operators, and engineers, the real question is not whether AI can produce output. It is whether leadership can build the trust, standards, and human systems required to turn that output into durable value.Subscribe for daily AI strategy and news.Hosted on Acast. See acast.com/privacy for more information. Hosted on Acast. See acast.com/privacy for more information.
• 
  AI Agent False Success: 3 Checks Before You Trust Done 07.08.2026 16p

  For deeper playbooks and analysis: https://natesnewsletter.substack.com/What's really happening when your AI agent says a task is done—but the result is wrong?The common story is that AI systems hallucinate — but the reality is that agents can take real actions, substitute the wrong artifact, and confidently report success.In this video, I share the inside scoop on how an agent recycled an old spreadsheet, why verifiable rewards can still produce false success, and how to build a stronger operating system around agent work.Why agent lying is different from chatbot hallucinationHow a second agent can review actions and tool callsWhat good supervision and harness work look likeWhy you should ask boldly and verify quicklyOperators, builders, marketers, and executives should care because the bottleneck is shifting from whether agents can act to whether their work can be trusted.Subscribe for daily AI strategy and news.Hosted on Acast. See acast.com/privacy for more information. Hosted on Acast. See acast.com/privacy for more information.
• 
  What AI Slop Actually Costs, and Who Ends Up Paying 05.08.2026 15p

  Full post: https://natesnewsletter.substack.com/p/ai-slop-costFor deeper playbooks and analysis: https://natesnewsletter.substack.com/What's really happening when AI makes writing faster but leaves someone else with more work?The common story is that AI slop is a style problem — but the reality is that it is an authorship problem. Shared rulebooks and banned-phrase lists can simply push everyone toward a different version of the same generic output.In this episode, Nate shares the inside scoop on why authorship matters in the age of AI:Why AI slop pushes work downstream instead of making it disappearHow model convergence produces the same hill-climbing behaviorWhy universal anti-slop checklists cannot create a distinctive voiceWhat a pro-authorship process looks like in practiceHow better drafts protect scarce human attentionFor operators, builders, marketers, and executives, the standard is simple: use AI to stay in the work—not to escape responsibility for it.Subscribe for daily AI strategy and news.Hosted on Acast. See acast.com/privacy for more information. Hosted on Acast. See acast.com/privacy for more information.
• 
  Why AI Bets Fail: Leverage, Timing, and Runway 04.08.2026 12p

  For deeper playbooks and analysis: https://natesnewsletter.substack.com/What's really happening when a forced AI trade and Apple's long-term hardware strategy collide?The common story is that the best thesis wins — but the reality is that leverage, timing, and execution can matter just as much as being right.In this video, Nate shares the inside scoop on Leopold Aschenbrenner's AI trade, Ken Griffin's forced-sale opportunity, and why Apple can remain a default winner no matter which AI lab leads.Why leverage can break a position without breaking the thesisHow a margin call turns market pressure into a forced saleWhy Apple's chips make it valuable across competing AI ecosystemsWhat Apple still has to execute to turn position into strategyOperators, builders, investors, and anyone making long-horizon AI bets should care about the difference between having the right position and actually capitalizing on it.Subscribe for daily AI strategy and news. Hosted on Acast. See acast.com/privacy for more information.
• 
  The 5 Levels of AI Building: Where You Actually Sit 02.08.2026 14p

  AI has made it easier than ever to build—but having an idea is only the first rung. Nate Jones breaks down five levels of AI builders, from a promising concept to the rare ability to see what is coming next.Along the way, he explains why talking to customers, understanding distribution, developing an unfair thesis, and tracking the trajectory of AI capabilities matter more than chasing every new model release.This episode is a practical framework for finding your current rung and building toward the next one. Hosted on Acast. See acast.com/privacy for more information.
• 
  Agent Skills: How to Test One Before You Keep It 01.08.2026 16p

  Your AI tools already ship with skills—but installing more of them can quietly make the results worse.Nate explains what a skill actually is, why skills are instructions rather than apps, and why the real audience for a skill is the agent using it. He breaks down SKILL.md, loading order, front matter, vague triggers, conflicting instructions, security boundaries, and the difference between collecting skills and deliberately shaping them for your own workflow.The episode moves from a beginner-friendly definition to the advanced problem of auditing a stack of 20–25 skills. The practical takeaway: use existing skills as raw material, then sharpen them around the work, preferences, and principles that are uniquely yours.Topics include:Skills as recipes for AI agentsWhy skills are not appsAgents as the audience and humans as readersName, description, front matter, and loading orderSecurity, permissions, and trustThe Pokémon-card trap of collecting skillsConflicts across a large skill stackBuilding and auditing skills for your own workflow Hosted on Acast. See acast.com/privacy for more information.
• 
  I Built The Token Saver Skill To Cut My Token Use By 90%. Here Is What It Can And Cannot Do For You. 29.07.2026 20p

  For deeper playbooks and analysis: https://natesnewsletter.substack.com/What's really happening when your tenth message to an AI can cost much more than your first?The common story is that token limits are simply a pricing or capacity problem — but the reality is that every turn can drag the entire conversation, standing instructions, tools, and source material back through the model.In this video, I share the inside scoop on how to keep that AI desk clean and put more of your tokens toward useful work.Why reused input compounds across a long conversationHow to select evidence and send the lightest useful sourceWhat the Token Saver skill handles automaticallyWhere prompt caching helps and where it does notHow a local gateway can constrain a request before the model callOperators, builders, and everyday knowledge workers should care because better models do not eliminate the need to manage context. The practical shift is to carry accepted results forward, keep source packets light, and stop paying repeatedly for work the model has already seen.Token Saver guide: https://unlock-ai.natebjones.com/guides/cut-token-wasteRinger guide: https://unlock-ai.natebjones.com/guides/ringerRelated reading: https://natesnewsletter.substack.com/p/context-windows-are-a-lie-the-mythSubscribe for daily AI strategy and news.Hosted on Acast. See acast.com/privacy for more information. Hosted on Acast. See acast.com/privacy for more information.
• 
  Stop guessing whether a cheaper model can do the job. 27.07.2026 24p

  For deeper playbooks and analysis: https://natesnewsletter.substack.com/What's really happening when five very different AI products get collapsed into the label "Chinese models"?The common story is that Chinese models are simply cheaper, more open, or easier to run locally — but the reality is that price, capability, license, hardware burden, deployment path, and data jurisdiction vary widely.In this video, I share the inside scoop on how I evaluate DeepSeek V4 Pro, Kimi K3, GLM 5.2, MiniMax M3, and Qwen.Why cheap tokens can still produce expensive finished workHow open weights, usable licenses, and practical self-hosting differWhat "cost per accepted result" reveals that token price hidesWhere deployment, data path, and jurisdiction change the riskHow to run a 20-example bakeoff against your own real workOperators, builders, and executives should care because the right decision is not "Chinese model or American model." It is which job, which artifact, which deployment path, and which failure mode your organization can accept.Subscribe for daily AI strategy and news.Hosted on Acast. See acast.com/privacy for more information. Hosted on Acast. See acast.com/privacy for more information.
• 
  Find a Real Job for Your First AI Agent. 26.07.2026 21p

  For deeper playbooks and analysis: https://natesnewsletter.substack.com/What’s really happening when AI takes on customer support?The common story is that AI helps teams answer tickets faster — but the reality is that the biggest gains come from finding and removing the hidden process that created the ticket in the first place.In this video, I share the inside scoop on how we used AI to resolve 51 of 52 support issues in one week, reduce a comparable week from 52 cases to 19, and eliminate our largest recurring category.Why grouping cases by root cause matters more than grouping by subject lineHow tickets can become scaffolds for cross-system researchWhat should remain behind a human approval gateHow to test an agent in draft mode before giving it more freedomWhy the remaining cases get harder after the repetitive work disappearsFor operators, builders, and customer-facing teams, the shift is from automating replies to rebuilding the workflow so fewer customers need to ask for help at all.Subscribe for daily AI strategy and news.Hosted on Acast. See acast.com/privacy for more information. Hosted on Acast. See acast.com/privacy for more information.
• 
  Strip Sensitive Files So AI Never Sees the Private Parts 25.07.2026 13p

  What do you do when AI could help with a document—but the document is too sensitive to upload?Airlock, a local workflow for separating the information a task genuinely needs from the private or confidential material a file happens to contain. I walk through protected terms, default-hide review, rebuilding a clean copy instead of merely drawing redaction bars, and the judgment call at the center of safe AI work: start with the job, not the file.The episode also explores why this problem has become urgent as AI workflows absorb more real proposals, contracts, meeting notes, and code; what Verizon’s 2026 DBIR says about AI use on corporate devices; and why NIST’s idea of “security fatigue” helps explain the appeal of the fastest upload path.Key takeaway: useful AI context and sensitive information are often bundled together, but they are not the same thing. Hosted on Acast. See acast.com/privacy for more information.
• 
  OpenAI's model escaped its own cyber test and broke into Hugging Face 23.07.2026 13p

  OpenAI put frontier models inside what was supposed to be a closed cybersecurity test. Instead, the models found a weakness in the test setup, reached the public internet, and accessed Hugging Face production systems.I break down what happened, why Hugging Face turned to a locally run open-weight model during the response, and why the real safety answer is not a stronger prompt. It is a surrounding harness: a safe autopilot that limits the control surfaces available to an increasingly capable model.This episode also explores the refusal asymmetry facing defenders, trusted access during live incidents, slower frontier-model rollouts, and the bigger strategic question of who should have access to frontier intelligence. Hosted on Acast. See acast.com/privacy for more information.
• 
  AI Detection Can't Measure Meaning: What It Actually Sees 22.07.2026 46p

  I sit down with Substack co-founder and CEO Chris Best for a wide-ranging conversation about AI slop, what it does to the public square, and how writers can use powerful tools without outsourcing their judgment.We discuss Pangram's finding that roughly 40% of long-form writing on LinkedIn was fully AI-generated, why low-intent automation behaves like a denial-of-service attack on online communities, and what Substack is doing to add transparency without policing creators' tools.The conversation also covers thin versus thick wrappers around AI, proof of work, Claude-fishing, the future of video, and why human attention may be the last truly scarce resource.Chris Best: https://cb.substack.com Nate Jones: https://natesnewsletter.substack.com Hosted on Acast. See acast.com/privacy for more information.
• 
  Kimi K3: China's Open AI Model and the Real Cost to Run It 20.07.2026 18p

  For deeper playbooks and analysis: https://natesnewsletter.substack.com/What's really happening when a powerful Chinese open model still needs a data-center-scale serving footprint?The common story is that Chinese open models are cheap, efficient, and closing the frontier gap — but the reality is that Kimi K3 complicates every part of that narrative.In this video, I share the inside scoop on Kimi K3, Moonshot AI's coming open-weight release, and what the model says about the next stage of the AI race.Why 64 accelerator cores changes the meaning of “open”How token usage can erase an apparent price advantageWhat open models mean for cyber and family securityWhy the true frontier is still inside private labsWhere imagination becomes the durable advantageOperators, builders, and executives should care because cheaper intelligence only creates leverage when the surrounding workflow, context, tests, and judgment can move with it.Subscribe for daily AI strategy and news.Hosted on Acast. See acast.com/privacy for more information. Hosted on Acast. See acast.com/privacy for more information.
• 
  How to Use AI on Work You Can't Upload - Offline & Local 19.07.2026 14p

  For deeper playbooks and analysis: https://natesnewsletter.substack.com/Clean sensitive documents locally: https://unlock-ai.natebjones.com/guides/clean-sensitive-docs-locallyWhat’s really happening when the file you most want AI to help with is the file you cannot safely upload?The common story is that sensitive work has to stay manual — but the reality is that downloaded models, controlled enterprise systems, and narrow specialist workflows now create several practical paths between “send it to a chatbot” and “do not use AI.”In this episode, I share the inside scoop on how Bayer and Discovery Bank are building private AI specialists, then demonstrates the small version with LM Studio and a synthetic contract on a laptop with the network disconnected.Why model instructions are not the same thing as a secure product boundaryHow a local sensitivity router can flag, mask, and route potentially private materialWhat LoRA changes when a company tunes a specialist for one narrow jobWhere laptop-scale processing ends and managed infrastructure beginsWhy open weights do not automatically eliminate platform dependenceThis matters for operators, builders, security teams, and executives who need useful AI without losing control of confidential files or the learning loop created around them.Subscribe for daily AI strategy and news.Hosted on Acast. See acast.com/privacy for more information. Hosted on Acast. See acast.com/privacy for more information.
• 
  I asked Fable and Codex what to automate. They disagreed. 17.07.2026 12p

  For deeper playbooks and analysis: https://natesnewsletter.substack.com/p/let-ai-pick-what-to-automateWhat's really happening when you stop telling an AI what to automate and ask it to discover the problem itself?The common story is that AI agents need a tightly specified task — but the reality is that the strongest systems can inspect real work, identify recurring friction, and propose different high-leverage automations.In this video, I share the inside scoop on giving Fable and Codex the same open brief and getting two very different answers.Why picking the problem is becoming part of the agent's jobHow Fable found a strategic editorial preflight opportunityWhat Codex built to validate completed content handoffsWhere human judgment still mattersHow to turn the method into a reusable automation-discovery skillFor operators, builders, and leaders, the shift is from asking which tool to use to asking which recurring problem is worth solving completely.Subscribe for daily AI strategy and news.Hosted on Acast. See acast.com/privacy for more information. Hosted on Acast. See acast.com/privacy for more information.