Series: Software that acts · Part 1 of 12
Software that acts: what software is becoming
Let us start with the basic idea in simple words.
Software moves from the tool you drive to the actor you supervise
Today, you open an application and you click: you fill in a form, you run a report, you check a table. You are the one driving.
Tomorrow, you will express an intent, for example "prepare the quarterly report and flag the gaps", and agents will carry it out by using the applications for you.
One word will come up more or less everywhere in this series: agent.
What is it?
The agent
An agent is a program that pursues a goal: it plans, uses tools, observes the result and starts again until it is done.
Think of an intern you hand a task to: they can only do what their access allows, and you review what matters.
Let us take the quarterly report request again, and look at who does what.
- You, you express an intention. "Prepare the quarterly report and flag the gaps." You say what you want to get, not how to do it.
- Agent, plans. It needs the figures for the quarter, the budget figures, then a comparison, and it chooses the order of the steps.
- Applications, provide the data. The agent reads the figures in the accounting system: it does not invent them, it fetches them where they are.
- Agent, produces the report. It compares, writes and flags three gaps above the threshold.
- You, you decide. You review, you decide on the gaps, and you remain responsible for what is sent.
In this example, nobody opened an application, but the applications have not disappeared for all that. They become systems of record, the place where trusted data lives, and a layer of agents does the work on top of them.
Now let us look at what changes, in practice.
Four things change
- From tool to actor. You no longer open an application to click: you say what you want, and agents carry it out.
- Intent becomes the source. Code can be regenerated, so what you keep and govern is the specification: the intent, the constraints and the criteria that say whether it succeeded.
- Software is also read by agents. A product that does not expose its capabilities to agents, through a protocol such as MCP (Model Context Protocol), will be bypassed or ignored. We will look at MCP in part 9.
- The human decides where it matters. Autonomy is set action by action, according to the risk, instead of putting fixed gates more or less everywhere.
All of this is moving fast. The research organisation METR measures the length of the tasks an agent manages to finish on its own: in its March 2025 measurements, that length doubled about every seven months.
If software becomes abundant, what becomes scarce?
Trust
Writing code is no longer what is scarce: what becomes scarce is being able to trust what acts.
So the human role concentrates on four things: deciding what is worth building, setting the constraints, making the important decisions, and remaining responsible for the result.
An agent can write an application in one hour. What then gains the most value?
Typing code faster
Not quite. Writing code is exactly what becomes abundant.
Knowing what to build, and being able to check that it is reliable
Right. Judgement and trust become the scarce resource.
Having many applications
Not quite. Many tools become temporary, and only the few systems that hold the trusted data count.
What does that change, depending on who you are?
For a small business, a large company, a developer
A small business can get custom tools without a development team, provided it knows how to describe precisely what it wants.
For a company present in several countries, the question is no longer only "which software should we buy?", but also "who is allowed to ask an agent for what, and how do we check it?".
For a developer, the job shifts: there is less code typed by hand, and more specifications, checks and guardrails.
It remains to be seen whether all this holds up in reality.
How I check it
Since 8 November 2026, I have been putting these ideas into my own projects, with one rule: every concept is learned by building it in a real project, not in a separate exercise.
In this series, I tell what I built, what it cost, and what did not work the first time.
What to remember
- Software is moving from a tool you drive to an actor you supervise.
- Applications do not disappear: they become systems of record, on which agents work.
- Being able to trust what acts becomes the scarce resource.
In the next part, we open the hood to see what an agent is made of.
Vision · Published on November 17, 2026Lire en français