Fifty Years After Xerox PARC, the Malleable Computer Exists

Fifty years after Xerox PARC's vision of a malleable computer, the combination of AI, an open operating system, and an AI-aware editor finally delivers on that promise, allowing users to reshape their computers conversationally without years of programming expertise.

TL;DR: Open system + AI colleague + AI-aware editor = the malleable computer Xerox PARC promised fifty years ago. Smalltalk bet the missing piece was a friendlier language; it was a colleague. Most mornings now, somewhere between the first coffee and the second, I sit down at my computer with a thought that begins: “Right Today I want to be able to…” Recently it was: kick off agent work in my editor, wander off to another workspace, and get tapped on the shoulder when the agent needs me. By mid-morning, my computer did the thing. Not an app that approximately did the thing, found after a search and a compromise. My computer, reshaped, doing exactly the thing. I want to convince you that this is not a productivity anecdote. It’s the arrival, fifty years late, of the most important idea in the history of personal computing, one we’ve been living in the shadow of the whole time. And it took an unlikely combination to get here: an AI, an operating system built by volunteers, and an editor that treats the two as colleagues. The idea we left behind at PARC In the 1970s, Alan Kay https://en.wikipedia.org/wiki/Alan Kay ‘s group at Xerox PARC https://en.wikipedia.org/wiki/PARC company built Smalltalk https://en.wikipedia.org/wiki/Smalltalk and the machine it lived on, the Alto https://en.wikipedia.org/wiki/Xerox Alto . Everyone knows what we took from PARC: the mouse, the windows, the bitmapped display, the desktop metaphor. Apple famously visited, saw the demo, and the next fifty years of interfaces descended from that afternoon. But the interface was never the idea. The idea was that the entire system was live and malleable. In a Smalltalk environment there was no wall between “using” and “programming.” Every object on screen could be inspected, modified, extended, while it ran . Kay’s Dynabook https://en.wikipedia.org/wiki/Dynabook vision was personal dynamic media, a computer you shape the way you shape an essay, not personal consumption media. We didn’t get that future. We got its screenshot. The industry took the Alto’s surface and shipped it on top of sealed systems where the user’s role shrank back to operator. Fifty years of windows and icons, running on machines philosophically opposed to what PARC was actually about. Why didn’t the real idea survive? Because malleability had a brutal price: expertise. Smalltalk bet that a sufficiently humane language would let ordinary people children, even reshape their systems. It was a beautiful bet, and it didn’t pay off at scale. Reshaping a computer remained the province of people willing to spend years learning how. So the industry, reasonably, sealed the machines and sold us polish instead. That price just collapsed. That’s the whole story. The missing piece was never a friendlier language. It was a colleague : one who has read every man page, never tires, and sits inside your editor. Pair an AI like Claude https://claude.com/ with an environment that is actually open to being reshaped, and the Alto’s bargain finally clears: malleability without the years of apprenticeship. The complexity doesn’t disappear; it becomes conversational. The rest of this post is what that looks like in practice, and how I stumbled into it. Twenty-two years in the walled garden I spent twenty-two years inside Apple’s ecosystem, and if I’m honest about the total the Macs, the iPhones, the upgrades, the peripherals, a music library built album by album, and the machines I bought for family along the way it’s many tens of thousands of dollars. And that’s just my own wallet; count the purchases I steered as the tribes designated computer person, and my economic footprint in Cupertino runs well beyond myself. I don’t say that with bitterness. For most of those years it was money well spent: beautiful machines, software that stayed out of my way, a promise of “it just works” that was largely kept. But somewhere along the line the deal changed. I came of age inspired by Steve Jobs. I know exactly how problematic he was, and the hagiography deserves every one of its asterisks. But the thing he understood, intuitively and completely, was that shareholder value is a trailing indicator of amazing products: delight the customer beyond reason, and the numbers follow. Tim Cook is a near-wizard in his own right, probably the finest operator of his generation. And under him the causality quietly inverted. The numbers became the product; delight became a line item. Services revenue, upgrade cadence, ecosystem retention: I could feel myself being optimised, and it killed the love. The premium I was paying stopped buying capability and started buying containment. I was renting a very nice room in a house whose walls I wasn’t allowed to touch, with a music library that made moving out feel unthinkable. Apple, ironically, took the Alto’s demo and built the most beautiful sealed boxes in history, and a sealed box, however lovely, can never be the Alto. So I left. Not in a huff; more like someone finally admitting the relationship had been coasting for years. Linux: still a pointy-elbow space Let me not romanticise where I landed. Linux in 2026 is dramatically better than its reputation, and also every bit as spiky as its reputation. It remains a pointy-elbow space. In my first months I debugged a Vulkan issue just to get my editor to launch. I’ve learned more about GStreamer codec plugins than any video hobbyist should need to. Wayland-versus-X11 is a sentence I can now say with a straight face. NVIDIA drivers are exactly the hazing ritual everyone warns you about; I now maintain a mental list of software that can’t initialize graphics on my card , and choose around it. I know what a race condition between desktop portals at login feels like. There were dark mornings where I stared at a terminal thinking: on the Mac, this would have just worked. And that’s true. It would have. But the pointiness and the power are the same property. Linux doesn’t hide its machinery, which means the machinery occasionally jabs you in the ribs, but it also means the machinery is there : exposed, documented, editable. Nothing is sealed. Every annoyance comes with a lid you’re allowed to open. This is the raw material the Alto idea needs: an environment made entirely of seams. Historically, the elbows were the price of admission. We’ll come back to what changed that. The stack For the curious, here’s where I landed, told as the story of a boot, because on Linux the boot is the story. The machine is Ubuntu https://ubuntu.com/ 26.04 LTS on an NVIDIA 580-series GPU driving an LG ultrawide. The NVIDIA card is the quiet villain of the whole setup: several components were chosen specifically because the obvious alternatives can’t initialize graphics on it. Told you about the elbows. The front door is greetd https://git.sr.ht/~kennylevinsen/greetd , a tiny login manager, launching a greeter that runs inside its own minimal Hyprland https://hypr.land/ instance and themes itself from my live desktop colours, so the login page and the desktop feel like one continuous thing. GNOME’s login manager is still installed, benched, as a fallback. All the console chatter that used to flash between login and desktop has been redirected into the system log, because I decided I didn’t want to see it. That sentence, because I decided , doesn’t exist on macOS. The compositor is Hyprland, On top of it sits choreography I’ve built myself: startup scripts that assemble my workspaces editor and terminals on 1, browser on 2, Signal and email on 3, the work-chat purgatory of Slack and Teams quarantined on 4 , window rules that pin misbehaving apps where they belong, and small daemons that quietly keep it all in line. The shell , meaning everything I actually see bar, launcher, notifications, clipboard history, control centre, wallpaper , is DankMaterialShell https://github.com/AvengeMedia/DankMaterialShell , a Material Design 3 suite built on Quickshell https://quickshell.org/ . It replaced a bar I hand-rolled in Quickshell, which itself replaced Waybar https://github.com/Alexays/Waybar , plus rofi https://github.com/davatorium/rofi and mako https://github.com/emersion/mako along the way. Colours flow from the wallpaper outward through matugen https://github.com/InioX/matugen , which generates a matching palette for the shell, the greeter, the terminal, and beyond. Change the wallpaper, and the entire machine re-dresses itself to match. The editor is Zed https://zed.dev/ : fast, GPU-rendered, refreshingly un-bloated, and, crucially, a speaker of the Agent Client Protocol https://agentclientprotocol.com/ , so Claude Code https://www.anthropic.com/claude-code runs inside it as a first-class citizen rather than a bolted-on chat panel. The same Claude is a CLI in my terminal: same binary, same memory, whichever surface I’m at. Zed happens to be my editor; any capable IDE will do. The point is the AI-as-colleague arrangement, not the brand. And the part that matters most: the entire configuration lives in a git repo at ~/dev/ricing , symlinked into place with GNU Stow https://www.gnu.org/software/stow/ : the dotfiles, the third-party package sources, even the /etc files for the login manager. A fresh machine could be rebuilt from it. Every experiment is a branch. My desktop has a commit history. Sit with that last bit for a second. My computing environment is version-controlled. I don’t have a desktop; I maintain one, the way you maintain a codebase, and I can fork it. The people at PARC would recognise this instantly, even if none of the tools would be familiar: it’s a system where the user is expected to reshape the system. Two mornings Abstract claims about malleability are cheap, so here are two real mornings. “Right Today I want to record and edit video on this machine.” Getting DaVinci Resolve https://www.blackmagicdesign.com/products/davinciresolve onto Linux was a gauntlet before it even launched: Blackmagic hides the download behind a form there’s an API trick to skip it , and the installer wouldn’t run under sudo until we forced Qt into offscreen mode. Then the real catch: the free version of Resolve won’t touch H.264 on Linux, the format OBS https://obsproject.com records by default, so the pipeline became OBS recording straight to DNxHR, a format Resolve actually eats. And once footage was flowing, the audio was visibly out of sync. Here is where having a colleague changes the shape of debugging. Instead of guessing, I simply sat in front of the camera and clapped. Claude took the recording apart: stepped through the frames to find the moment my hands met, pulled the audio track and located the transient spike of the clap, and measured the gap between them. The numbers pointed somewhere nobody suspected. Everyone’s instinct blamed the Bluetooth mic for lagging, but the audio was early ; the webcam’s “Use buffering” setting was delaying the video by ~300ms. The fix was disabling that, plus a measured −70ms mic offset in OBS. And the clap test became a repeatable calibration ritual: the hardware chain changes, I clap, Claude measures. Note the shape of that morning: every obstacle had a seam. OBS lets you change recording format. The installer can be coaxed. The latency can be measured, not guessed at. Nothing was sealed; it just needed navigating. “Right Today I want to kick off agent work in Zed, wander off, and get tapped on the shoulder when it needs me.” The whole point of an agent is that you don’t babysit it. But Zed’s own notification support missed events and, worse, yanked a window into focus when it did fire: exactly the interruption I was trying to avoid. So we went a layer down. The agent talks to Zed over a stdio protocol ACP , and we slotted a small wrapper into that pipe. It passes the stream through untouched, but watches for the messages that mean “the agent is waiting on a human” and fires a proper desktop toast: “Zed needs you.” Workspace-independent, so I can be reading feeds on 2 or suffering Slack on 4 and still know the moment my input is wanted, with nothing stealing focus. The obligatory gotcha: the custom agent entry in Zed’s settings had to be declared "type": "custom" , or Zed’s model picker would silently rewrite the config and wipe the wrapper out. The kind of thing you learn exactly once, which is why it went straight into Claude’s memory notes. Sit with what that second one actually is: I used Claude to rewire how Claude talks to my editor , by slipping a shim into an open protocol, while the whole arrangement was running. A system inspecting and modifying itself in flight. The Smalltalk people had a name for this. They called it using the computer. The three ingredients So here is the claim, stated plainly. The Alto’s promise needs exactly three things, and until very recently we’ve never had all three at once. The first is an environment made of seams. Linux can be reshaped in an hour precisely because it’s the pointy-elbow space. Everything is a file, which is exactly why my whole desktop can live in a git repo. Everything is scriptable. Every component assumes it will be composed with things its authors never imagined: nobody who wrote matugen, greetd, or Hyprland ever met, yet on my machine they behave like one product, because they all expose their seams. A sealed system can be pleasant, but it cannot be malleable. Malleability requires seams, and seams have edges. For thirty years, that was the trade: Apple sold the pleasantness, Linux kept the seams, and you picked your poison. The second is a guide through the complexity. This is what changed. Claude navigates the pointy space with me: it reads the logs, knows the arcana, remembers which config file governs what, and turns the elbows from a barrier into a texture. When I sit down with my morning “right, today I want…” , I’m not facing the complexity alone; I’m describing an intention to something that can help me carry it out against a system that permits it. The seams make the request tractable . The colleague makes it fast . The third is a place where they meet: an AI-aware IDE. A guide who can only talk is a phone-a-friend, not a colleague. When the AI lives in a browser tab, you become the courier, ferrying commands and error messages back and forth by hand, and the loop is too slow and too lossy for real reshaping work. An AI-aware editor dissolves that. Because Zed speaks an open agent protocol, Claude sits inside my working environment with the same view I have: the files, the terminals, the project. It doesn’t advise me on edits; it makes them, runs the result, reads the failure, and tries again while I watch or wander off. Zed happens to be mine; any IDE that treats the agent as a peer will do. And notice the recursion: the protocol that connects them is itself a seam. That’s what the notification shim exploited. Even the joint between colleague and environment is open to being reshaped. None of the three works without the others. AI bolted onto a sealed platform can only rearrange the furniture in someone else’s house; it hits the walls exactly where I used to. An open system without the guide is what Linux has always been: infinitely malleable in principle, expensively malleable in practice. And a guide with no hands on the environment reduces you to a go-between. Together, though, they close a fifty-year-old loop. My relationship with the machine has inverted: I no longer browse for software that matches my needs; I state my needs and the environment bends. Where this leaves me Twenty-two years and tens of thousands of dollars bought me computers that were finished. Polished, sealed, complete: someone else’s idea of done. What I have now is a computer that is never finished, and that’s the feature. It’s pointier, occasionally infuriating, and more mine than any machine I’ve owned. The folks at PARC saw all of this coming half a century ago; they just couldn’t have guessed that the missing piece would be a colleague rather than a language, or that the malleable machine would arrive wearing an odd operating system built by volunteers. But it’s here. And most mornings, I get to say “Right Today I want to be able to…” and mean it. Steve had a word for that feeling. It lives, not on the surface, but in the seams. PS. This morning it was “Right Today I want to be able to tell my story”