GitHub shipped v1.0.78-2 of Copilot CLI on August 1, a small point release that's more useful as a signal of how fast this tool is iterating than for any single headline feature. Copilot CLI is GitHub's terminal-native coding agent, competing directly with Claude Code and Codex CLI for the "live in your shell, not a browser tab" segment of the agentic coding market, and it has been shipping near-daily point releases through late July as the team works through session management and extension-loading rough edges. This build fixes three specific papercuts that matter if you use the tool heavily: extension-provided slash commands were firing their handler more than once when you had several extensions loaded simultaneously, which could trigger duplicate side effects; inline images in the terminal timeline were rendering with a repeated first row once you scrolled past them, a rendering bug that made image-heavy sessions (screenshots, diagrams) visually broken; and piped runs — where you feed a prompt via stdin rather than typing interactively — weren't firing the sessionEnd hook per completed turn the same way normal runs do, instead firing once at shutdown with a generic user_exit reason, which breaks automation that depends on per-turn hook signals for logging or CI integration. The release also tweaks the split-view sidebar's close confirmation text so a second keypress is unambiguous about what it does. None of this is exciting on its own, but for teams building automation on top of Copilot CLI — piping prompts from scripts, relying on hooks to trigger downstream actions, or running it inside CI — these are exactly the kind of fixes that turn a flaky integration into a dependable one, and they're worth tracking if your workflow touches any of the three affected paths.