When context keeps flowing, the unit of work shifts from file to conversation. Today we unpack this principle through Claude Code web and desktop sync.
Here's a familiar experience: an idea hits you on the subway, and by the time you reach home it's gone. I used to blame my memory. Turns out memory wasn't the issue. There was simply no vessel for the context.
This essay explains, from the start, why the unit of work has shifted from file to conversation. Even if you've never used an AI tool, you can follow along — we'll go slowly. Today's example is Claude Code's web-and-desktop shared session, but the principle applies to any tool. Three years from now the feature name will change. The spine of this essay won't.
Until now, "work" was a file. You made a document, saved it, emailed it, opened it again. Most Monday mornings were spent reopening the file you closed on Friday. The file lived on a desk. The desk lived in an office. Work was tied to a place.
But once you start working with AI, something strange happens. "Work" stops looking like a file and starts looking like a conversation. The file is only the output. The real work is the flow of dialogue that produced it. When the conversation continues, the work continues. When the conversation breaks, so does the work.
The trouble is — conversations are hard to "save" the way files are. A conversation carries the preceding context, what you just tried, the direction you abandoned, the option you're weighing right now. That's too much for a one-line memo. That's where this essay begins.
Losing ideas isn't laziness. You can use notes, voice memos, and apps and still lose them. Why?
Because each of them captures only part of the context. Voice memos capture sound. Notes capture words. Journals only make sense if you're the reader. But a living idea needs the state you were in when it arrived to survive. Strip away "what was I thinking about when this showed up?" and three lines of memo look like a stranger's writing.
Creators often misdiagnose this. "It's a focus problem." It isn't. It's a context-rupture problem. If three meetings interrupt a two-hour deep session, each rupture costs you fifteen minutes to rebuild the context. That's forty-five minutes you'll never get back. Which is why people who work with AI all end up saying the same thing: an unbroken flow is the precondition for depth.
Let's get concrete. A recent Claude Code feature lets web and desktop share the same session. The name doesn't matter. The behavior does.
On the subway you pull out your phone and throw Claude a question. "I have to write a blog essay. Rough out a structure for a topic like this." Claude returns a draft outline. You add a few opinions. You get off.
At the office, you open the desktop. The same Claude. The conversation from this morning is already there. "Take that structure and start the body." One sentence connects it. You don't re-explain anything. It already knows.
The point isn't "convenient." The point is that the unit of work has become the conversation. Change places, the conversation doesn't change. Change devices, the conversation doesn't change. Thirty minutes of commute plus two hours at the desk become one piece of work.
Picture your kitchen. You're cooking stew when the phone rings. Five-minute call, then you walk back in. The pot is still simmering. The ingredients are still on the counter. You pick up the ladle and stir once. The call didn't interrupt the cooking.
Now the opposite. You step out to take the call, and someone turns off the stove, cleans the pot, and clears the counter. You come back and start over. Mince the garlic, boil water, dissolve the paste. The same five minutes now feel like an hour.
Most of our old work environments were the second kitchen. Every device switch cleared the counter. Every place change turned off the stove. A shared conversation between web and desktop gives you the first kitchen — the one where the pot is still simmering.
Here's the aha.
Depth is not a quantity of time. It's the length of an unbroken flow.
Work eight hours with twenty ruptures and maybe two of those hours count as depth. Work five hours without rupture and all five count. Why does this matter? Because a creator's output is not proportional to time — it's proportional to flow.
Protecting flow needs two things. First, the will not to break it. Second, a vessel that can restore it if it breaks. Will alone isn't enough — you can't avoid the subway. That's why you need tools that let the conversation travel across places.
Try this.
A week of this and the feel arrives. The era of "work starts and ends at my desk" is over. Work starts in your head and ends somewhere. Cross three devices on the way — if the conversation stays one, so does the work.
So — what did we do today?
The unit of work moved from file to conversation. When conversation continues, context continues. When context continues, depth appears. Claude Code's web-desktop link is just one example of that. Whatever tool shows up next, the one that keeps context unbroken wins.
Three words to keep: Thought. Flows. Continues. Let thinking not be trapped in one device, let it flow between places, let it run through the whole day.
Three years from now, even if "Claude" is gone as a name, the principle still works. When you meet a new tool, ask: "Does this carry my conversation — or cut it?" That one question becomes your selection rule. Technology changes. The principle doesn't.