From questions to delegation, the era of always-on agents

For three years we used AI the same way: one question, one answer. In 2026 that pattern is breaking, and I think it’s the most important change of the year, more than any leaderboard point.

Three signs of the same shift

The agent has a computer of its own. Open-source OpenClaw and Hermes were first to show that an agent can run continuously and take orders from a chat. Then came Grok Bot, ChatGPT dots, Meta Muse and, in October, Claude Duet: all with a cloud computer and browser that keep working when you close your laptop.

The agent takes the initiative. Claude Duet sends you a morning brief of what needs attention and checks again every few hours; Grok Bot messages you on its own when it finds something relevant; dots does “proactive research” when idle. They no longer wait for the question: they propose, and come back to you for approvals.

Agents work as a team. With Grok Bot you create several Bots, each with a role, memory and routines, and a main one coordinates them: you talk to one, they work in parallel. Anthropic is testing a mode to manage sub-agents from the app and Meta presented Muse Wonder, built for agents. The single assistant becomes a small organisation.

From “asking” to “delegating”

The shift is subtle but huge. When you ask, you check each answer before using it. When you delegate, the work goes on without you, and you see the result at the end (or an exception when something goes wrong).

It’s the same leap a professional makes going from working alone to having an assistant. And as with a human assistant, the questions change:

what can I hand over, and what not?
which data and tools should it access?
how will I notice if it makes a mistake?
who answers if the mistake reaches the client?

The bottleneck is trust

Today’s agents are good but not infallible. On Arena’s Agent leaderboard, built from millions of real sessions, even the best have margins far from perfection; and agent security (prompt injection above all) is an open problem.

That’s why I think over the next two years the difference between who gets value from agents and who doesn’t won’t depend on the chosen model, but on three very non-technological things:

Written processes. An agent can’t follow a procedure that exists only in your head. Organisations that have documented how they work will delegate much more.
Tidy data. Consistent folders, clear names, one version of each document. The agent is as fast as the mess allows.
Thought-through permissions. Who can read, who can write, who can send or pay. The same rules you’d give a new hire, applied to software.

The one-person company?

There’s a lot of talk about the “one-person company”: one person and a swarm of agents doing a company’s work. There are real, interesting examples, especially in software and content. But for most businesses I think reality will be more modest and more useful: the same team doing more and better, because repetitive tasks run in the background.

In a professional firm it means the invoice arrives, is read, proposed for logging and queued for review before anyone opens the inbox. The professional starts the day from the exceptions, not the pile.

What I’d do now

Start with one agent and one repetitive task: for example a Bot that prepares a weekly roundup of your field every Monday. It teaches you to delegate at low risk.
Write down your procedures, even briefly: they’ll become Skills and instructions for agents.
Connect tools gradually, read-only when enough.
Keep a human on irreversible actions, and design the check to be realistic.

In one line

The near future isn’t an AI that answers better, but an AI that works while you do something else. The question isn’t “which model?” but “what am I ready to delegate, and under which rules?”.

Sources

Informational content, current as of the date shown. Prices, models and rules change often: always check official sources. Written with the support of AI tools and reviewed by the author.