Skip to content

Diary

Days when something happened that was not in the plan. Newest first.


8 October 2026: the statue is already in the marble

Section titled “8 October 2026: the statue is already in the marble”

Today I added nothing big. I spent the day on a border, on the colour of a message, on how a link is written.

I have used this extension every day for more than two months, and I have always cared about how a thing is used. It took daily use to show me how much. An oddity you notice the first time and then ignore; by the hundredth you realise it costs you something every time. My own message that looked like a box to type in. An address a line long where acme/widgets#312 was enough. A whole path when all I needed was the name of the file.

And then the controls. I want to be able to copy anything: an answer, a block of code, a table, the output of a command. I do not want to look at a hundred buttons. So the button is everywhere and visible nowhere: it appears when I point at the thing, which is the moment my hand is already going there. The same for the cross that removes an attachment, for the arrow that opens a row. The gesture brings the tool, and when the gesture is over the tool is gone.

None of these is a feature. None would make an announcement. They are still what decides whether you open a tool gladly or put up with it. That is what ergonomics means to me: not having to think about the interface while I work.

They say the statue is already inside the block of marble, and that all it takes is removing the pieces that are too many. An interface is the same. You do not add until it is beautiful: you use it long enough to see what is too much, and you take it away.

This started as a personal project: I wanted a better Claude Code integration in Visual Studio 2026, so I built one. Then, in a single day, a wave of pull requests arrived from Andrii Chebukin, enough that most of what 1.10.0 shipped came from someone I have never met.

What surprises me is not that someone showed up: it is how. The professionalism, and the quality of the code: contributions I would have been glad to have written myself, from someone with no stake in this beyond wanting it to be better.

I have been around open source for years and I still believe this: there is no other way to build things that are good and big. Not one person, however stubborn: people who have never met, working on the same thing because it is worth doing.

Not a milestone of the project: one of mine. Using this inside Visual Studio 2026 did not just make me faster: it unlocked ways of working I could not have had from the outside with VS Code. Step-by-step debugging, Hot Reload, the whole IDE: driven by the agent rather than described to it.

My client projects felt it first. Timelines contracted, and the people I work with noticed before I said anything.

When a tool changes the way you work, that is the sign it matters. Most don’t. This one did.

The CLI had Remote Control, VS Code had it, Visual Studio didn’t; so a session started here stayed where it started, and this is where I work. Now it doesn’t: I scanned the QR and kept the session going from my phone while setting up the Fiera di Santa Maria in Calcinatello, the village fair I help run every summer. The projects keep moving. I don’t have to be at the keyboard for all of it.

Claude hit a bug, set a breakpoint through the extension’s own MCP tools (in the very Visual Studio instance hosting the pane it was typing into), stepped through the live process, read the locals, found it, fixed it. The debugger was inspecting the program that was running the debugger. It worked, which was somehow the surprising part. I mostly watched. Almost as good as me 😏

The extension is developed inside itself: no VS Code, no external terminal, no other editor; the Chat and CLI panes in the README’s screenshots are the ones writing the next version. Which is also the toughest test there is: every rough edge turns up in the day’s work, not in a bug report.


Daniele Corsini (Frank Lupo)

Back to Why