Skip to main content

Microsoft Brings AI Agents Directly Into the Windows Terminal

AI agents, SRE
AI agents, SRE

Microsoft just shipped Intelligent Terminal 0.1 — an open-source, experimental fork of Windows Terminal with native agent integration built in. It’s available now from the Microsoft Store or via WinGet (winget install Microsoft.IntelligentTerminal), and it installs alongside your existing Windows Terminal without replacing it.

This is an early release, clearly labeled as experimental. But it’s a meaningful signal about where Microsoft thinks the terminal is going.

What it Actually Does

The core idea is straightforward: Instead of copying an error message, opening a browser, hunting through Stack Overflow, and then jumping back to your shell, you stay in the terminal. An AI agent is right there, aware of what’s on your screen.

Intelligent Terminal adds a persistent agent pane — a docked, context-aware panel where you can interact with an AI agent CLI without leaving your workflow. GitHub Copilot CLI is the default, but the architecture is open. Any Agent Client Protocol (ACP)-compatible agent works, including custom or local agents. If it’s installed on your PC, Intelligent Terminal will detect it.

The agent pane is toggled with Ctrl+Shift+. and stays out of the way when you don’t need it. You can ask it to explain an error, follow up with additional context, and it keeps the thread going. If the agent needs to run multiple or complex tasks, it spins up background tabs so your active shell stays focused.

Automatic Error Detection

When a command fails, an indicator appears in the agent status bar at the bottom of the window. Clicking it opens the agent pane with the error context already loaded. From there, the agent can explain what happened and suggest or run a fix. You can configure the tool to just flag errors, or to automatically suggest fixes as well.

It’s a small quality-of-life improvement that adds up quickly for anyone who spends hours a day in the terminal.

Managing Multiple Agents

If you’re running agents across multiple tabs or background tasks, keeping track of them has historically been a pain. The new agent management panel gives you a view of all active agents and their status, plus past sessions you can return to. You can pick up where you left off, check on a long-running task, or dismiss completed ones.

The Command Palette also gets an agent entry point. Type ? followed by your prompt and the terminal injects context from the active pane, then runs the agent in a background tab so your shell isn’t interrupted.

Why This Matters for DevOps Teams

The broader pattern here is worth noting. Developers are already using AI agents in their workflows — they’re just doing it awkwardly, with constant context-switching between tools. Intelligent Terminal is an attempt to reduce that friction by putting the agent where the work actually happens.

Mitch Ashley, VP and practice lead for software lifecycle engineering and AI-native software engineering at The Futurum Group, sees this as a strategic move with real competitive implications. “Intelligent Terminal positions the terminal as a viable agent surface on Windows, with the open Agent Client Protocol preserving developer choice at the agent layer while Microsoft owns the surface integration,” he said. “The agent-aware terminal becomes the default developer surface for AI-assisted work on Windows, narrowing the space for standalone AI developer tools and forcing competing platforms to ship an equivalent native experience or cede the developer surface entirely.”

That’s a significant observation. By embedding agent support at the terminal level and keeping the agent layer open via ACP, Microsoft gets the best of both worlds — platform control without locking developers into a single AI provider.

What’s Next

Microsoft says the Intelligent Terminal will be built based on community feedback, and the GitHub repository is open for issues and feature requests. Given that this is version 0.1, expect a lot to change. The foundation is there, but the experience will depend heavily on how well the team listens and iterates.

The team is deprecating Terminal Chat in Windows Terminal Canary with this release, signaling a shift in direction. If you don’t want an agentic terminal experience, nothing changes for you in mainline Windows Terminal. But for teams already leaning into AI-assisted development, this gives them a more native place to do it.

For DevOps engineers and developers who spend significant time in the terminal, it’s worth installing and testing. The friction reduction alone — from error detection to agent context — could make a real difference in daily workflows.

You can install it directly from the Microsoft Store or follow the project on GitHub.



from DevOps.com https://ift.tt/6a0vOTg
Labels:

Comments

Post a Comment

Popular posts from this blog

Cursor’s New SDK Turns AI Coding Agents Into Deployable Infrastructure

For most of its life, Cursor has been an IDE. A very good one. But with the public beta of the Cursor SDK, the company is making a different kind of move — one that should get the attention of DevOps teams. The Cursor SDK is a TypeScript library that gives engineers programmatic access to the same runtime, models, and agent harness that power Cursor’s desktop app, CLI, and web interface. In short, the agents that used to live inside an editor can now be invoked from anywhere in your stack. That’s a meaningful shift in how AI coding tools fit into software delivery pipelines. From the Editor to the Pipeline If you’ve used Cursor before, the workflow is familiar — you interact with an agent in real time, asking it to write functions, fix bugs, or review code. The SDK breaks that dependency on interactive use. Now you can call those same agents programmatically, from a CI/CD trigger, a backend service, or embedded inside another tool. Getting started is a single inst...
Post a Comment
Read more

Mistral Moves Coding Agents to the Cloud — and Gets Out of Your Way

For the past year or so, AI coding agents have been tethered to your local machine. You kick off a task, watch the terminal, and babysit every step. It works — but it’s not exactly hands-free. Mistral just changed that. On April 29, the Paris-based AI company announced remote coding agents for its Vibe platform, powered by a new model called Mistral Medium 3.5. The idea is simple: Instead of running coding sessions on your laptop, they now run in the cloud — asynchronously, in parallel, and without you watching over them. What’s Actually New Coding sessions can now work through long tasks while you’re away. Many can run in parallel, and you no longer become the bottleneck at every step the agent takes. That’s the core pitch. You start a task from the Mistral Vibe CLI or directly from Le Chat — Mistral’s AI assistant — and the agent handles the rest. When it’s done, it opens a pull request on GitHub and notifies you, so you review the result inste...
Post a Comment
Read more

GitHub Resets Copilot Pricing as AI Compute Costs Surge

The development community saw this one coming: GitHub will transition its Copilot service to a usage-based billing model on June 1, replacing its existing system of fixed subscriptions supplemented by premium request limits. As reported last week, GitHub suspended new sign-ups for several of its Copilot subscription tiers as it faced a surge in demand from agentic coding workflows. To address that, under GitHub’s new pricing model, customers across individual, business, and enterprise tiers will receive a monthly allocation of AI credits, which are consumed based on token usage. This includes input, output, and cached data processed by underlying models. Once those credits are exhausted, users can purchase additional capacity at published rates. The change leaves base subscription prices intact. Individual plans remain priced at $10 per month for Pro and $39 for Pro+, while business and enterprise tiers continue at $19 and $39 per user per month, respectively. Each plan’s monthly ...
Post a Comment
Read more