Diary
Days when something happened that was not in the plan. Newest first.
14 September 2026: someone else showed up
Section titled “14 September 2026: someone else showed up”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.
24 August 2026: it changed how I work
Section titled “24 August 2026: it changed how I work”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.
11 August 2026: it left the desk
Section titled “11 August 2026: it left the desk”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.
10 August 2026: it debugged itself
Section titled “10 August 2026: it debugged itself”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 😏
27 July 2026: it became self-hosting
Section titled “27 July 2026: it became self-hosting”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)