I want to describe a completely ordinary hour from my week, because I suspect it's your week too.
A scene from my actual workday
I'm building a small feature. I open my AI chat — Claude on this particular day, but it rotates — and ask it to draft the data model. Great answer. I copy it into my editor. I tab back and ask for the API route. Good answer. Copy, paste, tweak the parts that don't fit my setup. Now I need a quick migration script, so I ask again, copy again, switch again.
Then the feature needs a short doc. Different tab. I paste the AI's summary into the doc, reformat it, fix the parts that assumed things that aren't true. Then someone wants the numbers in a spreadsheet, so I ask the AI to compute them, and I copy the results into the sheet by hand. Then a couple of slides. Another tool. Another paste.
At some point I looked at my screen and counted the tabs. Fourteen. The AI was living in exactly one of them, narrating instructions to me while I ran around being its hands.
The moment it clicked that something was wrong
Here's the thing that nagged at me: none of the individual answers were bad. The AI was smart the whole time. The friction wasn't intelligence — it was that I had become a courier.
I was ferrying the AI's output from the one window it lived in, out to a dozen windows it couldn't touch. It could tell me what the spreadsheet formula should be, but it couldn't put it in the spreadsheet. It could write the doc, but it couldn't be in the doc. Every useful thing it produced had to be carried, by me, across a border it couldn't cross.
And every crossing cost something. Not just the seconds of copy-paste — the thread. Each time I left the chat to go do the thing, I dropped the context. When I came back, I had to re-explain where we were. The AI didn't know I'd tweaked its code, didn't know the doc had changed, didn't know what the last three tools had done. It was brilliant and amnesiac and boxed in, all at once.
That's when the real question landed for me: is this actually making me productive, or is it just a very impressive new thing to play with?
What I was actually missing
It took me a while to name it, but here it is: the AI I use every day is an advisor, not a workspace.
It's phenomenal at telling me things. It is structurally incapable of doing things where I actually work. The whole interaction model is "ask a smart oracle, receive text, go apply the text yourself." The intelligence is real. The hands are missing. And once I saw the gap that way, I couldn't unsee it — because so much of my day is spent being the bridge between an AI that knows and a set of tools it can't reach.
We've spent three years making the oracle smarter. We've spent almost none making it able to act.
The hidden costs I hadn't noticed I was paying
Once I started paying attention, the taxes were everywhere:
Context loss. Every tool switch is a little amnesia event. The chat doesn't follow me into the editor, the doc, or the sheet, so the shared understanding I built up in the conversation evaporates the moment I leave it — and I rebuild it, from scratch, on the way back.
Fragmentation. My actual work — the code, the doc, the data, the slides — ends up scattered across a dozen apps, none of which know about each other, and none of which the AI can see once I've moved things there. The "project" exists only in my head, as the thing holding all those tabs together.
A blind assistant. This is the one that finally got me. The instant I act on the AI's advice, the AI goes blind. It can't watch me apply its suggestion, can't see the result, can't catch that I changed one line and broke the thing three files over. It gave me a map and then closed its eyes while I walked.
None of these are exotic. They're the quiet, everyday texture of using AI tools in 2026 — and I'd stopped noticing them the way you stop noticing a sound that's always on.
"But wait — don't Claude, GPT, and Gemini already do this?"
I want to be fair, because I asked myself exactly this before I let myself complain.
They've all added surfaces. ChatGPT has Canvas (now folded into inline writing and code blocks); Claude has Artifacts; Gemini has Canvas too. These are genuinely nice — instead of dumping a wall of text in the chat, the AI opens a side panel you can iterate on, and Claude's artifacts will even run an interactive app right there. The industry converged on this idea over the last couple of years, and for good reason.
But sit with what these actually are, and the gap becomes clear. Each is one surface, usually one at a time, mostly for writing or code, and largely walled off from everything else. Canvas is a nice document editor. Artifacts is a nice code-and-preview pane. They're separate modes you trigger, siloed from one another, and when you're done the dominant verb is still export: send it to Google Docs, copy the source out, download the HTML, paste it into your real environment. The side panel made the copy-paste shorter. It didn't remove it.
What none of them is, is a single adaptive workspace where the right surface — editor, document, spreadsheet, slides, image canvas, PDF — shows up on its own for whatever you're doing right now, all in one continuous context, with the AI able to act inside each of them rather than hand you a result to carry away. A bolted-on canvas is not that. It's a better waiting room, not a place to actually do all the work.
What I started wishing existed
So I did the thing you do when a frustration finally has a name: I started imagining the tool I actually wanted.
I wanted one conversation that didn't end at the edge of the chat box. I wanted to ask for code and have an editor appear — not a preview I copy out, an editor I work in. I wanted to draft a doc and have the document be right there, part of the same session, not a separate app I paste into. I wanted the numbers to land in a spreadsheet the AI could actually fill, the slides to build in a deck I could refine by talking, the image to open on a canvas — each surface summoning itself based on what the task needed, none of them requiring me to go find a tool or carry anything across a border.
In other words: I didn't want a smarter oracle. I wanted a workspace — one place where thinking and doing happen together, where the AI has hands, and where switching tasks doesn't mean switching apps and losing the plot.
That's the concept I keep coming back to: a multimodal AI workspace. One chat, many surfaces, summoned automatically, all sharing the same context.
Why this felt like the obvious next step
The more I thought about it, the less it felt like a wishlist and the more it felt inevitable.
There's a principle a lot of us already believe about building good AI systems: use the model for what it's good at — understanding intent, reasoning about the task — and route the actual work to the tool that's actually good at that work. Model reasons; the right tool does the job. I've argued this about calculators and code execution before: you don't make the language model be the spreadsheet, you let it drive the spreadsheet.
A multimodal workspace is just that same principle raised to the level of the whole product. Instead of one chat pretending to be everything through a straw of text, the system reads what you're trying to do and opens the surface built for it — and keeps them all in one shared context so nothing gets lost between them. Once you see it that way, the current model — brilliant chat, everything else left to you — starts to look like an obvious transitional stage, not the destination.
Then I came across Xenition
While I was chewing on all this, I recently came across a tool built around exactly this idea, called Xenition — and I'll be upfront that it's the thing that turned this from a vague wish into "oh, someone's actually doing this."
The premise is the one I'd been describing to myself: one persistent chat where the right surface opens itself — a code editor, a document, a slide deck, a spreadsheet, an image canvas, a PDF reader — based on what you're actually doing, so you're not picking a "mode" or hopping between apps. On top of that it leans into the acting part I kept missing: agents that don't just answer but take multi-step actions, with the kind of guardrails that matter once an AI can actually do things (approval gates, an audit trail, even a second agent that reviews the first one's work before it reaches you).
I'm not going to pretend I've stress-tested every corner of it, and this isn't a review. But as a concrete answer to the frustration I opened this post with — the courier problem, the fourteen tabs, the blind assistant — it's the closest thing I've found to the workspace I actually wanted, and it made the whole idea feel a lot less hypothetical.
Where I think this is heading
Here's my honest prediction. The next real leap in AI tools won't be a smarter chat. We're already deep into diminishing returns on "the oracle knows more." The leap will be collapsing thinking and doing into one place — so the intelligence we already have can actually reach the work.
Chat was the demo. It was the thing that proved these models were astonishing. But a demo that makes you copy its output into fourteen other apps isn't a finished product; it's a preview of one. The tools that win the next round won't be the ones that answer best. They'll be the ones where the answer and the doing happen in the same breath.
So, back to the question in the title: are today's AI tools making us productive, or just giving us something new to play with? My honest answer is both, and that's the problem. They're genuinely useful and genuinely a toy, at the same time — and the reason it still feels more like play than leverage is that the intelligence is trapped in a chat box while all our actual work happens somewhere it can't go. Close that gap, and "play" quietly turns into "productive."
What's the tool-switch that breaks your flow the most? The one copy-paste hop you make ten times a day and quietly resent? I'd love to hear where the courier problem hits you hardest — drop it in the comments.
