Beyond VS Code

You just spent the Automation chapter handing follow-up work to the cloud coding agent — assigning issues, watching draft PRs come back, never leaving the GitHub-native loop. That was the last move inside VS Code. This chapter steps outside it.

The whole course has been first-class in VS Code, and that was a deliberate choice: it’s the surface most enterprise engineers are actually licensed to run, and it has the fullest set of agent features. But “first-class” was never “only.” The honest question to close on is the one a teammate will ask the first week: I live in a JetBrains IDE — how much of this do I lose?

The answer is reassuring, and it’s worth saying 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 are a cross-tool standard. What you steered the agent to do carries; only some of the agent features are still preview outside VS Code, and this chapter is about knowing which.

What’s in this chapter

The same work in JetBrains Do the orders-service and shared-lib work in a JetBrains IDE, with a per-feature callout for what's generally available versus still in preview — and the big reassurance that your rules files come along untouched.

The terminal footnote — Copilot CLI The same assistant, same account, same rules, reachable from a terminal for the moments you're already there. A footnote, kept deliberately short.

Start with JetBrains — it’s where the parity story really lives. Next: the same work in JetBrains.