> For the complete documentation index, see [llms.txt](https://docs.codemash.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.codemash.io/norbix-cloud/ai-chat.md).

# AI Chat

**AI Chat** is the assistant built into Norbix Cloud. Open it from any screen (as a side drawer or full screen) and work with your project by talking to it: inspect schemas, find records, configure modules, or ask "what changed?" — the assistant uses the same modules and respects the same permissions as you do.

### What you need

AI Chat needs a language model to run on. Two options:

* **System models** — models offered by the platform, ready to use.
* **Project models** — your own LLM provider connected as a project integration (for example your Anthropic or OpenAI account). Add one under your project's *Integrations*.

If no model is available, the chat launcher explains why (for example, no LLM is configured). Use the **model picker** to choose a model, or leave it on **Auto** and let Norbix pick the default.

### Scoped to your project and environment

The chat always works in the context of your currently selected project and environment (for example `DEV` or `PROD`). Switch the project — the assistant switches with you.

### Plans and approvals

For anything bigger than a question, the assistant first shows a **plan**: a numbered list of steps, each mapped to a concrete tool it wants to use. Nothing runs until you **approve** the plan. As it works, each step shows its status (pending, done, failed) and a short result summary. Actions that change data show a pending-action card asking for your confirmation.

### Two chats, one identity rule

Norbix has two chat surfaces, and they follow a strict identity boundary:

* **Hub chat** — what you use in Norbix Cloud. For admins and team members: structural work like schemas, integrations, users, and configuration.
* **API chat** — a chat your **shipped app** can offer its end users. End users can only work with their **own** data (own profile, own records) — never anything structural, never another user's data.

The same rule as everywhere in Norbix: the chat can do exactly what the signed-in identity is allowed to do, and every action is visible in [Logs & Monitoring](/norbix-cloud/logs.md).

### Related

* [Norbix + AI](/ai/ai.md) — MCP server, IDE clients, and framework integrations
* [Membership](/norbix-cloud/membership.md) — roles and permissions that bound what the chat may do