The desktop has been the centre of knowledge work since the advent of the PC. For decades, this is where thinking happens — where documents are written, spreadsheets are built, code is crafted, designs take shape. If you do knowledge work professionally, you sit at a screen. The work happens while you’re there. When you leave, it stops.
This is not an article about the death of the desktop. If anything, our tools have never been more capable.
Something, though, is shifting.
Taking software development as an example — as it’s seen the largest impact to date — something feels slightly off.
The desktop is still central
Today, the desktop remains where most knowledge work happens. For developers, this means the IDE. Most thinking, writing, and decision-making still happens there. Modern IDEs have never been more capable — autocomplete, inline diagnostics, integrated terminals, AI assistance built right in.
This needs to be acknowledged upfront. The desktop isn’t going anywhere soon.
Something feels different
Despite this, the rhythm has changed. More work happens around the desktop than inside it. Waiting is increasing:
- Builds running
- CI pipelines completing
- Deployments propagating
- Code reviews pending
- Async discussions unfolding
The desktop is excellent at doing. It’s less suited to waiting.
The question, not the answer
This raises a question worth sitting with:
When does the desktop stop being the centre of knowledge work?
Not “when does it disappear.” Not “what replaces it.” But: when is it no longer the most important place?
Work continues without you
The more powerful and autonomous our tools become, the more we shift from operators to reviewers. The less it makes sense to sit at a desktop waiting to be needed.
Work increasingly continues while you are away:
- CI runs overnight
- Agents generate changes
- Tests execute in pipelines
- Environments reconcile themselves
Work becomes something you check in on, not something that only happens while typing.
The desktop as intervention surface
The desktop shifts from:
- The place where everything happens
- To a place where you intervene
It becomes:
- An inspection tool
- A correction surface
- A decision checkpoint
Still critical. Just no longer central all the time.
Asynchronous agency
Long-running agents and automated workflows don’t replace knowledge workers. They create continuity between sessions.
The important change isn’t intelligence — it’s persistence. Work that used to stop when you closed your laptop can now continue, carefully, in the background.
This is worth noting without grand claims.
The shift in attention
The real change isn’t from desktop to chat, or local to cloud. It’s from:
- Continuous attention → intermittent supervision
Notifications, summaries, and diffs matter more than keystrokes. You’re notified, you assess, you decide, you move on. The skill is doing that well — without having been there.
Mobile as a signal
Working from a phone isn’t ideal. But it reveals something: if it works on mobile, it’s probably supervisory.
Mobile work shows what must remain central versus what can be checked remotely. It’s a clue about where the centre is moving.
Rejecting false binaries
This is not:
- Desktop vs Cloud
- Human vs AI
- Presence vs Absence
The future looks layered, not replaced. The centre moves temporarily, not permanently. Different modes of work overlap rather than exclude each other.
Where this leaves us
The desktop is still the centre — most of the time.
However, there are growing periods where it isn’t. Those periods matter disproportionately. They’re where continuity happens, where decisions compound, where work progresses without presence.
This raises questions about:
- How we design tools
- How we structure workflows
- Who is responsible for what
- What “being productive” even means
Software development is feeling this shift first. Other forms of knowledge work will follow.
What comes next
This is the first article in a series exploring these shifts. Not to predict or advocate, but to observe and name what’s already happening.
Upcoming themes:
- Long-running work and persistence
- Supervision versus execution
- Git as memory
- Chat as coordination, not creation
The centre doesn’t disappear. It moves. And it’s worth paying attention to where.