No Formal Workflow System
ManyAI does not have a named workflow system. Instead it uses provider routing by task type via bestFor[] arrays. Users do not pick a workflow — the app routes automatically based on the nature of the request.
For a full workflow plugin system with named types, tabs, and custom configuration, see ManyAI Desktop — Workflows.
Task Type Routing
Task types are automatically detected and routed to preferred providers based on their bestFor configuration in lib/providers/providers.ts.
| Task Type | Preferred Provider | Notes |
|---|---|---|
| Coding | Mistral | Code generation and explanation |
| Reasoning | SambaNova | Deep analysis, 70B model |
| Creative | Mistral | Writing and brainstorming |
| Summarization | Gemini | 1M token context, long documents |
| Translation | Gemini | Multilingual, long context |
| Image | Pollinations | Auto-detected from prompt keywords, no key required |
Image Request Detection
isImageGenRequest() scans the prompt for keywords including: draw, paint, generate image, create image, sketch, illustration. If matched, the request routes to image-capable providers. Pollinations is always available for image tasks and requires no API key.
Provider bestFor Mapping
Each provider definition in lib/providers/providers.ts includes a bestFor array listing task types it excels at. pickProvider() uses this in first-pass selection before falling back to any capable provider in ROUTING_ORDER.
ROUTING_ORDER
A static priority list defining which providers to attempt first across all task types. Users can reorder providers in Settings. The order determines fallback sequence when the preferred provider for a task type is unavailable.