A code editor for the edit you make once
It is not trying to replace your IDE. It replaces the ten minutes of setup before a five-minute change.
Code runs the Monaco engine — the one behind VS Code — with syntax highlighting, IntelliSense across languages, an integrated terminal, a project-style file explorer, real-time collaborative editing and a one-click workspace share link.
The edit you make once
Nobody is moving their daily development here, and the module is better understood as solving a different problem: the change that is small but currently costs you an hour of setup.
A config file a colleague needs corrected. A script you wrote last year on a machine you no longer have. Something a client asked about while you are on a laptop that has none of your tooling. In each case the change takes four minutes and getting ready to make it takes forty.
The share link is the actual feature
One click produces a link to the workspace. Somebody opens it and sees the same files, and with collaborative editing you are both in there at once.
This changes two situations completely. Reviewing a junior's work becomes sitting next to them rather than leaving comments on a diff — you fix the line together and they see why. And explaining a bug to someone stops being a description; you point at it.
The link goes to the workspace, so treat it as you would any workspace access: it shows what is in the project, not just the file you meant to share.
The terminal, and what it is not
The integrated terminal runs commands, which is enough for the common cases — installing a dependency to check something, running a test, a quick script.
What it is not is your development machine. Long-running processes, anything needing your local services, anything depending on a specific toolchain version: those belong where they already work. Reaching for the browser editor there costs more than it saves.
Where your own setup still wins
Say this plainly rather than discovering it mid-task. Your local editor keeps winning for sustained work, for anything with your extensions and keybindings in muscle memory, and for large repositories where a file tree in a browser is genuinely slower to navigate.
Use Code for the small, the shared and the away-from-desk. That is three real situations a week for most people, and it is enough.
Questions people actually ask
Should I move my development here?
No. It is built for the change that is small but currently costs an hour of setup — a config fix, an old script, something asked while you are on a machine without your tooling. Sustained work belongs in your own editor.
What does the share link give the other person?
Access to the workspace, not just one file, and with collaborative editing you are both in it at once. Treat it like any workspace access — they see the project, not only the file you meant.
Can I run anything in the terminal?
Commands, yes — installing a dependency, running a test, a quick script. It is not your development machine: long-running processes, local services and specific toolchain versions belong where they already work.
