# The Personal Web

*First noted: August 2026 · Last revised: October 2026*

An agent can do far more than put together an answer in text.

When the agent runs on your machine or on a small VPS, nothing stops it from producing persistent artefacts. Not just text in a chat window: files, pages, tables, small applications. It writes them, rereads them and keeps them up to date.

From there, the agent can reconstruct surfaces. It can gather material, transform it, write a page, a dashboard or an app, and serve it at a private URL. You open it in your browser. It looks like the web, but it was assembled by the agent, out of material collected elsewhere.

This is the personal web: a web recomposed around the user's intentions.

The browser stops being only a window onto the outside web. It becomes a rendering layer for local reconstructions of the world.

## A web recomposed around intention

Two examples.

### A multi-criteria decision assistant

I want to go to South-East Asia. I don't know when.

The right time, for me, is not the one in a travel guide. It is the combination of five different signals: the weather has to be good, flights have to be cheap, my friend Ling has to be in the area, it has to fall outside my blocked work weeks, and it must not be high season on the two islands I care about.

No existing product can answer that question, because no product can know that particular combination. It exists only for me.

So I ask my agent to build me a surface that watches it. Not an alert: a dashboard, or a small app, that pulls these signals together and shows me where they converge. And perhaps that app will include a way to talk to Ling — or directly to Ling's agent — and to see Ling's calendar, if it is shared with me.

This is not a service I buy. It is a surface made for me, around my intention.

### Small surfaces for everyday life

Most of these surfaces are far more modest, and that is where they will first become ordinary. A parent asks for a page that brings together the week's school menus, the swimming pool timetable and the weather for Saturday, and opens it every Monday morning. Someone choosing a washing machine gets a table comparing three models on noise, energy use and the real cost of repairs, keeps it open until the purchase is made, then forgets it. On holiday, the agent puts together a small map of the bakeries open on Sunday morning around the rental. A runner sees the week's training plan next to the night's sleep, with the day's session adjusted when the night was short.

Some of these surfaces are disposable. Others become permanent and, over time, come to form a personal infrastructure for the user.

## A personal infrastructure

Extend the habit and a person accumulates a constellation of local surfaces, continuously regenerated: dashboards for decisions in progress, reading rooms for complex subjects, private observatories for the signals they watch, comparison spaces for purchases, living maps for projects, family interfaces that condense schedules and obligations.

Some could last for years. A health observatory combining sleep, test results, activity and medical records. A project observatory combining mail, documents, meetings and market signals into a single operational surface.

At that point the personal web becomes a zone of operational intelligence: a place where the outside world is selectively recomposed into a form the user can use directly.

## A new software primitive

Instead of shipping only complete, self-sufficient applications, developers will increasingly ship parts: capabilities, data access points, renderable modules meant to be recomposed by someone else's agent. Part of software remains a finished product. Another part becomes composable material.

This is already visible in commerce. Shopify publishes MCP servers so that a merchant's catalogue can be queried directly by an agent, and a set of web tools so that a page can expose its actions to an agent running in the browser. A shop is no longer only a shop window. It also ships callable parts.

The unit of value moves with it. It is no longer only the application as a closed object. It is the capacity to take part in an assembly you do not control. A service has value because agents can call it, interpret it, mix it with other sources and place it in a temporary personal environment.