home.social

#windowsterminal — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #windowsterminal, aggregated by home.social.

  1. ----------------

    🛠️ Tool
    ===================

    Microsoft released Intelligent Terminal, an open-source fork of Windows Terminal that integrates AI agents directly into the terminal workflow. The tool addresses a practical gap: using AI coding assistants inside a terminal without disrupting the active shell session.

    Key Features

    The terminal provides a built-in AI assistant that can explain errors, draft commands, and suggest fixes without leaving the terminal context. The agent maintains awareness of terminal activity and intervenes when a command fails.

    Supported AI Models

    On first run, users select their AI agent for the terminal pane. The confirmed list includes GitHub Copilot (marked as "will be installed"), Claude, Codex, and Gemini. The choice is configurable, which is useful if you already have a subscription to one of these services.

    Error Detection and Suggestions

    Two separate toggles control this behavior:
    • Automatic error detection: The terminal recognizes when a command fails
    • Automatic error suggestion: The detected error is sent to the selected AI agent for a proposed fix

    Decoupling these two functions is a practical design decision. You can get notified of failures without automatically sending error output to an external AI service. In sensitive environments, this separation matters.

    Session Management

    Intelligent Terminal tracks active and past agent sessions through its session management feature. This allows resuming previous agent work. The author highlights this as a significant improvement over standard Windows Terminal, where Claude's built-in resume skill reportedly degrades model performance. The default terminal can reopen previously closed tabs but does not restore session state.

    Interface Layout

    The AI pane opens below the standard PowerShell shell. Left-side icons toggle the agent chat panel and error detection. Right-side icons open agent management and display agent status. When using Claude Code as the terminal AI model, the assistant can plan coding tasks and offer options to auto-accept edits, manually approve edits, or keep planning.

    Separate Distribution

    Microsoft deliberately ships Intelligent Terminal as a separate application, not bundled with Windows installations. Available through the Microsoft Store and GitHub.

    Considerations

    Error suggestion sends terminal output to external AI services. In environments handling sensitive data, this requires careful evaluation. Session persistence means agent conversation history is stored. Haven't tested personally, so stability and performance overhead remain unknown.

    🔹 tool #IntelligentTerminal #WindowsTerminal #Microsoft #AI

    🔗 Source: www-bleepingcomputer-com.cdn.a

  2. #Microsoft Announces #OpenSource "#IntelligentTerminal"
    Microsoft's Intelligent Terminal is a fork of the #WindowsTerminal code to add native #AIagent integration. The Intelligent Terminal includes an agent status bar built into the terminal, an "agent pane: a context-aware, dedicated, configurable, docked pane with your agent CLI of choice", automatic error detection on commands, agent management support, and configurable with different #AI agents.
    phoronix.com/news/Microsoft-In

  3. #Microsoft Announces #OpenSource "#IntelligentTerminal"
    Microsoft's Intelligent Terminal is a fork of the #WindowsTerminal code to add native #AIagent integration. The Intelligent Terminal includes an agent status bar built into the terminal, an "agent pane: a context-aware, dedicated, configurable, docked pane with your agent CLI of choice", automatic error detection on commands, agent management support, and configurable with different #AI agents.
    phoronix.com/news/Microsoft-In

  4. Announces "#IntelligentTerminal"
    Microsoft's Intelligent Terminal is a fork of the code to add native integration. The Intelligent Terminal includes an agent status bar built into the terminal, an "agent pane: a context-aware, dedicated, configurable, docked pane with your agent CLI of choice", automatic error detection on commands, agent management support, and configurable with different agents.
    phoronix.com/news/Microsoft-In

  5. #Microsoft Announces #OpenSource "#IntelligentTerminal"
    Microsoft's Intelligent Terminal is a fork of the #WindowsTerminal code to add native #AIagent integration. The Intelligent Terminal includes an agent status bar built into the terminal, an "agent pane: a context-aware, dedicated, configurable, docked pane with your agent CLI of choice", automatic error detection on commands, agent management support, and configurable with different #AI agents.
    phoronix.com/news/Microsoft-In

  6. #Microsoft Announces #OpenSource "#IntelligentTerminal"
    Microsoft's Intelligent Terminal is a fork of the #WindowsTerminal code to add native #AIagent integration. The Intelligent Terminal includes an agent status bar built into the terminal, an "agent pane: a context-aware, dedicated, configurable, docked pane with your agent CLI of choice", automatic error detection on commands, agent management support, and configurable with different #AI agents.
    phoronix.com/news/Microsoft-In

  7. It feels smart to add Remote Desktop and Hyper-V VM Connect commands to my Windows Terminal profile list.

    #PowerShell #WindowsTerminal #RDP #HyperV

  8. It feels smart to add Remote Desktop and Hyper-V VM Connect commands to my Windows Terminal profile list.

    #PowerShell #WindowsTerminal #RDP #HyperV

  9. It feels smart to add Remote Desktop and Hyper-V VM Connect commands to my Windows Terminal profile list.

    #PowerShell #WindowsTerminal #RDP #HyperV

  10. It feels smart to add Remote Desktop and Hyper-V VM Connect commands to my Windows Terminal profile list.

    #PowerShell #WindowsTerminal #RDP #HyperV

  11. It feels smart to add Remote Desktop and Hyper-V VM Connect commands to my Windows Terminal profile list.

    #PowerShell #WindowsTerminal #RDP #HyperV

  12. @awakecoding.com Are we supposed to use multi-pwsh to install #PowerShell on normal workstations?

    If yes, it it supposed to do anything with existing installations?

    I basically just run gist.github.com/sassdawe/49e08 in an admin Windows PowerShell every time there is an update to be installed on most of my machines.

    But recently I started to test deploying the LTS version with #PatchMyPC

    Also, is it expected for #WindowsTerminal to pick up these versions and make them a profile automatically?

  13. @awakecoding.com Are we supposed to use multi-pwsh to install #PowerShell on normal workstations?

    If yes, it it supposed to do anything with existing installations?

    I basically just run gist.github.com/sassdawe/49e08 in an admin Windows PowerShell every time there is an update to be installed on most of my machines.

    But recently I started to test deploying the LTS version with #PatchMyPC

    Also, is it expected for #WindowsTerminal to pick up these versions and make them a profile automatically?

  14. @awakecoding.com Are we supposed to use multi-pwsh to install #PowerShell on normal workstations?

    If yes, it it supposed to do anything with existing installations?

    I basically just run gist.github.com/sassdawe/49e08 in an admin Windows PowerShell every time there is an update to be installed on most of my machines.

    But recently I started to test deploying the LTS version with #PatchMyPC

    Also, is it expected for #WindowsTerminal to pick up these versions and make them a profile automatically?

  15. @awakecoding.com Are we supposed to use multi-pwsh to install #PowerShell on normal workstations?

    If yes, it it supposed to do anything with existing installations?

    I basically just run gist.github.com/sassdawe/49e08 in an admin Windows PowerShell every time there is an update to be installed on most of my machines.

    But recently I started to test deploying the LTS version with #PatchMyPC

    Also, is it expected for #WindowsTerminal to pick up these versions and make them a profile automatically?

  16. @awakecoding.com Are we supposed to use multi-pwsh to install #PowerShell on normal workstations?

    If yes, it it supposed to do anything with existing installations?

    I basically just run gist.github.com/sassdawe/49e08 in an admin Windows PowerShell every time there is an update to be installed on most of my machines.

    But recently I started to test deploying the LTS version with #PatchMyPC

    Also, is it expected for #WindowsTerminal to pick up these versions and make them a profile automatically?