GitHub publishes a new Copilot CLI guide focused on interactive and non-interactive modes
GitHub published a new entry in its Copilot CLI for Beginners series explaining the difference between interactive and non-interactive CLI use. The post describes interactive mode as the default back-and-forth session experience and non-interactive mode as a one-shot prompt flow entered directly from the shell.
According to GitHub, interactive mode starts when a user launches `copilot` and is meant for iterative work inside the same session, including asking follow-up questions and requesting that Copilot run project tasks. Non-interactive mode is triggered with `copilot -p` and is positioned for quick summarization, code generation, and lightweight shell-based workflows.
The guide also documents session resume behavior. GitHub says users can type `/resume` from interactive mode or use `copilot –resume` from the command line to reopen a previous session while preserving earlier context.
This is a documentation and workflow update rather than a new product launch, but it adds more concrete public guidance around how GitHub wants developers to use Copilot CLI in day-to-day terminal work.