Adam Sitnik

@Aaronontheweb Yes, I am more or less trying to figure out what BCL is missing to provide great experience for writing TUI apps.

@SitnikAdam ahhh is this why you were asking me about TUI support in the BCL the other week?

If you ever needed PTY support in .NET, please share yur feedback in github.com/dotnet/runtime…

I'm thrilled to release CodeAlta - one of the first efficient AI coding-agent TUIs built entirely in C#/.NET 🚀 I've been developing and using it daily for the past 3 months, and I hope you enjoy it as much as I do! 🤗 Retweets are highly appreciated! 🙏 CodeAlta brings you a beautiful, colorful timeline interface, multiple threads in the same workspace, a real prompt editor experience, quick file viewing/editing with syntax highlighting, in-app model provider configuration, a multi-agent-ready environment, and much more! ✨

Finally! `unsafe` becomes safer! 😊 devblogs.microsoft.com/dotnet/improvi…

@brinkzapp In case of pipes, the end of the file (EOF) is reached when all handles to its write end have been closed. It works like that on every OS and programming language. And we provide APIs for reading from Pipes (FileStream/RandomAccess can read from any file including pipes)

@SitnikAdam No need auto close, more something intuitive like WaitForExit but for pipe instead of dispose or close, with ai writing us code, this will be yet another quirk in dotnet

There is one non-exciting thing about the Process improvements: I've left very little space for any further performance improvements. Especially for the synchronous methods ;)

#UCK26 | @lindseybroos is bringing one of the most underrated technologies in the .NET ecosystem to Update Conference Krakow. In her session, Lindsey will show why Microsoft Orleans deserves far more attention from developers building modern distributed systems. From the virtual actor model and built-in state persistence to scalability and developer-friendly architecture, Orleans simplifies many of the challenges teams face when building reliable cloud-native applications. With her strong background in .NET consulting, community leadership, training and real-world software development, Lindsey combines deep technical expertise with a practical perspective developers can immediately apply. If distributed systems, scalability and modern .NET architecture are topics you care about, this is a session you should not miss. 🎤 Learn more about the sessions: krakow.updateconf.net 💻 Watch live: now.updateconference.net 📍 27–28 May 2026, Krakow #UpdateConference #UpdateConferenceKrakow #dotnet #microsoftorleans #distributedsystems #cloudnative #softwarearchitecture #csharp

@LEGO_Group I am sorry to say that, but the BrickLink integration story is a failure. I've not integrated my old account, so it got DELETED and now once I registered a new one I can't even ask seller a single question?!

@brinkzapp We could use Close, but it's the same as Dispose. We have considered enabling auto-close by the .Start methods, but we would not be able to guarantee that all handles are closed when exception is being thrown (in this example between 1st and 2nd process gets started)

@SitnikAdam We are so used to be told that if you use using, then no need manual dispose, to have api require manual dispose call, have you consider to use different method name instead

@brinkzapp We do, in order to close the parent copy of given pipe end (otherwise EOF is not reported)

@SitnikAdam The brackets is noisy and do we really need to manually dispose like in the code sample?

@Aaronontheweb I am interested in TUI

@SitnikAdam the TUI stuff or the Apple Silicon issues?

Just dropped a new release of my Termina TUI library (Netclaw's TUI) - Fixed thread-safety issues that could cause NREs on Apple Silicon - Fixed UTF8 rendering in environments like the Visual Studio 2026 console (UTF8 might not be ready immediately) - Multiple SelectionList improvements v0.9.0 is hitting NuGet and I'm integrating it back into Netclaw to fix some crash issues during Netclaw init for Apple Silicon users. github.com/Aaronontheweb/…

@brinkzapp With the new API you can redirect the standard handles (including input) to anything (#redirecting-standard-handles" target="_blank" rel="nofollow noopener">devblogs.microsoft.com/dotnet/process…). We don't provide an API for creating a pseudo terminal yet.

@SitnikAdam Can i claude code non headless? Easily send stdin to interactive terminal ui ?

@davesmits @_h0x0d_ You mean the Process class? It predates me, but I was once told that the initial goal of Process API was to provide diagnostics information

@SitnikAdam @_h0x0d_ Why it's in the diagnostic namespace?

It's finally here! Process API Improvements in .NET 11 devblogs.microsoft.com/dotnet/process…

@jp_mikkers It was the most upvoted feature request. At the same time it was really hard to provide correct and optimal implementation for all Operating Systems that .NET supports.

@SitnikAdam Yay for the option to disable handle inheritance.

@nietras1 @Lucas_Trz No changes were made to Refresh. Could you please create a runtime issue with all the details?

@SitnikAdam @Lucas_Trz Are there any changes to process info e. g. process state? If I recall correctly Refresh() is very slow and we often had to turn to p/invoke due to no fine grained api for process info like memory use or similar.

@theo_albers @neuecc We had a very long discussion about the names, you can check youtube.com/watch?v=FLO5CX… to get the full picture.

@SitnikAdam @neuecc Great to see the elimination of deadlocks. The Run* methods somehow feel like they should have been called Start*, for consistency sake 🫢

.NET 11のProcess強化、ProcessXじゃないですかー。また先を行ってしまいましたか #process-gets-a-major-api-expansion" target="_blank" rel="nofollow noopener">github.com/dotnet/core/bl…

@Dave_DotNet Please follow github.com/dotnet/perform… for updates (I am not working on this particular feature, but asked offline the people who do).

Has anyone got any #dotnet 11 runtime-async benchmarks they can share please? FYI ... as of Preview 4 which was released yesterday runtime libraries are now compiled with runtime-async.

@xoofx Thanks a lot, I really appreciate it @xoofx !

@SitnikAdam Congrats and pretty cool and useful all these new APIs! Super welcome!

devblogs.microsoft.com/dotnet/process… Please share your feedback!

@torn_hoof I hope it will bring an end to the "file in use" problems ;)

@SitnikAdam Yay for ProcessStartInfo.KillOnParentExit, no more manual job object pinvoke