LEX AI Docs Hub: Setup and Navigation
How the docs hub is organised, the six-step setup flow from lex setup-with-ai to picking a mode, and the intent-first routing principle.
LEX AI Docs Hub: Setup and Navigation
The docs hub is organized for question-first navigation with top-topic buttons, a sidebar topic map, and in-place topic switching.
Start topics
- Overview
- Setup and dashboard
- AI dashboard
- Choose the right path
Setup flow
- Prepare the workspace with
lex setup-with-ai. The command is hyphenated;lex setup_with_aiis a Python module path, not a command, and fails withNo such command. - Select the coding environments actually in use, with repeatable
-e/--environmentflags.lex setup-with-ai --list-environmentsprints the supported keys, and the dashboard offers the same choice later. - Open the control surface with
lex ai-dashboard. - Confirm active project resolution, then read the MCP registration table, which reports for each config file whether the server entry is registered, missing, or absent.
- Select the correct MCP mode from the ten mode cards.
- Start a fresh assistant request after a mode change, so the IDE picks up the new tool surface. Each environment has its own refresh gesture — reloading the VS Code window, refreshing the Cascade panel, and so on.
Routing principle
Use user intent first, tool names second. If the intent matches multiple rows, ask one clarification question. Where the user cannot yet state the outcome they want, route them to Brief mode rather than guessing a build mode on their behalf.
Why this docs format
Topic switching keeps navigation visible while users jump across setup, modes, system behavior, and operations without losing context. It also keeps each fact in one place: a page explains a rule once, and the other pages cross-reference it rather than restating it and drifting.
See Setup and dashboard and AI dashboard for the operator detail.
Was this helpful?
Your feedback shapes what we write next.
