{"id":11575,"date":"2026-06-17T15:31:51","date_gmt":"2026-06-17T22:31:51","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/commandline\/?p=11575"},"modified":"2026-06-18T15:05:22","modified_gmt":"2026-06-18T22:05:22","slug":"intelligent-terminal-0-1-1-is-here-bash-support-new-slash-commands-and-customization","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/commandline\/intelligent-terminal-0-1-1-is-here-bash-support-new-slash-commands-and-customization\/","title":{"rendered":"Intelligent Terminal 0.1.1 is here: bash support, new slash commands, and more customization"},"content":{"rendered":"

We’re back with the first servicing release of Intelligent Terminal! This update brings auto error detection to Bash and WSL<\/strong>, a new \/fix<\/code> command for on-demand help, an on-the-fly \/model<\/code> picker, a customizable agent pane, and Windows 10 support, along with a round of bug fixes and reliability improvements.<\/p>\n

You can grab the update from the Microsoft Store<\/a>, via winget install Microsoft.IntelligentTerminal<\/code>, or by heading to the release page<\/a> on GitHub. Let’s dive in!<\/p>\n

Auto error detection and fix support comes to Bash and WSL<\/h3>\n

In 0.1, automatic error detection and fix\/command suggestions were limited to PowerShell. With this release, that same experience now works in Bash and WSL Bash<\/strong>. When a command fails, Intelligent Terminal picks it up and the agent can explain what happened and suggest or run the best fix, no matter which shell you’re in.<\/p>\n

\"wsl<\/a><\/p>\n

Introducing \/fix<\/code> \u2013 ask for a quick fix on demand<\/h3>\n

You no longer have to wait for auto-detection to get help with a failed command. The new \/fix<\/code> slash command<\/strong> in the agent pane lets you manually ask the agent for a fix to your shell output or error at any time, regardless of whether auto-detection or auto-fix is enabled or disabled.<\/p>\n

This is especially handy for the cases auto-detection can’t catch: commands that succeed but don’t actually do what you wanted. The exit code is clean, so nothing trips the error detector, but the result is clearly off. A few examples where you’d just type \/fix:<\/p>\n