<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Bash | The .NET Blog</title><link>https://thedotnetblog.com/tags/bash/</link><description>Articles, tutorials and insights from the .NET community.</description><generator>Hugo</generator><language>en</language><managingEditor>@thedotnetblog (The .NET Blog)</managingEditor><webMaster>@thedotnetblog</webMaster><lastBuildDate>Mon, 29 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://thedotnetblog.com/tags/bash/index.xml" rel="self" type="application/rss+xml"/><item><title>Intelligent Terminal 0.1.1 Is Starting to Show What an AI-Native Shell Experience Could Look Like</title><link>https://thedotnetblog.com/news/emiliano-montesdeoca/intelligent-terminal-011-bash-fix-models/</link><pubDate>Mon, 29 Jun 2026 00:00:00 +0000</pubDate><author>Emiliano Montesdeoca</author><guid>https://thedotnetblog.com/news/emiliano-montesdeoca/intelligent-terminal-011-bash-fix-models/</guid><description>Intelligent Terminal 0.1.1 adds Bash and WSL support, a manual /fix flow, and on-the-fly model switching. It is still early, but the direction is becoming much more interesting for developers who live in the terminal.</description><content:encoded>&lt;p&gt;I still think AI in the terminal is one of the most promising developer experience areas right now.&lt;/p&gt;
&lt;p&gt;That is why &lt;strong&gt;Intelligent Terminal 0.1.1&lt;/strong&gt; stood out to me more than a typical point release normally would.&lt;/p&gt;
&lt;p&gt;This update adds:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Bash and WSL error detection&lt;/li&gt;
&lt;li&gt;a manual &lt;code&gt;/fix&lt;/code&gt; flow&lt;/li&gt;
&lt;li&gt;on-the-fly model switching&lt;/li&gt;
&lt;li&gt;a more customizable agent pane&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;That combination starts to make the product feel less like an experiment and more like an evolving shell experience.&lt;/p&gt;
&lt;h2 id="fix-is-the-right-kind-of-feature"&gt;&lt;code&gt;/fix&lt;/code&gt; is the right kind of feature&lt;/h2&gt;
&lt;p&gt;The addition I like most is probably &lt;code&gt;/fix&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;Why? Because not every problem shows up as a clean shell failure. Sometimes the command technically works and still gives you the wrong outcome. That is exactly where a manual “help me reason about this result” flow is useful.&lt;/p&gt;
&lt;p&gt;That is a much more realistic terminal assistance model than waiting for a perfect auto-detection mechanism.&lt;/p&gt;
&lt;h2 id="bash-and-wsl-support-make-the-experience-more-credible"&gt;Bash and WSL support make the experience more credible&lt;/h2&gt;
&lt;p&gt;Expanding beyond PowerShell was necessary.&lt;/p&gt;
&lt;p&gt;If this kind of terminal intelligence is going to matter to more developers, it has to work where developers actually spend time. Bash and WSL support is a big part of that.&lt;/p&gt;
&lt;h2 id="my-take"&gt;My take&lt;/h2&gt;
&lt;p&gt;This is still early-stage tooling, but the direction is good.&lt;/p&gt;
&lt;p&gt;The terminal is one of the most natural places for AI-assisted troubleshooting, command repair, and environment-aware guidance. Updates like this make that future easier to imagine.&lt;/p&gt;
&lt;p&gt;Original post: &lt;a href="https://devblogs.microsoft.com/commandline/intelligent-terminal-0-1-1-is-here-bash-support-new-slash-commands-and-customization/"&gt;Intelligent Terminal 0.1.1 is here: bash support, new slash commands, and more customization&lt;/a&gt;&lt;/p&gt;</content:encoded></item></channel></rss>