LoxiaFlow doesn't let you point every feature at every model. Each feature is locked to one of the two categories described in AI Config Categories — Coding (CLI tools and the LoxiaFlow Agent loop, with real file/shell access) or General Purpose (API-based, read-only) — so a feature that touches your codebase can never accidentally run on a model that can't actually edit files. This mapping is enforced in Settings → AI Config → Model Mapping, not just documented here — a model that isn't in the right category won't show up as a selectable option for that feature.
| Feature | Model category | Tier |
|---|---|---|
| 01Planning & Requirements | ||
| Documents | General Purpose | Light |
| 02System Design | ||
| Style Guide | General Purpose | Light |
| Mockups | General Purpose | Heavy Generation |
| Project Layers — Run Setup | Coding | Heavy Coding |
| 03Implementation | ||
| Generate Workflows | General Purpose | Heavy Generation |
| Workflows / Workflow Runner (Run Layers) | Coding | Heavy Coding |
| 04Testing & Security | ||
| Test Generator | General Purpose | Medium Coding |
| Security Scans | General Purpose | Light |
| 05Maintenance | ||
| Issues | Coding | Heavy Coding |
| Issue Runner | Coding | Heavy Coding |
| —Cross-Feature Utilities | ||
| AI Console | General Purpose | Light |
| Git Changes | Not AI-driven | — |
| Terminal | Not AI-driven | — |
Suggested models by tier
Every feature above maps to one of these four tiers — the list below is the suggested model/mode combination for that tier, shown once rather than repeated per feature.
Why the split
Project Layers (Run Setup), Workflows, Workflow Runner, Issues, and Issue Runner all drive the LoxiaFlow Agent loop against your real project files — so only agent-capable, Coding-purpose models (CLI tools like Claude CLI or Agy CLI, or an Ollama model with the Agent loop enabled) are selectable there. Every other AI feature runs a single prompt/response with no file or shell access — Style Guide, Documents, Mockups, Generate Workflows, AI Console, Test Generator, and Security Scans — so they're restricted to General Purpose models instead, including the plain Anthropic API and any OpenAI-compatible provider.
Git Changes and Terminal don't call a model at all — they're plain, non-AI utilities used alongside the AI-driven features above.