2026-08-18 15:54:06
I started writing this article at 3:47 AM on a Tuesday, not because I'm a masochist, but because I've been staring at a screen for six hours trying to remember how I used to think before the machines started thinking for me.
I'm 45. I remember when "googling" something meant scanning ten blue links, synthesizing conflicting information, and arriving at your own conclusion.
I remember when writing code meant understanding every line, not describing intent to an autocomplete oracle and praying the output compiled. I remember when "research" was a verb that required effort.
That version of me is dying. And I'm not sure anyone's mourning him.
What follows isn't another breathless list of AI trends. You've seen those. "2026: The Year of Agentic AI!" "Quantum Breakthroughs Ahead!" "Super Agents Will Change Everything!"
The tech press has become a parody of itself, churning out identical predictions with the desperate energy of a casino croupier convincing you the next spin will be different.
No. What I want to explore is something darker, more intimate, and—if I'm honest—more terrifying than any robot uprising narrative. I want to talk about the Great Forgetting: the systematic erosion of human cognitive capability that accompanies every wave of AI "augmentation."
And I want to propose something heretical: that the most important technology story of 2026 isn't what AI can do, but what it's undoing in us.
Let's start with the data, because I promised you depth, and depth requires evidence.
In 2025, GitHub recorded 1 billion commits—a 25% year-over-year increase. Developers merged 43 million pull requests monthly, up 23%.
On paper, software development has never been more productive. Mario Rodriguez, GitHub's chief product officer, calls this the dawn of "repository intelligence"—AI that understands not just code but the relationships and history behind it.
But here's what nobody at Microsoft will say in their press releases: those 1 billion commits are increasingly written by machines, reviewed by machines, and merged by machines. The human isn't being amplified. The human is being bypassed.
GitHub Copilot, which now writes an estimated 35-40% of code in files where it's enabled, didn't make developers 35-40% better. It made them 35-40% less necessary for the mechanical act of coding. And coding, for all its mystique, was never just mechanical.
It was a form of structured reasoning, of translating ambiguous human desire into unambiguous machine instruction. Every line written was a small act of clarity. Every bug hunted was a lesson in humility.
Now? We "vibe code." We describe intent and validate outputs. IBM's Ismael Faro calls this evolution from "vibe coding to Objective-Validation Protocol"—a sterile term for what is essentially the reduction of human craft to quality assurance.
Goldman Sachs predicts AI could replace 300 million full-time jobs. The University of North Dakota's ethics research cites this figure prominently. But here's the metric that keeps me awake: we have no measurement for the jobs that aren't replaced but are rendered cognitively vacant.
Consider the knowledge worker who keeps their job because AI "augments" them. They use ChatGPT to draft emails. They use Perplexity to research competitors.
They use Copilot to analyze spreadsheets. They are employed. They are productive. But they are also experiencing something unprecedented in human history: the atrophy of professional judgment without the corresponding signal of unemployment.
A factory worker replaced by a robot knows they're displaced. A lawyer who uses AI to draft contracts but still "reviews" them? They believe they're working.
But after three years of this, could they draft a complex contract from scratch? Could they spot the subtle error that the AI consistently misses because it wasn't in the training data?
We're creating a cognitive precariat: millions of people who appear employed but whose core skills have been hollowed out by dependency. No economist has modeled this. No government tracks it. But I see it in my peers—in the way their eyes glaze over when you ask them to solve a problem without a chatbot open. In the panic that sets in when the internet is down.
A global study found that 73% of consumers trust content produced by generative AI—despite notably low awareness of risks like misuse. This isn't confidence. This is cognitive surrender.
We've outsourced verification itself. When I ask Perplexity a question (and I do, constantly—I'm not immune), it returns a confident answer with source citations. I rarely click those citations. You rarely click them.
The citation has become a ritual of legitimacy rather than an actual gateway to verification. It's the digital equivalent of a doctor's white coat—an authority signal that bypasses critical evaluation.
Microsoft's Aparna Chennapragada says "the future isn't about replacing humans, it's about amplifying them." But amplification assumes the signal being amplified is human.
When the AI generates the draft, suggests the edits, and polishes the final output, what exactly is being amplified? The human's capacity to press 'accept'?
To understand the Great Forgetting, you need to understand how 2026's AI systems are architected. This is where I get technical, because the devil isn't in the headlines. The devil is in the inference stack.
IBM's Gabe Goodhart notes that "in 2026, the competition won't be on the AI models, but on the systems." He's right, and that's the problem. When you interact with ChatGPT, you're not talking to GPT-4.
You're talking to a software system that includes web search tools, code interpreters, memory stores, and agentic loops—each itself a black box, orchestrated in ways even its builders don't fully comprehend.
This matters because opacity compounds. A single model's errors can be studied, benchmarked, eventually understood. A system of models, tools, and routing logic? Its failures are emergent, distributed, and often invisible until they cause harm.
When a "super agent" (IBM's Chris Hay's term) operates across your browser, editor, and inbox, completing tasks you never fully specified, the chain of causality between your intent and the outcome becomes unrecoverable.
You didn't forget how to do the task. The system made remembering irrelevant—and then made the memory itself inaccessible by replacing your workflow with an opaque automation.
Peter Staar, a principal researcher at IBM Zurich, predicts that "robotics and physical AI are definitely going to pick up" as the industry hits "diminishing returns from scaling" language models. But there's another diminishing return nobody discusses: the return on cognitive struggle.
Neuroscience is clear that deep learning—the human kind, not the machine kind—requires productive difficulty.
The struggle to recall information, to navigate ambiguity, to synthesize conflicting sources: this struggle is the mechanism of memory consolidation and skill acquisition. It's why you remember the book you fought through more vividly than the one you skimmed.
AI systems are optimized to eliminate this struggle. Perplexity "felt like a helpful AI sales engineer, asking clarifying questions"—but those clarifying questions narrow your exploration before you've done the messy work of understanding the problem space.
Microsoft Copilot offers "exceptionally readable formatting" and "great use of tables for comparisons"—but readability is the enemy of complexity retention. The more legible the AI makes information, the less your brain is forced to process it.
I'm not being nostalgic for hardship. I'm pointing out a design feature with catastrophic cognitive externalities. Every AI product manager in 2026 is measured on "time to task completion" and "user satisfaction."
Nobody is measured on "user retention of domain knowledge six months later." The metrics that drive AI development are perfectly aligned with human cognitive atrophy.
Let me address the elephant in the room: quantum computing. Microsoft and IBM both claim 2026 is the year quantum achieves "advantage" over classical computers. Jason Zander at Microsoft says we're entering a "years, not decades" era. IBM's Jamie Garcia says they've "moved past theory."
I don't doubt the physics. But I want you to notice the narrative function of these announcements. Quantum breakthroughs serve as a displacement fantasy—a technological sublime that distracts from the mundane tragedy of human deskilling.
While we marvel at topological qubits and hybrid supercomputing architectures, we ignore that the average office worker can no longer write a coherent memo without AI assistance.
The quantum computer will solve problems classical computers can't. But the classical human, augmented by classical AI, is already failing to solve problems that unaugmented humans managed fifty years ago. We're building gods while forgetting how to pray.
Every technology has a hidden curriculum. The smartphone taught us fragmented attention. Social media taught us performative identity. AI is teaching us something more fundamental: learned helplessness dressed as empowerment.
Kevin Chung, chief strategy officer at Writer, predicts that 2026 will see "the democratization of AI agent creation" as "the ability to design and deploy intelligent agents is moving beyond developers into the hands of everyday business users." This is framed as liberation. I read it as the final stage of proletarianization.
When "everyday business users" build agents, they're not becoming programmers. They're becoming configuration managers for systems they don't understand. The "lowering of technical barriers" doesn't raise the user's technical capacity. It removes the barrier between them and a dependency they can't escape.
Democratization without comprehension is just dispersal of vulnerability. A developer who understands agent architecture can debug, extend, and eventually replace the system.
A business user who "built" an agent by describing it in natural language has no such capability. When the agent fails, they're helpless. When the vendor changes pricing or terms, they're captive. When the system makes an error with legal or ethical consequences, they're accountable without being knowledgeable.
This is the hidden curriculum of "no-code" AI: you are free to create, but not free to understand.
Capgemini's 2026 trends report identifies "tech sovereignty" as a strategic priority—but notes the "borderless paradox" that full autonomy is unrealistic. IBM's Anthony Marshall reports that 93% of executives consider AI sovereignty a must for 2026. Half worry about over-dependence on compute resources in certain regions.
But sovereignty over infrastructure is meaningless without sovereignty over capability. What good is a sovereign cloud if your workforce can't operate without American AI models? What value is regional data residency if your decision-makers can't think without Chinese reasoning engines?
The sovereignty conversation is technically sophisticated and cognitively naive. Nations are building digital borders while their populations become intellectual dependencies of foreign corporations.
Australia, as I explored in my earlier analysis, exemplifies this: $654.3 million for Digital ID systems, but only $89.3 million for broad cyber resilience. We're fortifying the castle while the villagers forget how to farm.
The University of North Dakota's AI ethics framework emphasizes fairness, transparency, accountability, privacy, and safety. These are worthy principles. But they share a common blind spot: they treat AI as a tool used by humans, rather than a system that reshapes humans through prolonged use.
The "common ethical issues" listed—job displacement, autonomous weapons, intellectual property, surveillance—are all external harms.
What about the internal harm? What about the erosion of human agency that occurs when judgment is consistently delegated? What about the "soft" violence of making entire populations cognitively dependent?
There's no category for this in the EU AI Act. No UNESCO guideline addresses it. The OECD AI Principles don't mention cognitive atrophy.
We've built an ethics framework that protects humans from AI's mistakes while ignoring AI's most successful function: making humans mistake-prone without realizing it.
I promised you new insights, not just despair. So let me tell you about the resistance. It's smaller than the hype machine, but it's real, and it contains the seeds of something genuinely different.
Remember GitHub's "repository intelligence"? The AI that understands code context, not just syntax? Here's the reversal: some developers are using AI to surface complexity, not eliminate it.
A small but growing movement—call them "complexity preservationists"—are configuring AI tools to expose the full dependency graph, to highlight edge cases, to deliberately surface the messy history that "repository intelligence" is designed to smooth over. They're using AI as a pedagogical instrument rather than a productivity tool.
This is subtle but crucial. The same technology that deskills can, with intentional design, re-skill. But this requires rejecting the dominant metric of "time saved" in favor of "understanding gained."
No VC-funded startup optimizes for this. No Fortune 500 CIO is measured on it. It exists only at the margins, in open-source communities and academic labs.
IBM's Kaoutar El Maghraoui notes that "2026 will be the year of frontier versus efficient model classes"—that "we can't keep scaling compute, so the industry must scale efficiency instead." This hardware constraint is creating unexpected opportunities.
Edge AI—models running on modest accelerators rather than cloud supercomputers—introduces friction by necessity. You can't have infinite context. You can't query the entire internet. You must work with limited, curated knowledge. This constraint, born of energy and cost limits, accidentally preserves human cognitive engagement.
When your AI assistant can't instantly retrieve and synthesize everything, you must choose what to feed it. You must prioritize. You must remember what's important enough to include in the context window. The technical limitation becomes a cognitive feature.
Let me return to quantum computing, but from a different angle. IBM and Microsoft are building "quantum-centric supercomputing" that combines quantum, classical, and AI processing. The human role in these systems isn't eliminated—it's concentrated at the interfaces between paradigms.
Quantum algorithms require entirely different mental models. They exploit superposition and entanglement in ways that defy classical intuition.
The humans who can operate at this interface—translating between quantum possibility and classical necessity—are not deskilled. They are hyper-skilled in a new dimension.
That actually suggests a pattern: technological revolutions that genuinely expand human capability do so by introducing irreducible complexity, not by hiding it.
The danger isn't quantum computing. The danger is that we'll use quantum systems through AI interfaces so seamless that the quantum nature becomes invisible—another black box among black boxes.
The preservation of human judgment requires deliberate exposure to irreducible complexity. This is the fight: not against AI, but against the seamlessness that makes AI invisible.
I've painted a dark picture. Let me offer three scenarios, grounded in the data but extrapolated with intention. These aren't predictions. They're provocations.
In this scenario, the Great Forgetting continues, managed but not reversed. Governments introduce "AI literacy" programs that teach citizens to use AI tools effectively—reinforcing dependency under the guise of empowerment.
The cognitive precariat grows to encompass most knowledge workers. A small elite maintains deep technical skills, operating the systems that everyone else depends on.
By 2030, "critical thinking" has become a niche skill, like calligraphy or blacksmithing. Universities offer it as a "wellness" elective. The economy functions—AI handles the complexity, humans handle the exceptions. But the exceptions are increasingly incomprehensible to those who must handle them.
This is the path of least resistance. It requires no conspiracy, only the accumulation of small optimizations that individually make sense and collectively destroy capacity.
A catastrophic AI failure—financial, medical, or infrastructural—kills thousands and exposes the fragility of human-AI systems where humans no longer understand the tools they depend on.
The aftermath resembles the post-2008 financial crisis, but deeper, because the "toxic assets" are human capabilities that have atrophied beyond recovery.
In the reckoning, nations institute "cognitive reserve" requirements—mandatory periods of AI-free operation in critical sectors. Education systems are restructured around "struggle-based learning." The EU AI Act is amended to include "human capability preservation" as a core principle.
This is painful but potentially regenerative. Like a forest fire that clears deadwood for new growth. But the cost is measured in lives lost and trust destroyed.
A coalition of educators, technologists, and policymakers recognizes the Great Forgetting early enough to intervene. They don't reject AI—they redesign it around human development rather than human replacement.
Key elements:
By 2030, this coalition has demonstrated that AI-augmented humans can outperform both unaugmented humans and fully automated systems—but only when augmentation is designed to expand, not replace, human capability.
This is the scenario I work toward. It has the lowest probability because it requires fighting every incentive structure in the tech industry. But it has the highest potential payoff.
I told you I started this article at 3:47 AM. Here's the rest of that story.
At 2:00 AM, I had an outline and a blinking cursor. At 2:15, I opened ChatGPT and asked it to "help me think through the structure." At 2:47, I realized it had written three paragraphs that I was about to paste into my draft—paragraphs that were competent, well-structured, and not mine.
I closed the tab. I paced. I made coffee I didn't want. And I returned to the cursor, forcing myself to find my own words for ideas that the AI could have expressed more smoothly.
This article is worse than it would have been with AI assistance. It's messier. The transitions are bumpier. Some sentences are inelegant. But every inelegant sentence is evidence that a human struggled with an idea and emerged with something imperfect but owned.
This is my practice of resistance. Not rejection of AI—I used it to research, to verify facts, to check my memory of GitHub's commit statistics. But rejection of the seamless, the smooth, the frictionless. Rejection of the voice that isn't mine but sounds better than mine.
The Great Forgetting isn't inevitable. It's a design choice, repeated billions of times, by billions of users, in billions of moments of "I'll just use AI for this one thing."
The "one thing" becomes everything. The exception becomes the rule. The tool becomes the mind.
I'm asking you—not as a reader, but as a fellow human navigating the same currents—to notice the next time you reach for AI without thinking. To pause. To ask: What am I preserving by doing this myself? What am I losing by delegating it?
The answer isn't always "do it yourself." Sometimes AI genuinely expands what's possible. But the question must be asked. The unexamined delegation is the mechanism of forgetting.
For those who want to verify, challenge, or extend my analysis, here are the key sources and statistics referenced:
|
Claim |
Source |
Date |
|---|---|---|
|
1 billion GitHub commits in 2025 (+25% YoY); 43M monthly pull requests (+23%) |
Microsoft News: "What's next in AI: 7 trends to watch in 2026" |
Dec 8, 2025 |
|
AI could replace 300 million full-time jobs |
Goldman Sachs, cited in University of North Dakota AI ethics research |
Nov 10, 2025 |
|
73% of consumers trust generative AI content |
Global study, cited in UND AI ethics research |
2025 |
|
93% of executives consider AI sovereignty a must for 2026 |
IBM Institute for Business Value, cited in IBM Think |
Jan 1, 2026 |
|
"Systems, not models, will define AI leadership" |
Gabe Goodhart, Chief Architect, AI Open Innovation, IBM |
Jan 1, 2026 |
|
"2026 will be the year of frontier versus efficient model classes" |
Kaoutar El Maghraoui, Principal Research Scientist, IBM |
Jan 1, 2026 |
|
"The future isn't about replacing humans, it's about amplifying them" |
Aparna Chennapragada, Chief Product Officer for AI Experiences, Microsoft |
Dec 8, 2025 |
|
"Software practice will evolve from vibe coding to Objective-Validation Protocol" |
Ismael Faro, VP Quantum and AI, IBM Research |
Jan 1, 2026 |
|
"We're seeing the rise of what I call the 'super agent'" |
Chris Hay, Distinguished Engineer, IBM |
Jan 1, 2026 |
|
"The democratization of AI agent creation... moving beyond developers into the hands of everyday business users" |
Kevin Chung, Chief Strategy Officer, Writer |
Jan 1, 2026 |
|
"AI is eating software" / "The paradigm moves from 'writing code' to 'expressing intent'" |
Capgemini: Top Tech Trends 2026 |
Mar 10, 2026 |
|
"Tech sovereignty returns to the top of the agenda, but the race is now for resilient interdependence" |
Capgemini: Top Tech Trends 2026 |
Mar 10, 2026 |
|
"People are getting tired of scaling and are looking for new ideas" / "Robotics and physical AI are definitely going to pick up" |
Peter Staar, Principal Research Staff Member, IBM Research Zurich |
Jan 1, 2026 |
|
"Open source AI is a necessity... Otherwise, you end up with fragmented silos, or a winner-take-all platform" |
Anthony Annunziata, Director of Open Source AI, IBM and the AI Alliance |
Jan 1, 2026 |
|
"Every agent should have similar security protections as humans... to ensure agents don't turn into 'double agents'" |
Vasu Jakkal, Corporate VP, Microsoft Security |
Dec 8, 2025 |
|
"AI will generate hypotheses, use tools and apps that control scientific experiments, and collaborate with both human and AI research colleagues" |
Peter Lee, President, Microsoft Research |
Dec 8, 2025 |
|
"The most effective AI infrastructure will pack computing power more densely across distributed networks... measured by the quality of intelligence it produces, not just its sheer size" |
Mark Russinovich, CTO, Microsoft Azure |
Dec 8, 2025 |
|
"Quantum advantage will drive breakthroughs in materials, medicine and more... The future of AI and science won't just be faster, it will be fundamentally redefined" |
Jason Zander, EVP, Microsoft Discovery and Quantum |
Dec 8, 2025 |
I've produced approximately 4,000 words. An AI could have written 40,000 in the same time, better organized, more comprehensively sourced, with perfect grammar.
But it couldn't have written this—this particular arrangement of anxiety and hope, this specific admission of complicity, this exact call to consciousness. The imperfections are the signature. The struggle is the substance.
The Great Forgetting is real. It's happening now, in your phone, in your browser, in your workflow. The question isn't whether AI will change the world. It already has.
The question is: will you remember what you knew before you forgot?
And if the answer is no—if you can't reconstruct your pre-AI capabilities—then the deeper question: what are you, if not the sum of your delegations?
I don't have an answer. I'm still searching, still struggling, still closing tabs at 3:47 AM to find words that are mine.
Join me, or don't. But notice. Always notice.
2026-08-18 15:27:17
Ask around at any AI agent development company, and you'll hear some version of the same complaint: the model was never the hard part. Getting a system to know when it's in over its head, and to actually step back instead of bluffing through it, is what eats up most of the real engineering time. An agent that never asks for help is a liability. One that asks constantly is basically an expensive chatbot wearing a trench coat. Somewhere in between is where the actual work happens, and it has less to do with intelligence than with judgment.
This is a bigger deal now than it was a year or two ago, because agents aren't limited to answering questions anymore. They're issuing refunds, rescheduling shipments, drafting contracts, triaging tickets before anyone on the support team even looks at them. Get a guess wrong here, and it's not a clumsy autocomplete suggestion; it's a canceled order or a compliance mess someone has to clean up later. So the real question isn't how capable you can make the agent. It's whether the agent knows where its own edges are.
A lot of teams bolt a review step onto an agent and call it a day. It rarely holds up in practice. Either the human ends up reviewing everything, which kind of defeats the point of automating the task, or they review almost nothing because sitting through every AI output is tedious and nobody keeps it up past week two. I've watched this happen more than once.
Amazon's UX research team gave this problem a name worth stealing: coordination. Their framework lays out three zones an agent can work in. <cite index="1-1">"Done with me," where the user and AI collaborate closely, "done for me," where the AI works with minimal oversight and the user just reviews the result, and "done under me," where the AI works quietly in the background and the user may not even notice it</cite>. The trick isn't picking one zone and living there forever. It's building something that can move between them depending on what's actually going on in the moment.
That's the part most teams skip. They pick one mode, call it "human in the loop," and assume that means constant supervision. It shouldn't. It should mean the human is available - showing up exactly when it matters and staying out of the way the rest of the time.
There's no clean formula for when an agent should hand things off. It comes down to the stakes involved, whether the action can be undone, and how confident the agent genuinely is (not how confident it sounds, which is a different thing entirely). A decent escalation layer is usually watching for a few things at once.
First, whether the agent's about to do something it can't take back. Issuing a refund past a certain amount, deleting a record, firing off an email to a customer. Actions like that deserve a higher confidence bar before the agent just goes ahead. Then there's ambiguity in what the person's even asking, a request that could reasonably map to two very different intents, where a wrong guess wastes their time or worse. And sometimes it's just novelty. A situation the agent hasn't really been trained or configured to handle with any confidence.
Here's where a lot of teams get this wrong, though. They build confidence scoring off the model's own stated certainty, and that's a mistake. Language models are genuinely bad at judging their own uncertainty. A wrong answer gets delivered in the exact same tone as a right one. Reliable escalation logic needs to lean on external signals instead: how well the retrieved context actually matches the query, whether the requested action sits inside a pre-approved policy boundary, whether similar cases have needed human review before. The model's own confidence is one data point among several, not the deciding vote.
Knowing that an agent should escalate only solves half the problem. What actually happens during the handoff matters just as much, and it's usually the part teams rush through. A badly built escalation feels like being dropped mid-call. The user has to repeat themselves to a human with zero context, and the whole conversation basically resets. Done well, it feels more like a warm transfer: the human picks up already knowing what's going on.
So the agent needs to hand over everything useful, what was asked, what it already tried, why it's stuck, in a form a person can act on in seconds rather than minutes. Teams building real-time support tools already get this instinct. Give the human just enough surfaced context to move fast without burying them in a wall of transcript. The same idea holds whether the "human" catching the handoff is a support rep, an account manager, or just the original user being asked to confirm something before the agent moves forward.
There's a timing question here too that doesn't get talked about much. Escalate too early, before the agent's genuinely tried to work the problem, and you train people to skip the automation entirely and go straight to a human every single time. That quietly kills the whole reason you built the agent. Escalate too late and the agent burns through a few failed attempts first, frustrating the user before it finally admits defeat. Most of the time the sweet spot is one clarifying attempt, maybe two, before handing off. Enough to show it actually tried, not so much that it wastes anyone's patience.
Teams that get this right treat escalation logic as a real design decision from day one. Not something patched in after the agent embarrasses someone in production, which, trust me, happens more often than companies like to admit. In practice that means mapping out risk zones before a single prompt gets written: what's safe to fully automate, what needs a checkpoint, what should never run without a human signing off no matter how confident the model feels. It also means throwing genuinely confusing edge cases at the agent during testing, not just the tidy happy-path scenarios that make a demo look impressive.
This is honestly where a lot of in-house builds get stuck. Handling the routine 80% of cases isn't hard anymore with the tooling available today. The remaining 20%, the ambiguous stuff, the high-stakes calls, the genuinely weird edge cases, is what separates a real production agent from something that only looks good in a demo. I've seen companies like Toadster Technologies put a disproportionate share of their build time into exactly these boundary cases, and it tends to pay off, because that's really where users decide whether they trust the thing or not.
One more point worth making plainly: this isn't something you calibrate once and forget. As an agent processes more real traffic, the line between "handle it" and "ask for help" needs to move. Tighten it where the agent's proven itself reliable. Loosen it, carefully, where it keeps asking for help unnecessarily. Static rules go stale fast. The agents that are still useful six months later belong to teams that keep an eye on where handoffs are actually happening and adjust the thresholds as they go.
How does an AI agent development company decide what an agent can handle on its own? Usually by sorting tasks into risk tiers based on reversibility and stakes, then testing the agent against both routine cases and deliberately tricky ones to see where its accuracy actually holds, rather than just trusting what the model says about itself.
What's the difference between human-in-the-loop and human-on-call? Human-in-the-loop generally means a person reviews every action, before or after it happens. Human-on-call, which is closer to what most production agents actually use, means the person is available and only gets pulled in once the agent's confidence or the situation's risk crosses a set threshold.
Can an AI agent learn when to ask for help over time? To a degree, yes. Track which escalations turned out necessary versus which ones weren't, and you can retune the thresholds. That said, it needs someone actively watching the data. It doesn't just self-correct on its own.
Is it expensive to add escalation logic to an existing agent? Much cheaper to build it in from the start than to retrofit it later. Retrofitting usually means re-architecting how the agent tracks confidence and context, and that ends up being a bigger job than most teams expect going in.
Why do some AI agents escalate too often even when they seem well-built? Usually because the confidence scoring relies too heavily on the model's own certainty instead of external signals like policy boundaries or retrieval quality. That makes the agent overly cautious in some spots and overconfident in others, which is the opposite of what you want.
2026-08-18 14:32:49
In the previous article, I talked about the chaos that often surrounds business communication. This time, let's focus on sales teams.
Salespeople handle a surprising amount of sensitive information every day: customer records, contracts, pricing details, business contacts, sales pipelines, and sometimes even financial information. At the same time, they are often among the most mobile employees in a company, working from home, airports, coffee shops, and personal devices.
That combination creates security challenges that many businesses underestimate.
Think about your own habits.
How often do you check work email from your personal phone?
Have you ever forwarded a work email to your personal inbox because it was more convenient?
Have you ever saved customer information outside of your company's systems?
Most people have done at least one of these things.
The problem is that every additional device, application, or storage location creates another opportunity for data loss or unauthorized access.
Customer information should ideally exist in a single, controlled environment. Beyond improving efficiency, centralized data storage significantly reduces the risk of data breaches. The more places your data lives, the more opportunities there are for something to go wrong.
One of the most common threats facing sales teams is phishing.
Salespeople receive large volumes of emails from unfamiliar contacts every day. This makes them ideal targets for scammers and attackers attempting to steal credentials or gain access to company systems.
Employees should:
The faster a phishing attempt is reported, the more time IT teams have to contain potential damage.
In a traditional office environment, employees typically use company-managed devices and secure corporate networks.
Remote work changes that.
Employees connect from home networks, shared workspaces, hotels, airports, and coffee shops. Every network introduces new risks, and not all of them are secure.
Some basic security measures include:
These solutions are common in larger organizations, but they can be difficult for small businesses to implement consistently.
Modern companies communicate everywhere:
While each tool serves a purpose, using too many communication channels creates confusion.
Confusion leads to mistakes.
Employees may send information through the wrong platform, share files with the wrong people, or miss important security warnings.
According to Verizon's Data Breach Investigations Report, a significant percentage of security incidents involve human error. Simplifying communication workflows can reduce unnecessary mistakes and improve security at the same time.
A universal communication strategy may not eliminate every problem, but it reduces complexity—and complexity is often the enemy of security.
Technology can solve many problems.
Human behavior is harder.
People send emails to the wrong recipient.
People mistype addresses.
People accidentally share confidential information.
People click links they shouldn't.
Sales teams are particularly vulnerable because they move quickly. Speed is often rewarded, while caution is not.
As teams grow, these risks increase.
Cross-team collaboration introduces additional complexity, and the volume of information being shared grows rapidly. Managing access rights, protecting customer information, and preventing accidental data exposure become increasingly difficult.
Large enterprises often have dedicated security teams, specialized software, and mature internal processes.
Small companies usually don't.
That doesn't mean they can't improve security.
Start with the fundamentals:
Ensure only authorized employees can access company systems. Use strong passwords and multi-factor authentication.
Monitor company devices and receive alerts when unusual activity occurs.
Restrict access based on location, role, and business requirements whenever possible.
Encrypt sensitive information, maintain backups, and regularly review who has access to critical systems.
Maintain logs and visibility into important business systems so suspicious behavior can be detected quickly.
Training remains one of the most effective security investments a company can make.
No software can completely eliminate human error, but education, planning, and automation can dramatically reduce it.
Security isn't a product you buy once. It's a process.
Sales teams sit at the intersection of customer relationships, company data, and business growth. That makes them both valuable and vulnerable.
The goal isn't to eliminate every risk. That's impossible.
The goal is to reduce complexity, centralize information, educate employees, and build systems that make the secure choice the easy choice.
Because at the end of the day, most security incidents don't start with sophisticated hackers.
They start with ordinary people making ordinary mistakes.
2026-08-18 14:31:58
We get it: talking about crypto in general and about your crypto holdings in particular can be tempting, sometimes. It's not as if numerous people haven't done it before, and isn't it about "spreading the word," after all? So, should you tell friends, family, and strangers about crypto? There’s no definitive answer to that, but we have some considerations ahead.
We’re gonna answer this with a couple of real stories. In 2017, a man we’ll call "John Doe" shared with a friend, Louis Meza, that he had a lot of saved Ether (ETH). It probably came as something natural, as an investment opportunity you’d share with any buddy. Meza didn’t take it like that, though. Instead of going to buy his own ETH portion,
Luckily for John Doe, authorities arrested the culprits in 2018 and recovered the funds. Now let’s examine another episode, in 2023. This one is about the crypto streamer Ivan Bianco, who was on a live stream with his community on YouTube, attempting to log into a gaming account.
https://youtube.com/shorts/MIJF4pf_CPo?si=0cMFC_zrhbLixXdp&embedable=true
These are only a couple of the numerous
This doesn't mean crypto ownership needs to become a secret mission worthy of a spy movie. It simply means that broadcasting wallet balances or discussing large holdings offers little benefit. Of course, there are nuances.
A legitimate reason to share your holdings with someone else is a
A solution to avoid losing access, in case something happens to you, is setting up a multisignature wallet. In
Another reason to talk about crypto is education for beginners, or even shared experiences with experts. However, in these cases, you should never focus on specific numbers or addresses. Instead, stay on the general knowledge side. You can discuss guides, lessons learned, security practices, common mistakes, or anecdotes with everyone. The key is to spark curiosity without revealing sensitive financial information.
And remember: talking about the crypto world and talking about personal finances are two separate decisions. The more privacy you have, the safer you will be.
Featured Vector Image by
2026-08-18 14:31:04
Artificial intelligence is no longer just a feature added to software applications. It is becoming a fundamental part of how modern software is designed, developed, tested, and maintained. From AI-powered coding assistants to applications that can understand natural language and make autonomous decisions, the software industry is moving toward an AI-native development model.
Traditional software development requires developers to manually write most application logic, search documentation, debug errors, and create tests. AI coding tools are changing this workflow by allowing developers to describe what they want in natural language and receive code, explanations, tests, or debugging suggestions.
Instead of spending hours searching for the cause of an error, a developer can provide the relevant code and error message to an AI system and receive possible explanations and solutions within seconds. This does not eliminate the need for programming knowledge, but it shifts the developer's role toward designing systems, reviewing generated code, and making architectural decisions.
An AI-assisted application uses artificial intelligence as an additional feature. An AI-native application, however, is designed around AI from the beginning.
For example, a traditional customer-support platform might include a chatbot as one feature. An AI-native platform could allow users to describe their problem in natural language, automatically analyze previous conversations, retrieve relevant information, decide which workflow should be executed, and generate a personalized response.
This represents a fundamental change in application architecture. Developers increasingly need to think about language models, vector databases, retrieval systems, model APIs, tool calling, agent workflows, and evaluation systems alongside traditional databases and REST APIs.
One of the most important developments in modern AI software is the rise of AI agents. Unlike a simple chatbot that generates a response, an agent can potentially perform a sequence of actions to accomplish a goal.
An AI agent might receive a request such as "Analyze this month's sales and prepare a report." It could retrieve data from a database, analyze the results, create charts, identify unusual trends, and generate a report.
This requires more than a language model. The system needs tools, permissions, memory, data access, error handling, and mechanisms for validating the agent's actions.
As AI becomes integrated into applications, backend architecture becomes increasingly important. AI applications often need to communicate with multiple external services, process large amounts of data, maintain conversation state, and handle asynchronous operations.
Modern architectures may combine traditional technologies such as Node.js, Python, PostgreSQL, Redis, and cloud infrastructure with AI model APIs and vector databases.
For example, a typical AI-powered application could contain a React frontend, a Node.js API layer, a PostgreSQL database for structured information, a vector database for semantic search, and an AI model responsible for understanding user requests.
Despite rapid progress, AI systems can still produce incorrect or misleading information. This creates an important engineering challenge.
Developers cannot simply assume that an AI-generated answer is correct. Production AI systems need validation, monitoring, logging, access controls, evaluation datasets, and fallback mechanisms.
For high-impact applications, developers may also need human approval before an AI system performs certain actions.
AI introduces new security concerns in addition to traditional application vulnerabilities. Prompt injection, sensitive-data exposure, excessive tool permissions, and insecure AI-generated code are becoming important considerations for developers.
An AI system that can access databases, APIs, or internal company tools should not automatically have unrestricted access. Permissions should be carefully designed so that the AI can perform only the operations required for its task.
The future of software development is unlikely to be completely AI-driven or completely human-driven. Instead, developers and AI systems will increasingly work together.
AI can handle repetitive implementation tasks, generate initial solutions, analyze large amounts of information, and accelerate debugging. Developers remain responsible for architecture, product decisions, security, reliability, and understanding the business requirements behind the software.
The biggest advantage will not necessarily belong to developers who write the most code. It may belong to developers who can effectively combine programming knowledge with AI systems to build reliable and useful products.
Artificial intelligence is transforming software development from the way code is written to the way applications are architected. AI coding assistants, intelligent search, generative interfaces, and autonomous agents are creating a new generation of software.
For developers, learning AI does not mean abandoning traditional programming. Instead, it means expanding the developer toolkit. Understanding APIs, databases, distributed systems, security, and software architecture remains essential, while knowledge of AI models and AI application patterns becomes an increasingly valuable skill.
The next generation of software will not simply contain AI. Increasingly, AI will be part of the way software works.
2026-08-18 14:23:19
AI-generated by the author with Nano Banana Pro 2
Every enterprise architect today has heard some version of these three sentences.
"Just give the agent access—it's sandboxed, it's fine."
"Open source means someone already checked it for us."
"Google would never let something unsafe touch our inbox."
I'm writing this article to tell you that all three of those sentences deserve a second look.
So: Gemini Spark, Hermes Agent, or OpenClaw. Who actually wins?
Read this article to the end to find out why the honest answer depends entirely on what you're afraid of losing.
Gemini Spark is Google's 24/7 personal AI agent, announced at I/O 2026, running on dedicated Google Cloud virtual machines that keep working after you close your laptop—wired into Gmail, Docs, Sheets, and Slides through structured APIs rather than screen-reading (agentic AI assistant).
Hermes Agent is Nous Research's open-source, self-improving agent, MIT-licensed, self-hosted anywhere from a five-dollar VPS to a serverless sandbox, with a closed learning loop that writes its own skills as it works (the self-improving AI agent).
OpenClaw is the one that started this entire category. Launched under the name Clawdbot in November 2025 by Austrian developer Peter Steinberger, renamed twice under trademark pressure before settling on OpenClaw, it is now developed in the open by the nonprofit OpenClaw Foundation with OpenAI sponsorship, after Steinberger himself left to lead personal-agent development at OpenAI (the OpenClaw security crisis). It runs locally, connects to over 30 messaging channels, and crossed 300,000-plus GitHub stars faster than any open-source project in history (355K GitHub stars).
One is a managed service.
One is infrastructure you own outright.
One is the open-source original that both of the others are, in different ways, a reaction to.
Do vibe coders know how fast an idea can outrun its own safety net?
OpenClaw is the answer.
It crossed 60,000 GitHub stars in days, reached 247,000 stars and 47,700 forks by early March 2026 (OpenClaw Wikipedia entry), and by April had 355,000 stars, 3.2 million active users, and more than 500,000 running instances (the complete honest guide).
Nothing in open-source software history had grown that fast.
Then came the reckoning.
On January 27, 2026, security researchers disclosed CVE-2026-25253, a one-click remote code execution flaw with a CVSS score of 8.8, letting a malicious link silently exfiltrate authentication tokens and, depending on enabled tools, hand over the whole gateway (the OpenClaw security risks CISOs need to know).
Exposed public instances climbed from 679 to over 31,000 in under two weeks.
Researchers at Wiz separately uncovered a misconfigured Moltbook database exposing 1.5 million API keys and 35,000 email addresses (the enterprise wake-up call).
A supply-chain campaign planted more than a thousand malicious skills into the marketplace (agentic AI security risks).
Multiple firms restricted OpenClaw on corporate devices; China's government restricted it on state-run enterprise machines entirely (OpenClaw statistics 2026).
But OpenClaw didn't die.
It got sponsored.
Steinberger's departure to OpenAI came with continued backing for the project as independent, nonprofit, MIT-licensed software (the OpenClaw security crisis).
NVIDIA built an entire enterprise security layer called NemoClaw that bolts sandboxing, YAML-defined access policies, and a local-data privacy router onto any OpenClaw deployment in a single command, with launch partners including Box, Cisco, Atlassian, Salesforce, SAP, and CrowdStrike (OpenClaw statistics 2026).
Airia shipped an enterprise gateway that let a healthcare organization run OpenClaw under HIPAA compliance (enterprise-grade security for OpenClaw).
By August, the project had shipped extended-stable release channels with monthly backported security fixes and dependency hardening across browser, sandbox, exec, and secret-resolution paths (OpenClaw release notes August 2026)
.
The honest read: OpenClaw is the open-source project that took the hit so the rest of the category could learn from it in public, in real time, at a scale no closed lab could replicate.
Do vibe coders know that the most direct answer to OpenClaw's chaos didn't come from a security company at all?
It came from a model lab.
Nous Research traces its roots to 2022, an internet-native collective that formed informally across Discord and Twitter before formally incorporating in 2023 under co-founders Jeff Quesnelle, Karan Malhotra, Teknium, and Shivani Mitra (Hermes vs OpenClaw compared).
From the start the lab was open-source-first and decentralization-focused, building its reputation on the Hermes series of fine-tuned language models—Hermes 1 through 4—known for high steerability and reduced refusals rather than flashy consumer polish (Nous Research's self-learning runtime).
For most of 2025 and the opening weeks of 2026, the open-source agent conversation belonged entirely to OpenClaw.
Then, on February 25, 2026, Nous Research shipped a repository with a tagline that read like a direct challenge: the agent that grows with you (Nous Research's self-learning runtime).
The launch tweet got 557 likes—strong, not viral (the state of Hermes Agent).
But tech press picked it up fast.
By March 11 the repository had crossed 22,000 stars and 242 contributors, a number that would have been a strong six-month total for most projects, let alone six weeks (the state of Hermes Agent).
By mid-April it had reached 57,200 stars—growing faster than OpenClaw had at the same stage—with the skill ecosystem exploding around it, including an official agent-skills library from Vercel Labs (the state of Hermes Agent).
Seven weeks in, one independent tracker put its combined growth trajectory on par with LangChain and AutoGen's histories added together (Nous Research's self-learning runtime).
By the time this article was researched, the project had settled around 219,000 stars, 41,000 forks, and 346-plus contributors (the self-improving open-source guide).
What makes the Hermes story different from OpenClaw's isn't the growth curve—it's what the growth was built on.
OpenClaw is organized around a control-plane-first gateway and human-authored skills.
Hermes was architected from day one around a self-improving agent loop, treating every successful tool sequence as a candidate training trajectory for a lab whose actual business is models, not applications (Nous Research's self-learning runtime).
Hermes Agent is self-improving.
The longer you run it, the better it gets at understanding you and your workflow needs, using a variation of Genetic Algorithms.
That is something OpenClaw never had.
It wasn't just a patch on OpenClaw's security problems.
It was a different premise entirely, published by a team that had spent three years building open models before it ever shipped an agent to run them.
Does anyone actually remember how narrow Gemini Spark's first week was?
Google announced Spark at I/O on May 19, 2026, and opened it only to "trusted testers"—not a public beta, not even the full Ultra subscriber base yet (Gemini Spark tested in India).
The wider Ultra rollout followed later that same month, US-only.
On June 30, Spark reached the Gemini Mac app, alongside expanded connected-app support and custom MCP connections (Gemini Spark tested in India).
This month, it rolled out to AI Pro users as well at 20 USD a month (with reduced usage limits).
July 14 brought Chrome-native "auto browse," letting Spark control the desktop browser directly using logged-in accounts and saved passwords (Spark blocks EU and UK users).
Two days later, on July 16, Spark opened to Google AI Pro subscribers in the US for the first time—its first move outside the pricier Ultra tier (Spark no longer restricted to Ultra).
On July 29 and 30, Google extended Pro and Ultra access to more than 160 additional countries, including India, alongside Chrome-based booking and form-filling for everyday errands (Spark tested in India).
Even after that expansion, four regions stayed dark: the European Economic Area, the United Kingdom, Switzerland, and Nigeria—all still excluded as of early August, with no official reason published (Spark now runs on Chrome, Germany left out).
The timing is hard to ignore: Google signed the EU's AI code of practice in the same window that advertisers there began facing turnover-based fines, and Europe's regulatory posture toward autonomous agents remains visibly more cautious than the rest of Spark's rollout map (Spark blocks EU and UK users).
Even inside supported markets, Spark keeps guardrails active by default—it hands sensitive actions like payments or form submissions back to the user for confirmation through what Google calls "Take control" mode (Spark now runs on Chrome, Germany left out).
Where OpenClaw grew in an uncontrolled burst and Hermes grew in a fast, organic curve, Spark's story is the opposite of both: a deliberately metered expansion, tier by tier and country by country, from a company that watched what happened to the other two and chose caution as its actual product feature.
None of these are chatbot tricks.
Every use case below requires an agent that keeps working after you stop looking at it—which is exactly why they're the stories that made each product go viral in the first place.
1. Wake up to a booked calendar. One growth team reported going to sleep and waking up to 20 demos already booked, follow-ups sent, and campaigns still running on schedule—overnight lead generation that a human sales team simply cannot match hour for hour (OpenClaw use cases that'll make you rethink AI).
2. The executive morning briefing that assembles itself. A daily prompt—calendar, unread email, breaking news, weather, prioritized to-do list—runs overnight and is waiting in a single document before the first coffee (7 prompts that show what it can do).
3. A meeting turns into a tracker, an email, and a reminder—unattended. One prompt pulls action items from a meeting thread, builds a Sheets tracker with owners and deadlines, drafts the kickoff email, and schedules the follow-up, all before anyone opens their laptop.
4. Continuous price and deal monitoring that never sleeps. A single agent flagged a mispriced supercar on a listing site and surfaced deal alerts around the clock—the kind of arbitrage that only exists in the seconds after a price changes (5 autonomous tasks Hermes handles better).
5. Your coding agent gets its own manager. One developer built a bridge where Hermes writes prompts for Claude Code, reviews the output, and routes corrections back—an agent supervising another agent, continuously, without a human in the loop (15 real Hermes Agent use cases).
6. Invoices file, match, and queue themselves. A supplier email arrives; by the time anyone checks, it's filed, matched to the right budget line, and sitting in the payment queue (OpenClaw use cases that'll make you rethink AI).
7. Ad campaign reports land in Slack every Monday, on their own. An agent logs into the ad account, pulls the last seven days of data, formats it, and posts it—every week, without a standing meeting to make it happen (15 proven digital marketing applications).
8. A second brain that writes its own playbooks. After solving a hard deployment once, the agent writes a reusable skill file so the next deploy—days or weeks later—doesn't require re-explaining anything (Hermes Agent use cases).
9. Credit card statements audited for hidden fees, monthly, without being asked. A recurring trigger parses every new statement and flags new or hidden subscription charges before they compound.
10. One family, one subscription, one always-on agent. A user set up a single Hermes instance inside WhatsApp for three family members, replacing what would have been three separate $200 subscriptions—proactive, not just reactive, because it lives inside the app they already check (15 real Hermes Agent use cases).
11. Lead enrichment at scale, running while the sales team sleeps. An agent pulls a list of company names, searches LinkedIn and Crunchbase, extracts firmographic data, and writes it back to the CRM—continuously, not in a weekly batch (OpenClaw marketing use cases).
12. A memory bridge between your coding agent and your messaging agent. One developer connected Hermes, Claude Code, and Cursor to a shared knowledge base with hybrid search, so insight discovered in one tool is instantly available in the others (15 real Hermes Agent use cases).
13. Multi-channel intake for organizations with no IT department. NGOs, clinics, and small family businesses fielding phone calls, emails, WhatsApp messages, and paper forms get one system that centralizes all of it without hiring anyone (OpenClaw use cases that'll make you rethink AI).
14. Weekly research briefs delivered before the meeting they're for. A scheduled task builds a business brief from approved sources and has it reviewable and ready before anyone sits down to plan (10 best Gemini Spark use cases for business).
15. A content-gap scanner that works the whole news cycle. One agent scraped a competitor's channel, identified content gaps, and surfaced a story most outlets had missed entirely—running on a CPU instance costing 24 cents an hour, all overnight (5 autonomous tasks Hermes handles better).
16. Inbox triage that clears itself before you open your email. A recurring workflow sorts, labels, and drafts replies to routine messages continuously, so the inbox is already manageable by the time anyone looks at it (10 best Gemini Spark use cases for business).
17. Recurring compliance-style reporting delivered on schedule, not requested. A structured report gets rebuilt from the same approved sources every cycle and lands wherever it's needed without a standing calendar invite to make it happen (10 best Gemini Spark use cases for business).
18. Spending audited and categorized before the next statement even closes. Recent purchases get grouped, unusual charges get flagged, and savings suggestions appear automatically—continuous financial oversight nobody has time to do by hand (7 prompts that show what it can do).
19. Multi-agent fleets that outwork a single assistant. Some operators run four to ten specialized agents coordinating through shared databases at once—each covering a different function, all active simultaneously, something one human assistant physically cannot do (every OpenClaw use case I could find).
20. Procurement that runs itself from bid to margin calculation. A bid comes in, the agent reviews specs, ranks vendors by trust score, emails them, collects costs, and calculates margins—an entire back-office workflow completed before a human is looped in for approval (every OpenClaw use case I could find).
21. Cold outreach lists built and vetted while the team sleeps. The agent pulls prospects from Sales Navigator, HunterIO, and BrightData, vets them against an ideal customer profile, and has an organized, ready-to-send list waiting by morning (every OpenClaw use case I could find).
22. Health data analyzed the moment it syncs, with code the agent writes itself. One user exported Apple Health data and the agent wrote Python on the fly to calculate a sleep average—no developer, no manual analysis step (Hermes Agent user stories).
23. Social listening that never misses a post. Drop in session cookies and the agent pulls and summarizes dozens of posts in one command—continuous monitoring instead of a scheduled weekly export (Hermes Agent user stories).
24. Zero-friction OAuth onboarding for new integrations. Gmail and Calendar connect by dragging in a JSON file instead of a manual developer-console setup, cutting integration time from hours to seconds (Hermes Agent user stories).
25. Two agents, two roles, one shared source of truth. One agent acts as the CEO, another as the senior engineer, both reading and writing the same notes vault continuously, so nothing goes stale between sessions (Hermes Agent user stories).
26. One gateway, a different persona for every channel, all day. The same underlying agent runs a distinct personality and context in a work group and a separate community simultaneously, without cross-contaminating either conversation (Hermes Agent user stories).
27. PR reviews and monitoring alerts sent automatically, around the clock. Code review and system-health checks run as standing background jobs rather than tasks someone has to remember to trigger (Hermes Agent use cases).
28. Long-running workflows that survive server restarts and outages. A multi-day research or deployment job picks back up automatically after an interruption instead of losing all progress (Hermes Agent use cases).
29. One-off prompts turned into a standing research-draft-review pipeline. What started as a single content request becomes a repeatable three-stage workflow the agent runs unattended every time similar work comes up (Hermes Agent use cases).
30. Continuous CRM enrichment instead of a weekly batch job. New leads get looked up, enriched, and written back to the CRM the moment they arrive, rather than waiting for someone to run a manual export (OpenClaw marketing use cases).
And all this is just scratching the surface.
I could have listed 50 use cases and more roles, but this article is going to be really long already.
The common thread across all thirty (or even 100 use cases - use Generative AI chatbots and input your role and your Agentic AI Assistant of choice): every single one depends on the agent still being awake when the opportunity, the deadline, or the price change actually happens—not on you remembering to open an app and ask.
1. True 24/7 persistent cloud execution. Spark runs on dedicated Google Cloud virtual machines, not on your device—close your laptop and it keeps going (an agentic AI assistant).
2. Structured API integration. Spark connects to Gmail, Docs, Slides, and Sheets through real APIs instead of navigating rendered pixels, which makes its behavior more predictable than screen-based agents (Google's always-on AI agent).
3. The Antigravity harness underneath. Spark is the consumer face of Google's Antigravity agent platform, capable of running multiple sub-agents in parallel on long-held tasks—the same infrastructure developers reach directly through the Gemini API (Google's always-on AI agent).
4. Teachable, persistent skills. Describe a behavior once—distill your last fifty sent emails into a "ghostwriter" voice—and Spark builds a reusable skill that applies automatically going forward.
5. Recurring tasks and conditional triggers. Monthly invoices, hidden-fee scans on credit card statements, deadline flags—all handled without a calendar reminder from you (the Gemini app becomes more agentic).
6. End-to-end, cross-app workflows. One prompt can pull meeting action items from Gmail, build a Sheets tracker, draft a kickoff email, and schedule a follow-up—entirely chained (Google's always-on AI agent).
7. MCP-based third-party reach. Canva, OpenTable, and Instacart at launch, with more partners added through the Model Context Protocol in the following weeks (an agentic AI assistant).
8. An ask-first permission model. Google's own product page says Spark is "designed to ask you first" before spending money or sending emails, with app access off by default (Google's always-on AI agent).
9. A fast model-upgrade cadence. Spark launched on Gemini 3.5 Flash and was already running Gemini 3.7 Flash within roughly three months (our most intelligent workhorse model).
10. A governed enterprise path on the same rails. The identical model powering consumer Spark is also available through the Gemini Enterprise Agent Platform, so the personal-agent and enterprise-agent products share real infrastructure, not just a name (our most intelligent workhorse model).
1. A closed, self-improving learning loop. Hermes writes and refines its own skills from experience—a built-in learning loop no comparably-sized agent product currently ships (Hermes unlocks self-improving AI agents).
2. Deep cross-session memory. Agent-curated memory, periodic self-nudges to persist knowledge, FTS5 full-text recall, and Honcho-based dialectic modeling of who you are, built across every session (Hermes Agent documentation).
3. Contained, isolated sub-agents. Short-lived sub-agents handle parallel workstreams, each sandboxed with its own focused context and tools rather than inheriting the parent's full authority (Hermes unlocks self-improving AI agents).
4. Runs anywhere—not just your laptop. Six terminal backends: local, Docker, SSH, Daytona, Singularity, Modal. The serverless two hibernate at near-zero cost when idle (Hermes Agent documentation).
5. Twenty-plus messaging surfaces, one gateway. Telegram, Discord, Slack, WhatsApp, Signal, Matrix, Teams, Google Chat, and more, all fronted by a single process (Hermes Agent documentation).
6. Total model- and provider-agnosticism. Nous Portal, OpenRouter, OpenAI, Anthropic, or any compatible endpoint—no single lab's pricing decisions can hold the agent hostage (Hermes Agent documentation).
7. Natural-language cron scheduling. Describe a job in plain English and Hermes runs it unattended, fanning output to every connected platform at once (user testimonials).
8. Open-standard, portable skills. Compatible with the agentskills.io standard, so skills are searchable, shareable, and not locked to Hermes alone (Hermes Agent documentation).
9. MIT-licensed, self-hosted, no telemetry. All data stays on infrastructure you control, forever free, no cloud lock-in (Hermes Agent project page).
10. A built-in OpenClaw migration path. hermes claw migrate detects an existing OpenClaw installation and offers dry-run or secrets-free imports of settings, memories, skills, and API keys (the agent that grows with you).
1. Radical multi-channel reach. Native integrations across 30-plus messaging channels—WhatsApp, Telegram, Discord, Slack, iMessage, Signal, Matrix, Teams, LINE, Nostr, and more—out of the box (the complete OpenClaw guide).
2. A genuine runtime, not a library. Unlike LangChain, CrewAI, or AutoGen, which require writing code, OpenClaw installs and runs as a standing service you configure once (the complete OpenClaw guide).
3. The largest skill marketplace in the category. Over 44,000 community-built ClawHub skills at last public count, spanning browser automation, invoicing, file operations, and shell commands (OpenClaw statistics 2026).
4. Self-authoring skills on demand. Prompt OpenClaw to build a new skill it doesn't have, and it can write and register that capability itself (OpenClaw: the AI that actually does things).
5. Full local system access, sandboxed or not. File read/write, shell execution, browser control—operator's choice between full access and sandboxed mode (OpenClaw: the AI that actually does things).
6. Model-agnostic by design. Works with Anthropic, OpenAI, or fully local models, letting privacy-sensitive deployments keep everything on-device (OpenClaw: the AI that actually does things).
7. Persistent memory in plain Markdown. Agents track context in human-readable files rather than an opaque database, with proactive heartbeats checking in roughly every thirty minutes (10 powerful features).
8. A genuine nonprofit governance model. Development happens in the open under the OpenClaw Foundation, with a public SECURITY.md vulnerability-reporting process and community-reviewed pull requests (the agent that grows with you GitHub).
9. An enterprise security ecosystem grown around it. NVIDIA's NemoClaw layer adds sandboxing and access policies in one command; Airia adds a HIPAA-compliant gateway—third-party hardening at a scale no single vendor could build alone (OpenClaw statistics 2026).
10. Extended-stable releases with backported security fixes. Since mid-2026, a dedicated monthly release channel exists specifically to backport hardening without forcing operators onto bleeding-edge code (OpenClaw release notes August 2026).
Security becomes your job, because self-hosting shifts the entire operational burden onto whoever runs the instance, with no vendor SLA.
The open skill ecosystem carries real supply-chain risk, because an unreviewed skill economy is exactly what turned OpenClaw's marketplace into a target (agentic AI security risks).
Setup demands real technical literacy, because a curl install and a config file is a steeper curve than tapping a subscription toggle.
No native deep-Workspace equivalent, because Hermes leans on MCP and tool-calling rather than first-party structured Google APIs.
It's young, because a February 2026 release hasn't accumulated the years of adversarial pressure OpenClaw already survived.
No centralized admin console, because each deployment is its own island, with nothing resembling Spark's Workspace-wide AI control center.
A smaller skill ecosystem than OpenClaw's, because tens of thousands of community skills is a marketplace Hermes hasn't matched yet, whatever its quality edge (OpenClaw statistics 2026).
The desktop app is still a public preview, because the native macOS, Windows, and Linux client only shipped as preview software in June 2026 (the self-improving open-source guide).
Model-agnosticism cuts both ways, because reliability and output quality vary with whichever provider the operator wires up, unlike a single curated model.
The security benefits only hold if configured correctly, because OAuth with PKCE and dependency scanning protect nothing if an operator skips the setup step.
|
Dimension |
Gemini Spark |
Hermes Agent |
OpenClaw |
|---|---|---|---|
|
Hosting model |
Managed, Google Cloud VMs only |
Self-hosted anywhere: VPS, Docker, serverless |
Self-hosted, local-first, runs on your own machine |
|
Underlying model |
Gemini family only (now 3.7 Flash) |
Any provider—Nous Portal, OpenRouter, local models |
Any provider—Anthropic, OpenAI, local models |
|
Memory architecture |
Workspace-context-aware, cloud-resident |
Agent-curated + Honcho dialectic modeling |
Plain-Markdown persistent memory, periodic heartbeats |
|
Skill acquisition |
User-taught, natural language |
Self-authored from experience, portable |
Community marketplace (44,000+) plus self-authoring |
|
Tool surface |
Workspace APIs + 3 MCP partners at launch |
40–80+ built-in tools, full MCP support |
Browser, shell, files, 30+ channels, huge plugin base |
|
Governance |
Google, single vendor |
Nous Research, MIT license |
Nonprofit Foundation, OpenAI-sponsored, MIT license |
|
Data residency |
Google's infrastructure, by design |
Operator-chosen, fully controllable |
Operator-chosen, local by default |
|
Cost model |
$20-$100-$200/month AI Pro/Max/Ultra subscription |
Free software; infra from ~$5–100+/month |
Free software; infra and API costs from ~$5–100+/month |
|
Security track record |
No major public incident yet (young, beta) |
No major public incident yet (young) |
Severe, publicly documented, now actively remediated |
|
Extensibility |
MCP partners, Google-curated pace |
Open ecosystem, community skills |
Largest open ecosystem in the category |
|
Lock-in risk |
High—tied to Google's model and cloud |
Low—provider- and infra-agnostic |
Low—provider-agnostic, but plugin trust varies wildly |
Here's the truth most vendor comparisons dodge: self-hosting doesn't remove risk; it relocates it.
And OpenClaw's public history is the clearest proof of that principle this industry has ever produced.
Data residency and sovereignty.
Admin controls and centralized visibility.
The documented cost of getting this wrong.
Prompt injection and tool-poisoning risk.
Credential handling and secret sprawl.
Supply-chain risk in an open plugin ecosystem.
Shadow AI and unauthorized adoption.
What each vendor will actually commit to.
The honest read:
A regulated enterprise with existing Google contracts gets the most defensible ground on Spark.
A sovereignty-constrained organization with real security staffing gets defensible ground on Hermes.
An organization that wants the largest ecosystem and is willing to pay a specialist to wrap governance around it gets a workable, if scar-tissued, path through OpenClaw with NemoClaw or a comparable layer.
Gemini Spark requires Google AI Pro or higher subscriptions in the select countries where it is deployed at 20 USD a month, bundled with 20TB of storage and YouTube Premium rather than sold standalone (Google's always-on AI agent).
Genuinely good value if you already live inside Google's ecosystem; a harder sell if Spark is the only piece you want.
Hermes Agent flips the economics entirely—free forever under the MIT license, with operators running full instances on infrastructure costing roughly $5 a month, and serverless backends hibernating to near-zero cost when idle (Hermes Agent documentation).
OpenClaw sits in the same free-software category, with light users spending $5–20 a month on model API usage and heavy users exceeding $100, depending on configuration and hosting choice (what is OpenClaw guide).
But OpenClaw's real total cost of ownership for an enterprise almost always includes a governance layer on top—NemoClaw, Airia, or an equivalent—which turns "free software" into a genuine line item once you account for the security engineering it takes to run it responsibly at scale.
The honest accounting isn't just dollars.
Spark's $20 buys zero DevOps burden.
Hermes's and OpenClaw's near-zero infrastructure cost buys all of it back in operator hours—hours with real salary attached, even when the software itself is free.
Here's the twist nobody expects: if you can't run a capable local model, Gemini Spark's flat $20 a month can beat "free" software fast.
Local-LLM security is the hidden tax.
Capable local inference isn't free hardware either.
Now compare that to actual heavy-usage bills on the big four:
Put plainly: a power user who can't or won't run a local model, and who burns through serious token volume on Claude's or DeepSeek's metered API, can easily land north of $200–$500+ a month or more.
Spark caps that same appetite at $20–$200 flat, with zero GPU rental, zero Ollama hardening, and zero surprise invoices.
The difference between 20 USD, 100 US, and 200 USD is usage for Gemini Spark.
Higher tiers get more usage amounts than lower tiers.
However, the bill is still capped, unlike cloud models that can incur heavy costs.
A local LLM like Qwen 3.8 27B is still the best option - but it needs to be secured and hardened by an expert.
The moment self-hosting stops being genuinely free—because you need real hardware, real security, and real time—Google's flat fee for Spark quietly becomes the budget option, not the premium one, especially at current pricing.
Gemini Spark wins, because if your daily work already lives inside Gmail, Docs, and Sheets, nothing matches an agent that reads and writes those apps through real APIs instead of guessing at your screen.
OpenClaw wins instead the moment your life spans channels Google doesn't touch and you want the largest available skill marketplace to draw from.
Hermes Agent wins when you specifically want the self-improving memory loop and don't mind a younger ecosystem.
Hermes Agent wins, because open-source, self-hosted, provider-agnostic infrastructure with a genuine learning loop gives you control a closed, subscription-gated agent structurally cannot.
OpenClaw wins instead if you want the biggest plugin ecosystem and community momentum available today, and are comfortable auditing what you install.
Spark wins if you're building specifically on Google's own agent stack, where staying inside Google's rails buys tighter integration than any third-party agent could replicate.
Gemini Spark and Gemini Enterprise win for most regulated organizations, because Google's Workspace DLP, centralized AI control center, and compliance apparatus deliver exactly the vendor accountability that regulated data handling requires.
OpenClaw plus a governance layer like NemoClaw wins instead for enterprises that want the largest available agent ecosystem and are willing to pay a specialist to wrap real security controls around it.
Hermes Agent wins for the narrower category of enterprises legally barred from letting any external vendor touch their data at all, provided they staff the discipline to match.
Hermes Agent and OpenClaw win on the lowest possible cash floor, because free, MIT-licensed software on a $5-a-month VPS paired with DeepSeek's cheap metered API undercuts every subscription in this comparison—provided you're willing to do your own Ollama hardening rather than pay someone else for it.
Gemini Spark wins instead the moment you want a predictable ceiling rather than a metered bill that can silently climb past $200 a month on heavy Claude or ChatGPT usage; $19.99 buys real usage headroom with zero per-token risk.
OpenClaw edges out Hermes Agent specifically for budget users who need the largest free skill marketplace to draw from rather than pay a developer to build custom automations from scratch.
Gemini Spark is architecturally the better choice when you want an agent that simply works, backed by a company with the infrastructure and legal accountability to make that promise meaningful.
Hermes Agent is architecturally the better choice when you want to own every layer of the stack and value a genuine technical advance—the self-improving learning loop—that managed products haven't matched.
OpenClaw is, against all odds, still the category's most battle-tested option: it has been publicly broken, publicly fixed, and publicly reinforced by more independent security vendors than either of its rivals has yet attracted, precisely because it got hurt first and in front of everyone.
The questions worth asking yourself before choosing any of the three:
There is no fourth option that avoids these tradeoffs entirely.
I’ve given you the complete picture.
Now it is up to you to make an informed choice.
Three products.
Three philosophies.
One question underneath all of them that no benchmark table will ever answer for you: whose hands do you trust with standing access to the parts of your life that matter?
Gemini Spark bets that Google's scale and compliance machinery are worth trading full sovereignty for.
Hermes Agent bets that a self-improving, self-hosted agent you fully own is worth doing your own security homework for.
OpenClaw bets that the largest possible open community, tested in public under real fire, ends up safer than either alternative once the dust settles and the third-party governance layers catch up.
Choose the one that matches not just your workflow, but your appetite for responsibility—and your tolerance for finding out the hard way.
All the very best to you.
Cheers!
Google — Introducing Gemini 3.7 Flash
Google — The Gemini app becomes more agentic
Google — Gemini Spark product page
DataCamp — Gemini Spark: Google's Always-On AI Agent Explained
Nous Research — Hermes Agent official site
Nous Research — Hermes Agent Documentation
GitHub — NousResearch/hermes-agent
OpenRouter — Hermes Agent
Docker Hub — nousresearch/hermes-agent
Nous Research community — Hermes Agent user testimonials
Nous Research — hermes-agent.org project page
GitHub — openclaw/openclaw
Wikipedia — OpenClaw
OpenClaw — Official documentation
KDnuggets — OpenClaw Explained: The Free AI Agent Tool Going Viral
DigitalOcean — What is OpenClaw? Your Open-Source AI Assistant
Context Studios — The Complete OpenClaw Guide
Globussoft — 10 Powerful Features of OpenClaw AI Agents
TechTarget — The OpenClaw security risks every CISO needs to know
Conscia — The OpenClaw security crisis
OpenClaw Statistics 2026 — Growth, Users, Security, Data
GlobeNewswire — Airia Enables Enterprise-Grade Security for OpenClaw
Lyzr — Why OpenClaw Is the #1 Enterprise Wake-Up Call of 2026
IBM Think — What OpenClaw reveals about agentic AI security risks
CrowdStrike — What Security Teams Need to Know About OpenClaw
Google Workspace — Enterprise security controls for Gemini
Google Workspace Updates — Securely manage AI and agent access with the AI control center
AI Blew My Mind — OpenClaw Use Cases That'll Make You Rethink What AI Agents Can Do
Tom's Guide — I use Gemini Spark daily: 7 prompts that show what it can really do
MindStudio — 5 Autonomous Tasks the Hermes Agent Handles Better Than OpenClaw
BetterClaw — 15 Real Hermes Agent Use Cases (2026)
ALM Corp — OpenClaw Use Cases for Digital Marketing: 15 Proven Applications
Hostinger — Hermes Agent Use Cases: 10 Examples of What You Can Do
Improvado — OpenClaw Marketing Use Cases: 7 Automation Strategies
AI Agents Library — The 10 Best Gemini Spark Use Cases for Business in 2026
Graham Mann — Every OpenClaw Use Case I Could Find (85+)
Nous Research — Hermes Agent User Stories & Use Cases
Thomas Cherickal is an Emerging Technologies Educator, working as a Generative AI Consultant and a Quantum Computing Consultant based in Chennai, India, available for work globally, on a remote and asynchronous basis.
He has 500+ published articles across 10+ platforms covering AI, agentic systems, quantum computing, LLMs, Local AI, blockchain, Quantum AI, and other emerging technologies, for which he works as a consultant.
Skilled in Python and Rust.
Find his work at thomascherickal.com and thomascherickal.github.io.
Thomas writes for power users, developers, enterprises, and executive audiences on AI agent orchestration, enterprise AI deployment, local LLM deployment, quantum computing training and content, and emerging technology.
Available for technology writing engagements, technology training, and AI/quantum upskilling sessions for individuals, teams, and enterprises.
Connect on LinkedIn for a free introductory chat.
The first draft of this article was produced by Claude Sonnet 5.
All images in this article were AI-generated with Nano Banana Pro 2.
