How does Copilot typically integrate into a developer's workflow?

Copilot installs as an extension inside the editor you already use, and that placement is the entire design. GitHub's setup guide runs through VS Code, Visual Studio, the JetBrains IDEs, Vim and Neovim, Xcode and others, all under one instruction: "To use Copilot in your preferred coding environment, follow the steps for your chosen IDE." Once it is in place you "get code suggestions as you type in your IDE" — nothing to switch to, nothing to paste.

That placement is what makes it useful. A tool sitting beside your open file can read the file; a tool in a separate window has to be told everything first.

Copilot does reach other surfaces — the GitHub website, the command line, mobile, and a standalone desktop app. So the wrong answer here is not the mention of a desktop application, which genuinely exists; it is the word "only", which would rule out the editor extension most people use every day. The remaining two options describe delivery methods that have nothing to do with installing software at all.