GitHub Copilot CLI's redesigned terminal reaches GA as coding agents settle into the shell
GitHub Copilot's redesigned CLI is generally available, adding tabs, an in-session MCP registry installer, and theme-aware accessibility. The terminal is quietly becoming the shared home turf for Copilot, Claude Code, and Codex.
GitHub has moved the redesigned Copilot CLI terminal interface to general availability, trading a plain prompt for a tabbed, theme-aware workspace that installs tools without leaving the session. The update, which reached GA on June 23, is easy to file as a cosmetic refresh, but it lands in a more interesting context: the command line has become the shared home turf for the major coding agents, and how each one behaves in that window is now a real point of comparison.
What shipped
An interactive Copilot CLI session now opens with tabs across the top. Alongside a default session tab, developers working inside a repository get repository-scoped tabs for issues and pull requests, plus a gists tab, navigable by keyboard or mouse. The intent is to keep the context a developer is asking about inside the same window as the agent doing the work, rather than bouncing to a browser.
The tooling story is the more consequential part. Copilot CLI now handles setup in-session: /mcp add walks through a guided form for configuring a Model Context Protocol server, the open standard agents use to reach external tools, and /mcp search browses the GitHub MCP Registry to install one directly. Skills toggle with /skills, plugins install through /plugin, and /settings opens an inline configuration dialog. For a developer, that removes the usual friction of hand-editing a config file to wire up a tool, which is where a lot of MCP experimentation quietly dies.
GitHub also put real work into the interface itself. The redesign uses what it calls theme-aware semantic colors and responsive components that adapt to narrow terminals without truncating content, with screen reader detection and color modes that include a high-contrast and a colorblind option. Accessibility in a terminal agent is not a headline feature, but it is the kind of detail that decides whether a tool is usable for a whole team rather than most of it.
Where this lands in the market
The framing worth holding onto is that the terminal is no longer a fallback surface for coding agents; it is increasingly the primary one. Claude Code established the pattern of a capable agent living in the shell, Codex followed it into the CLI, and Copilot moving its own terminal experience to GA confirms the direction rather than setting it. The competition is shifting from “does this agent work in the terminal” to “how good is the terminal experience,” and that is where tabs, in-session tool installation, and accessibility start to matter.
For GitHub specifically, the CLI is also a distribution advantage in plain sight. Copilot reaches developers through an existing seat in most enterprises, and a terminal agent that installs MCP servers from GitHub’s own registry keeps that ecosystem gravity pointed inward. The practical shift for a working developer is that choosing a coding agent is becoming less about raw capability, which is converging, and more about which shell environment they want to spend their day inside.
What’s worth watching
The open question is whether interface polish translates into daily use or just a better first impression. Tabs and guided setup lower the barrier to trying MCP tools, but the tools themselves still have to be worth keeping, and a registry is only as good as what is in it. The signal to watch is whether the GitHub MCP Registry fills with servers developers actually run, or stays a demo surface.
The broader thread is convergence. As Copilot, Claude Code, and Codex land on similar terminal-native shapes, the differentiators move to model quality, tool ecosystems, and pricing rather than the interface. Over the next 90 days, the things to track are how the MCP registry grows, whether Copilot’s terminal usage rises against its IDE integration, and how the competing CLIs answer on accessibility and in-session tooling. Stackmaven’s follow-up coverage will land on or around October 10.