Choose a Workflow and Stack
Most people make this harder than it needs to be.
Do not start with vendor rankings. Start with how you want to work. Once the workflow shape is right, the stack choice gets much easier.
Step 1: Choose Your Workflow Shape
Section titled “Step 1: Choose Your Workflow Shape”Integrated AI IDE
Section titled “Integrated AI IDE”Best when you want navigation, editing, and AI help in one place.
Good fit:
- you want one environment
- you do frequent multi-file work
- you value ease of use over maximum flexibility
AI Extension in Your Current Editor
Section titled “AI Extension in Your Current Editor”Best when you already like your editor and want AI without changing your whole environment.
Good fit:
- you want gradual adoption
- you care about portability
- you want flexibility in model or provider setup
Terminal Agent Workflow
Section titled “Terminal Agent Workflow”Best when you think in commands, diffs, plans, and verification loops.
Good fit:
- you already work in the terminal
- you want explicit control
- you want long-running or research-heavy agent workflows
Step 2: Apply Your Operating Constraints
Section titled “Step 2: Apply Your Operating Constraints”Now filter the workflow shape through your real constraints:
- Do you need local or private execution?
- Do you need enterprise identity, policy, or audit controls?
- Do you need screenshots or other multimodal input?
- Do you need easy model switching?
These are filters, not separate workflow shapes.
Step 3: Pick a Stack Bundle
Section titled “Step 3: Pick a Stack Bundle”Here are the only bundles most readers need to consider first:
- integrated AI IDE stack
- current-editor plus AI extension stack
- terminal agent stack
- private or local version of one of the above
- enterprise-managed version of one of the above
The goal is not to find the perfect product. The goal is to pick a setup you can actually operate well.
Step 4: Compare the Criteria That Matter
Section titled “Step 4: Compare the Criteria That Matter”Before you commit, compare your short list on:
- verification ergonomics
- privacy and deployment boundary
- setup burden
- switching cost
- team rollout friction
If a tool is impressive but makes verification awkward, it is the wrong fit for serious work.
Opinionated Defaults
Section titled “Opinionated Defaults”If you are new
Section titled “If you are new”Start with the lightest workflow that fits your existing habits.
If you are editor-first
Section titled “If you are editor-first”Start with an integrated IDE or an extension in the editor you already trust.
If you are terminal-first
Section titled “If you are terminal-first”Start with a terminal agent stack and optimize for explicit diffs, tests, and control.
If privacy is the main constraint
Section titled “If privacy is the main constraint”Choose the workflow shape first, then pick the local or tightly controlled version of it.
If you are evaluating for a team
Section titled “If you are evaluating for a team”Prioritize deployment boundary, identity, auditability, and verification ergonomics before feature volume.
Where Models and Providers Fit
Section titled “Where Models and Providers Fit”Once you know your workflow shape, use these pages to narrow the stack:
These pages should support the workflow decision, not replace it.
What This Page Does Not Do
Section titled “What This Page Does Not Do”This page helps you choose a working setup. It does not maintain a giant live market matrix.
For volatile details like benchmark movement, vendor snapshots, and privacy comparisons, use the Reference Appendix.