LEX AI Overview
What LEX AI is, the ten workflow modes it exposes, which one to choose for a given job, and how to get started with lex setup-with-ai.
LEX AI Overview
LEX AI is a local MCP server package that gives your IDE assistant a structured, tool-driven way to build, document, change, audit, test, adapt, and deploy Lex projects. Instead of free-form prompting, the assistant works through purpose-built modes, each with its own tools, guardrails, and durable outputs.
What it does
- Coordinates workflows instead of generating code ad hoc — the server owns the ordering, the gates, and the error handling, so a run does not depend on how the prompt was worded.
- Exposes one mode at a time — the assistant only ever sees the tools belonging to the job you chose, which is what keeps runs deterministic.
- Leaves durable artifacts — contracts, plans, technical maps, and reports stay in the project as handoff memory for the next person or the next session.
The ten modes
Mode key | What it is for |
|---|---|
| Interview you and write the project contract. |
| Build a new app end to end (20 steps). |
| Reverse-document an existing codebase (18 steps). |
| Make one focused, well-checked change. |
| Run a convention or business-compliance audit. |
| Write the test suite and prove it catches regressions. |
| Adapt an app to a changed input-data format. |
| Get an existing app running in a target environment. |
| Scaffold a capped first version. |
| Expand an approved MVP to full scope. |
Which mode to choose
- You cannot yet describe what should be built —
brief. It asks the questions, writes.lex/contract.md, and names the build mode to continue in. - New app from scratch —
forward. Fast first cut —mvp_generator. Grow that MVP into the real thing —mvp_completion. - Change an existing app —
edit. Audit it —review. Document it —backward. - It has no trustworthy tests —
test. Its input file changed shape —input. It needs to run somewhere —deploy.
Where it runs
The server plugs into seven supported coding environments: GitHub Copilot in JetBrains IDEs, in VS Code, and in the Copilot CLI, plus Cursor, Claude Code, OpenAI Codex, and Windsurf. The same agents and the same rules ship to all of them; only the file layout each host expects differs. See Supported coding tools.
Getting started
- Run
lex setup-with-aiin your Lex project folder. - Run
lex ai-dashboard, confirm the project, select your coding environments, and pick a mode. - Start a fresh assistant request describing what you want.
See Setup and dashboard and Choose the right path next.
Was this helpful?
Your feedback shapes what we write next.
