Structured coding runs through multi-agent review. Draft, challenge, vote, and audit before the result lands.
The 7 stages below are not separate AI personalities — they are structured review phases that every model you select passes through together. Each model casts a binary yes/no vote at each stage; a no comes with its reasoning. A single no from any model blocks the run from advancing until the council resolves it into a genuine yes. Two models take on per-stage coordination duties (Lead: synthesises the discussion; Writer: authors the output artifact) — but their vote carries exactly the same weight as every other Guardian in the council.
Every selected model is an equal-vote Guardian for the whole run. Lead and Writer are duties that move between Guardians as the pipeline advances — never a higher rank.
The code stage — the Writer drafts the implementation while the council critiques.
Guardian. Every selected model. Equal vote, every stage, the whole run.
Lead. A per-stage duty: coordinates the discussion and announces the outcome — votes with equal weight. It moves to a different Guardian every stage.
Writer. A per-stage duty: the only model that writes code or runs commands, at the build stages. It also rotates between Guardians.
Binary vote. Each Guardian votes Yes or No — there is no third option. A No never ends the run: it loops back to deliberation, the council brings counter-arguments, and it resolves into a genuine Yes.
Your plan sets how many equal-vote Guardians sit on the council. Every Guardian still votes with the same weight at every stage — a larger council just means more independent perspectives debating before anything ships.
Solo model — a single Guardian.
A three-model council quorum.
Five models debate every stage.
Up to ten Guardians at the table.
Enterprise plans seat custom council sizes and may bring their own model keys. See pricing for the live plan catalog.
Interactive requirements Q&A — all models clarify scope together
"What is the exact success criterion for this task?"
Planning — the council aligns on approach and trade-offs
"Here are three viable approaches with their trade-offs."
System design — interfaces, modules, and data contracts
"The interface contract must be established before implementation begins."
Code draft — the Writer produces the first implementation
"Draft written. Submitting for council review."
Refine and challenge — the full council critiques the draft
"The draft is correct but this path can be O(n log n) instead of O(n²)."
Red-team and security audit — adversarial review by all models
"Input is not sanitized here — this is an injection vector."
Final validation — the council verifies correctness end-to-end
"Root cause traced three layers deep. Fix confirmed, regression covered."
One council, seven stages. Every model is an equal-vote Guardian the whole run; the Lead and Writer duties move between them stage by stage.
Actually runs the project; any failure goes back to the council and is worked to a genuine pass before finishing.
Read & research belong to every Guardian. Write & Run belong to the Writer only, and only at Maverick (04) and Optimizer (05).
The technology behind the desktop workflow
A multi-layered retrieval pipeline that understands code structure. It intelligently switches between vector retrieval for semantics and keyword search for exact symbol matches.
Every model you select is an equal-weight Guardian across all 7 stages. Voting is binary — yes or no — and a blocking no must carry a written rationale. A no is never dropped or rubber-stamped: the council deliberates, bringing counter-arguments or alternatives, until the objection resolves into a genuine yes. A run never silently hard-stops on an objection.
A council that doesn't just agree — it runs the code. Most AI tools vote on plausibility; SAMI's council votes on proven behaviour. It actually runs the project's build, tests, lint, and typecheck and feeds the real result back before any verdict is reached. A passing run is proven, not assumed. A failing run is put in front of the council with the real failure in view — the council either accepts it or blocks on it, which flows into the same never-abort resolution loop as a veto.
Industrial-grade security is baked into the development lifecycle. Automated red-teaming and dependency auditing occur before a single line of code is merged.
Manage complex microservices or mono-repos with ease. SAMI maintains independent context pools for each project while allowing cross-repo knowledge sharing.
The context engine grounds the whole run. A shared baseline context flows under every stage, each stage pulls its own slice on top, and any model can look back at what another said earlier in the run.
Hybrid retrieval blends semantic, keyword and code intelligence into one project-context stream the council can draw on.
Built on a familiar editor foundation — with all the extensions you love, plus an entire AI team working for you.
Curated access to leading models without requiring individual API keys.
Unified billing across all provider models used within your workspace.
Automatic failover routing to ensure high availability for all agents.
Security-controlled access layers for sensitive enterprise environments.
Same editor foundation you already know — same shortcuts, same keybindings, no relearning curve
Familiar coding surface with full IntelliSense support
Watch agents discuss and debate in real-time
Real-time streaming of code changes
Find code by meaning, not just text
Connect approved tools and data sources explicitly when a run needs them
SAMI uses a curated model catalog. You choose the model that fits your plan and we handle routing, billing, and safety controls behind a single managed runtime.
Pick from the models SAMI currently offers. No provider setup, no key management, no separate billing.
Requests are routed through SAMI's managed provider layer for consistent latency, failover, and billing behavior.
Provider credentials stay inside SAMI infrastructure while your plan controls access to the available models.
Other tools give you one AI assistant. SAMI runs a council of models that debate, vote, and must reach consensus before any result is accepted.
| Feature | SAMI (IDE) | Copilot (VS Code) | Cursor (IDE) | Windsurf (IDE) | v0 (Vercel) | Bolt (Netlify) | Lovable |
|---|---|---|---|---|---|---|---|
| Primary AI Logic | Configurable AI Review | Single Chat Agent | Composer / Single Agent | Cascade Flow | UI Generation | Scaffold Bot | App Logic Gen |
| Cognitive Architecture | Multi-Stage Pipeline | Reactive Chat | Reactive Edits | Sequential Cascade | Component Gen | App Generation | App Generation |
| Validation Strategy | Peer Review & Veto | Manual | Iterative Fixes | Agentic Fixes | Visual Feedback | Terminal Errors | Terminal Errors |
| Multi-Agent Debate | |||||||
| Autonomous Debugging | Deep Audit Pass | Manual | Agentic Assist | Cascade Fix | UI Refiner | Self-Heal (Basic) | One-Click Fix |
| Integrated Browser | Full Subagent | Limited View | Live View | Web-Container | Live Preview | ||
| Data Sovereignty | Managed Model Access | Enterprise Cloud | SaaS Privacy Mode | Codeium Cloud | Vercel Ecosystem | Netlify Cloud | Lovable Cloud |
| Code Ownership | Local Filesystem | Local Filesystem | Local Filesystem | Local Filesystem | Git Sync | Git Sync | Export to GitHub |
| Agent Manager | Multi-Project Control | Global Settings | Single Context | Single Context | Project View | Project View | Project Focus |
Start with the desktop workflow. Manage account and billing from the web dashboard.