Copilot CLI v1.0.24 released
GitHub Copilot CLI issued v1.0.24, adding custom agent model support (for models like Claude Sonnet 4.5), a redesigned UI, preToolUse hooks and crash recovery, plus remote session support inside repositories. The update targets CLI‑first developer workflows and agent extensibility inside project repos. (x.com)
GitHub’s Copilot command-line tool has been shipping rapid updates since its February general release, and the recent releases show GitHub pushing harder into terminal-first coding agents. The official changelog lists version 1.0.18 on April 4, 2026, with new hook behavior and session fixes, while GitHub’s April 7 update added bring-your-own-model and local-model support. (github.com) (github.blog) Copilot CLI is GitHub’s interactive terminal app for coding tasks. GitHub says it can edit files, run tests, resume sessions, and switch between standard, plan, and autopilot modes from inside the shell. (docs.github.com) (github.blog) The new model story is central to the recent changes. On April 7, GitHub said Copilot CLI can connect to Anthropic, Azure OpenAI, OpenAI-compatible endpoints, and local runtimes such as Ollama and vLLM, without requiring GitHub-hosted model routing. (github.blog) That means a team can keep the same Copilot CLI interface while swapping in its own large language model provider. GitHub says built-in sub-agents inherit that provider configuration, and offline mode can keep the tool from contacting GitHub servers at all. (github.blog) Hooks are the other piece of the rollout. GitHub’s documentation says repository-scoped hook files in `.github/hooks/*.json` can run shell commands at events including `preToolUse`, `postToolUse`, `sessionStart`, and `errorOccurred`, letting teams log prompts, inspect tool calls, or block risky commands before execution. (docs.github.com 1) (docs.github.com 2) GitHub frames those hooks as a policy layer for engineering teams, not just a customization feature. Its tutorial for DevOps and platform teams says hooks can provide auditing, enforce organizational rules, and deny high-risk command patterns inside a repository where Copilot CLI is being used. (docs.github.com) Session continuity has also become a selling point. GitHub says Copilot CLI stores session data locally, supports `copilot --continue`, `copilot --resume`, and `/resume`, and lets users move between local sessions and remote coding-agent sessions. (docs.github.com) (github.blog) GitHub has been iterating on that workflow almost daily in April. The public changelog shows version 1.0.17 on April 3 speeding up the resume picker, and version 1.0.18 on April 4 grouping resumed sessions by branch and repository on first use. (github.com) The pace helps explain why GitHub keeps emphasizing the terminal as a full development surface. When Copilot CLI entered public preview in September 2025, GitHub pitched it as a way to work with a coding agent without leaving the command line; by February 25, 2026, GitHub said it had grown into a system that “plans, builds, reviews, and remembers across sessions.” (github.blog 1) (github.blog 2) The recent releases do not stand alone as a single one-off launch so much as part of that weekly rollout cadence. The through line across GitHub’s own release notes is consistent: more model choice, more repository-level control, and more ways to keep an agent session alive inside the terminal. (github.com) (docs.github.com)