Beyond VS Code

VS Code is where this course has been first-class, and that was deliberate: it has the fullest set of agent features for Copilot. But “first-class” was never “only.” The honest question to close on is the one a teammate asks the first week: I live in a JetBrains IDE - how much of this do I lose?

The answer is reassuring, and worth stating up front. Almost nothing you actually built is tied to VS Code. The conventions you wrote in the Rules chapter - the AGENTS.md, the CLAUDE.md - are repo-shaped, not editor-shaped, and JetBrains reads the same files. The skills you packaged follow the cross-tool Agent Skills format, and your MCP servers and custom agents carry their own support story there. What you steered the agent to do carries; only some of the agent features are still maturing outside VS Code, and this chapter is about knowing which.

What’s in this chapter

The same work in JetBrains Do the service and library work in a JetBrains IDE, with per-feature callouts for what is supported, what is preview, and what is not yet available - plus the reassurance that your rules files come along untouched.

The terminal surface - Copilot CLI The same assistant, same account, same rules, reachable from a terminal for the moments you are already there. Kept deliberately short.

Start with JetBrains - it is where the parity story really lives. Next: the same work in JetBrains.