Wren AI Core in WrenAI GenBI
In WrenAI GenBI, the context and modeling foundation is now called Wren AI Core (previously Wren Engine). It is the same open context layer — the rebrand reflects that the engine is now the centerpiece of the open-source Wren AI project, not a sub-component of the GenBI app.
This page explains how Wren AI Core fits inside the GenBI app. For Wren AI Core itself — what it is, how it works, what MDL is, the architecture, and the modeling guides — see the Wren AI Core overview.
How Wren AI Core fits into the GenBI stack
The GenBI app is composed of three services with different responsibilities:
- Wren UI — user interface for connecting data, modeling, and asking questions
- Wren AI Service — retrieval, prompting, SQL generation, and result validation
- Wren AI Core — context, modeling, and execution foundation that the other two depend on
Conceptually:
- Wren AI Core defines the business layer.
- Wren AI Service uses that layer to retrieve context and generate better SQL.
- Wren UI lets teams interact with the system.
That is why Wren AI Core is a core part of the GenBI app, but is also meaningful as its own open project that can power any agentic surface — Slack bots, Cursor/Claude workflows, internal copilots, customer-facing analytics agents, or existing BI tools — beyond GenBI.
Where to learn more about Wren AI Core
- What it is and how it works → Wren AI Core overview
- The semantic contract → What is MDL?
- Why agents need it → What is Context?
- System architecture → Architecture
- Modeling primitives → Modeling guides
- CLI → CLI reference