Developer Tools
GitHub Copilot CLI Moves From Chat Surface to Background Developer Worker
Published June 03, 2026 by Dillip Chowdary
The Release
GitHub refreshed Copilot CLI at Microsoft Build 2026 with a new experimental terminal interface, generally available rubber duck support, prompt scheduling, and voice input. The update is notable because it shifts the CLI from an interactive prompt surface toward a lightweight agent runtime embedded in everyday terminal work.
Scheduling Changes The Risk Model
The new /every and /after commands let users schedule prompts inside the current CLI session. A developer can ask Copilot to run checks every 30 minutes, summarize token usage hourly, or execute a one-time task later. That is useful for maintenance, but it also means AI prompts can become background jobs that need runtime limits, workspace scope, and a clear notification path.
Terminal UX Becomes Agent UX
The experimental interface adds tabs for repository issues, pull requests, and gists, allowing developers to inspect GitHub context without leaving the CLI. Accessibility improvements include high-contrast and colorblind color modes plus screen-reader-aware behavior. These are small interface details with a large adoption effect: agents are easier to trust when their state is readable in the place developers already work.
Voice And Rubber Duck
Voice input runs locally after the user downloads a runtime and selects a speech-to-text model, keeping recorded audio on the machine. Rubber duck support gives developers a structured way to talk through a problem before generating changes. Teams should treat these as design signals: coding agents are becoming conversational, scheduled, and stateful rather than one-shot autocomplete tools.