GitHub Copilot CLI Gets Tabs and No-Config-File Tool Setup in Redesigned Terminal UI
Mark Silvester · rss · 2026-07-10 Reader 🖥️
Agent SkillsAgent Tool ManagementCoding AgentsDeveloper Experience & FlowMCP (Model Context Protocol)
GitHub has made Copilot CLI's redesigned terminal interface generally available, adding tabbed in-terminal browsing of GitHub issues, pull requests and gists, guided in-session configuration of MCP servers, skills and plugins that removes the need to hand-edit config files, and accessibility-focused theming — consolidating the terminal into a self-contained, extensible surface for agentic development.
practical · expository — A short product-update news report describing a shipped release of GitHub Copilot CLI's redesigned terminal interface. Almost entirely expository (feature enumeration), but it carries an implicit argumentative undertone about where agentic-CLI tooling is heading: the terminal absorbing IDE-grade UX and treating skills/MCP/plugins as first-class, config-free extension surfaces.
Structure
| Part | Role |
|---|---|
| Lede: GA announcement | States that the redesigned terminal interface (previously experimental behind /experimental since Microsoft Build 2026) is now generally available, and previews the three headline changes: tabs, in-session tool config, cleaner/accessible UI. |
| Tabs and GitHub-object browsing | Describes the tabbed layout (Session, Gists, plus repo-scoped Issues and Pull requests) and the keyboard/mouse actions to reference (c), open (o), and search (/) items. |
| In-session tool configuration | Describes /mcp add and experimental /mcp search (GitHub MCP Registry install, no restart), /skills, /plugin, and /settings — replacing config-file editing with guided in-session forms. |
| Accessibility and readability | Describes theme-aware semantic colours, responsive non-truncating layout, /theme modes (default/dim/high-contrast/colorblind), and automatic screen-reader support. |
| Release history and how-to | Situates the update against Copilot CLI's own February 2026 GA and tells users how to update (copilot update) and give feedback (/feedback). |
Key terms
- Copilot CLI / agentic CLI
GitHub's command-line coding agent that works with GitHub directly from the terminal, now with a full terminal UI (TUI) layered over the agentic loop. - redesigned terminal interface (TUI)
A tabbed, mouse-and-keyboard, theme-aware, responsive text UI rendered inside the terminal — effectively an IDE-like workbench in a shell. - MCP servers / GitHub MCP Registry
Model Context Protocol servers that extend the CLI's tools; the GitHub MCP Registry is a browseable catalogue from which servers are installed in-session (via /mcp search) and become available immediately without a restart. - skills Agent Skills
Individually toggleable capability modules managed via the /skills command. - plugins
Installable extensions sourced from a marketplace, a repository, or a local path via the /plugin command. - no-config-file / in-session configuration
A guided, interactive-form workflow for adding tools and changing settings that removes the need to hand-edit configuration files. - theme-aware semantic colours / screen-reader support
Accessibility affordances: colour roles that adapt to the terminal theme, selectable colour modes (/theme), and auto-enabled screen-reader mode with labelled icons and disabled animations.
Propositions
- explicitCopilot CLI's redesigned terminal interface, previously available experimentally behind the /experimental flag since Microsoft Build 2026, is now generally available.conf: highsupportsGitHub Copilot CLI Reaches General Availability · p7 — This further GitHub investment in the AI-terminal experience is additional evidence for the GA doc's claim that the AI-powered CLI market is converging with major players investing heavily.
- explicitAn interactive Copilot CLI session presents tabs across the top — a default Session tab, a Gists tab, and, when run inside a repository, Issues and Pull requests tabs scoped to that repo — navigable by Tab key or mouse and reorderable/hideable.conf: high
- explicitDevelopers can act on GitHub issues and pull requests without leaving the CLI: pressing c drops a reference into the prompt (to investigate/fix/comment/review), o opens the item in the browser, and / runs a custom GitHub search.conf: high
- explicitConfiguring the tools that extend Copilot CLI is now a guided, in-session experience that removes the need to hand-edit configuration files.conf: high
- explicitMCP servers can be installed in-session via /mcp add (interactive form) or the experimental /mcp search (browse the GitHub MCP Registry), and newly added servers are available immediately without restarting the CLI.conf: high
- explicitSkills, plugins, and settings are each managed in-session through dedicated commands: /skills toggles individual skills, /plugin installs plugins from a marketplace/repo/local path, and /settings opens an inline configuration dialogue.conf: high
- explicitThe interface treats accessibility and readability as first-class concerns: theme-aware semantic colours, responsive components that adapt to narrow terminals without truncating content, a /theme command (default/dim/high-contrast/colorblind), and screen-reader support that turns on automatically when a screen reader is detected.conf: high
- implicitBringing GitHub objects (issues, pull requests, gists) into the terminal reduces the need to switch to a browser and keeps developers working in a single surface.conf: highsupportsGitHub Copilot CLI Reaches General Availability · p6 — Tabbed in-terminal browsing of issues/PRs/gists is a concrete new mechanism for the GA doc's claim that reducing context switching between terminal and browser preserves flow state.
- implicitReplacing config-file editing with guided in-session forms lowers the friction and onboarding cost of extending an agentic CLI, making its tool surface more discoverable.conf: high
- implicitSkills, MCP servers, and plugins are the assumed standard extension mechanisms for an agentic CLI — the tool now treats them as first-class, built-in configuration surfaces rather than optional add-ons.conf: highsupportsThis Week's Best Developer Tools & Betas · p5 — GitHub Copilot CLI now shipping first-class /mcp, /skills and /plugin support is evidence for 'extension mechanisms are table stakes for an agentic IDE'. Term mismatch: the referenced prop names skills/MCPs/hooks; this doc ships skills/MCP/plugins (no hooks) — the edge is on the table-stakes thesis, not a 1:1 triad match.
- implicitThe trajectory of agentic-CLI tooling is toward richer, IDE-like in-terminal experiences — tabs, panels, inline settings dialogs, object browsing — rather than minimal prompt-only interfaces.conf: medium
- implicitA vendor-curated registry (the GitHub MCP Registry) is the intended discovery-and-install mechanism for agent tools, positioning GitHub as a distribution hub for MCP servers.conf: mediumextendsGitHub Copilot CLI Reaches General Availability · p1 — Broadens the GA doc's 'terminal is the next critical surface deserving first-class AI integration' into a stronger claim: the terminal is becoming an IDE-like workbench (tabs, settings dialogs, object browsing), not just a prompt.
Arguments
The redesign makes Copilot CLI a more capable, more self-contained developer surface. strength: medium
Explicit premises:
- Tabs bring repo-scoped Issues, Pull requests and Gists into the session with keyboard/mouse actions to reference, open, or search them.
- In-session guided forms replace hand-editing of configuration files for MCP servers, skills, plugins and settings.
- Accessibility and readability improvements (theming, responsive layout, screen-reader support) broaden who can use it.
Implicit premises:
- Developers prefer to stay in the terminal, so reducing context switches to the browser improves flow and productivity.
- Lower setup friction increases adoption of the CLI's extension mechanisms.
- A terminal can host IDE-grade UX (tabs, settings dialogs, object browsing) without losing its speed/simplicity advantages.
Inferences:
- Consolidating GitHub browsing, tool configuration and theming into the CLI therefore raises its value relative to editing config files and switching to a browser.
An agentic CLI should natively support MCP servers, skills and plugins as configurable, discoverable, config-file-free surfaces. strength: medium
Explicit premises:
- The CLI now ships /mcp add, /mcp search (GitHub MCP Registry), /skills, /plugin and /settings as in-session commands.
- Newly added MCP servers are available immediately without restarting the CLI.
Implicit premises:
- Skills/MCP/plugins are the standard extension model for coding agents.
- Hand-editing configuration files is a friction barrier worth engineering away.
- A curated registry is the right discovery mechanism for agent tools.
Inferences:
- Therefore making these extension surfaces first-class, in-session and registry-installable is the correct direction for the tool.
Narratives
- Highlighting an issue or pull request in a tab and pressing c drops a reference into the prompt so Copilot can be asked to investigate, fix, comment on, or review it; pressing o opens it on GitHub in the browser, and / searches GitHub with a custom query.
→ A concrete usage scenario that makes the abstract 'work with GitHub without leaving the terminal' claim tangible, implicitly supporting the reduce-context-switching / single-surface proposition.
Questions addressed
- ✅ How can developers extend an agentic CLI with tools without hand-editing configuration files?
Guided in-session commands: /mcp add and /mcp search (registry install, no restart), /skills, /plugin, and /settings. - ✅ How can developers act on GitHub issues/PRs/gists without leaving the terminal for the browser?
Repo-scoped tabs with keyboard/mouse actions to reference (c), open (o), and search (/) items. - ✅ How can a terminal-based AI tool be made accessible and readable?
Theme-aware semantic colours, responsive non-truncating layout, /theme colour modes, and auto-enabled screen-reader support. - ⭕ Does one-command install of MCP servers from a registry ('available immediately without restarting') introduce supply-chain or prompt-injection risk?
Not addressed; the piece frames friction removal as pure benefit. - ⭕ Does adding IDE-like richness (tabs, dialogs, object browsing) compromise the terminal's speed and simplicity, or how does it compare to rival agentic CLIs?
Not addressed.
Gaps
- incompleteOne command installs an MCP server from the GitHub MCP Registry and it is 'available immediately without restarting the CLI', yet the piece offers zero security or governance framing. Frictionless one-click tool install broadens the attack surface (untrusted/vulnerable servers, prompt injection, the lethal-trifecta combination of private-data access + untrusted content + external channels) — exactly the concern that low-friction install intensifies.
Read next: Read against extract-mcp-api-sprawl (43% of MCP servers vulnerable to auth flaws, 33% allow unrestricted network access; MCP exposes actions not just data) and extract-mcp-centralised-auth-enterprise (per-server authorization and identity-provider governance) to see what a registry-driven install flow leaves unaddressed. The lethal-trifecta framing sharpens why 'immediately available' is the risky part. - incompleteNo evaluation of whether these UI additions actually improve developer outcomes. The flow/reduced-context-switching benefit is asserted with no usage, adoption, or before/after productivity data.
Read next: Compare with extract-copilot-cli-general-availability#g2 (the same missing-benchmark gap for the product's GA) and measuring-ai-impact-style outcome-anchored evaluation; a feature-add announcement is not evidence of a productivity effect. - incompleteNo positioning against rival agentic CLIs (Claude Code, Aider, Cursor's terminal mode, Amazon Q). Whether tabbed GitHub-object browsing and in-session config are genuine differentiators or merely catching up to table-stakes is left open.
Read next: Read against extract-console-dev-best-tools-and-betas#p5 (support for skills, MCPs and hooks is now table stakes for an agentic IDE) and extract-copilot-cli-general-availability#g3/#g4 (the same shallow-competitive-analysis gap) to judge whether this is a lead or a catch-up.
Related documents
- This Week's Best Developer Tools & Betas
- How Claude Code works in large codebases: Best practices and where to start
- Kafka App? There's a Skill for That
- JobRunr Introduces ClawRunr, an Open-Source Java AI Agent
- Agent Skills: Google-Backed AI Coding Agent Workflow
- Agent Skills
- Have your agent record video demos of its work with shot-scraper video
- Agentic Engine Optimization (AEO)
- With Android CLI, Google is Making the Android Toolchain Agent-Friendly
- Audit your Agent files