Yellow ships with a built-in AI assistant — a chat agent that can read and write data on your behalf. Ask it to find an instance, summarise a model, create several rows at once, or walk you through how a feature works. It runs inside your current tenant and respects your permissions: anything you cannot do yourself, it cannot do either.

Where you find it

The assistant is available from a chat panel in the main shell. Open it from the AI icon and start typing. Conversations are saved as sessions that you can re-open later, rename, or delete. Sessions are per-user and per-tenant — your colleague never sees your chats, and your Acme sessions never appear when you are working in Acme Staging.

What it can do

Out of the box the assistant can:

  • Search and read — list models in a schema, fetch instances matching a filter, open a specific record and explain it back to you.
  • Create and update — fill in one or many instances when you describe what you need. It uses the same forms and validations you would see by hand, so constraints still apply.
  • Work with files — list files attached to an instance, summarise their contents, or upload a generated artefact.
  • Help with the platform itself — explain concepts, point at the right help article, suggest how to model something.

Behind the scenes the assistant uses tools — small operations exposed by Yellow that match each capability above. You will see them listed as it runs (reading the Customer model, creating 3 instances, uploading invoice.pdf). The trace is there so you can audit what the assistant did.

When the assistant mentions an instance or a model in its answer, it embeds a link back to that record. Click it to open the instance in the Explorer. This means you can use the assistant as a search tool: ask "show me the orders from Acme this month" and follow the links it returns.

Permissions and trust

The assistant acts as you. It can only do what your role allows.

  • It will not bypass constraints — if a value violates a rule, the same validation message you would see in the form is returned to the chat.
  • It cannot cross tenants — every session is bound to the tenant you opened it from.
  • It does not store sensitive content outside your tenant. Sessions and transcripts live in your tenant's storage.

That said, you remain responsible for what you ask. A request like delete every overdue invoice will be executed if you have the capability — review the tool calls the assistant proposes before confirming when the action is destructive.

Sessions, history and resuming

  • Each session keeps the full conversation including tool calls. Re-open it to continue where you left off.
  • Rename a session to find it later (default names come from the first message).
  • Delete a session to remove the transcript. The data the assistant changed is not rolled back — only the chat itself disappears.