Back to the collectionTHE SHORT VERSION YOUR OWN CHECK, NOT OUR TEST RESULTS
Code editor
Visual Studio CodeMixed components
Edit and review your project in a familiar, extensible workspace.
Resolve these before a trial
Documentation is a starting point, not proof of fit in your setup.
- License/compatibility of any extension not individually checked
A good fit when…
People who want a general code editor with a broad extension ecosystem.
Before you choose
The editor, an AI agent extension, and a model subscription are different components.
What you’ll need
A supported desktop OS; extensions may need their own accounts and permissions.
FIRST-TIME SETUPGuided installation
EVERYDAY USEGraphical editing and review; terminal familiarity helps.
Try one real task before switching
A generic checklist to run yourself. Use a small, reversible trial and non-sensitive sample data.
- Define one task and write down what a useful result would look like.
- Confirm the selected edition, total cost, setup owner, and required connections in the official documentation.
- Run the same task in your current setup and the candidate. Record missing steps, manual work, and errors.
- Check how you would export or remove your trial data and return to your current setup.
- Keep, test further, or stop. Do not migrate until your must-have requirements are confirmed.
Where your information goes
Telemetry and extension behavior vary. AI extensions can send code to external providers.