> ## Documentation Index
> Fetch the complete documentation index at: https://docs.t3planet.de/en/latest/llms.txt
> Use this file to discover all available pages before exploring further.

# How it works

> How the AI agent runs a T3AI request: page context, the four steps of every request, the three kinds of actions (only reads, asks before changing, asks before deleting), workspaces, data protection, and the requirements before you start.

## The page is the context

The AI agent works on what you have open. The context line at the top of the window shows the module, language, workspace, and page. *This page* and *here* in your request mean that page, unless you name another one, for example *"Translate page Contact into German"* or `@pages:12`.

## The four steps of every request

```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
  ask["1. You ask"] --> look["2. Agent looks up what it needs"]
  look --> preview["3. Preview: nothing changed yet"]
  preview -->|Apply| saved["4. Saved, with Undo"]
  preview -->|"Cancel or Discard"| none["Nothing is written"]
```

1. **You ask** in your own words, in any language. Click a suggestion or pick an action with `/`.
2. **The agent looks up what it needs**, for example the site languages, the glossary, or the page content. These read steps run automatically and appear as steps marked **completed**.
3. **For a change, it shows a preview** marked **Preview — nothing changed yet**. The preview lists exactly what will be written: the page, the languages, the glossary term, or each SEO field with its current and new value.
4. **You decide.** Click **Apply** to write the change, or **Cancel** to discard it. After **Apply**, the result card links to **Open page**, **Edit**, **View on website**, and **Undo**.

The agent never skips step 3 for a change. If it is unsure, it asks a follow-up question instead of guessing.

## Three kinds of actions

Every T3AI tool declares what it does. The `/` picker and the suggestions show this label.

| Label | What happens | T3AI examples |
| - | - | - |
| **Only reads** | Runs immediately. You see a step and an answer. | Show the translation glossary, Show the SEO queue, Show the translation queue |
| **Asks before changing** | Shows a preview. Writes only after **Apply**. | Write all SEO texts, Translate the whole page, Create a page, Save a glossary term, Add pages to the SEO queue |
| **Asks before deleting** | Red preview. Needs two clicks: **Confirm (1 of 2)**, then **Apply (2 of 2)**. Cannot be undone. | Remove a glossary term |

![Red delete preview for Remove a glossary term with Confirm (1 of 2) and Cancel](https://mintcdn.com/t3planet/O7ph795gSp6qACKc/en/latest/ExtNsT3AI/AskAiAgent/images/t3ai-agent-delete-confirm.webp?fit=max\&auto=format\&n=O7ph795gSp6qACKc\&q=85\&s=125199a0d553709cc40620b23ff708af)

## Live or draft workspace

* In **Live**, an applied change is public immediately. The preview says *On confirm this goes live on the website.*
* In a draft workspace, the change stays in that workspace until it is published. The preview names the workspace.

The context line of the agent window shows the workspace that is used, for example **Workspace: Live**. It is decided in this order:

1. **Your backend workspace**: if you switched to a draft workspace in the TYPO3 backend, the agent saves there.
2. **AI Foundation > MCP > MCP Server**, tab **Connect**, field **Workspace**: if you work in Live, the agent saves to the workspace selected here. Select a draft workspace to keep agent changes as drafts while you stay in Live, or **Live** to publish directly. The selection is stored per backend user and also applies to new MCP tokens and CLI commands.

![AI Foundation MCP Server, tab Connect, with the Workspace field highlighted](https://mintcdn.com/t3planet/O7ph795gSp6qACKc/en/latest/ExtNsT3AI/AskAiAgent/images/t3ai-agent-mcp-workspace.webp?fit=max\&auto=format\&n=O7ph795gSp6qACKc\&q=85\&s=15ca4b71285db021b83f48704c428b98)

If no draft workspace exists yet, the MCP Server tab offers **Generate MCP workspace**. Creating it needs access to the Workspaces module. Workspaces require the TYPO3 system extension `workspaces`.

To make drafts mandatory for an editor group, enable **Workspace enforcement** in **AI Foundation > AI Permissions**, step **Governance & limits** of the group. Members of that group then cannot apply agent changes in Live; the agent shows *Your group policy requires workspace-only edits. Switch to a draft workspace before applying changes.* See [AI Permissions](https://docs.t3planet.de/en/latest/en/latest/ExtNsT3AF/Configuration/AIPermissions/Index.md#guided-wizard).

> [!NOTE]
>
> The Mass SEO and Mass Translation queues are shared by the whole site. The agent changes them only in Live.

## Large jobs go to the Scheduler

The agent works on one page or a few pages per request. For many pages, ask it to queue them, for example *"Queue all subpages of Products for Mass SEO"*. The [Mass SEO](https://docs.t3planet.de/en/latest/en/latest/ExtNsT3AI/MassSEO/Index.md) and [Mass Translation](https://docs.t3planet.de/en/latest/en/latest/ExtNsT3AI/Translation/MassTranslation/Index.md) Scheduler tasks then process the queue. A single turn warns at 20 tool calls and stops at 40.

## Where the AI text comes from

T3AI tools generate SEO texts, translations, pages, and images with the AI provider configured in AI Foundation. **AI Foundation > MCP > AI MCP Mode** decides where the text is generated:

* **Context**: the AI agent's own model writes the text, and the T3AI tool saves it.
* **Native**: T3AI generates the text inside TYPO3.

Each AI call uses credits. Regenerating a preview uses credits again.

## Data protection

Your messages and the content the agent reads are sent to the AI provider shown in the message field. Your backend permissions and the AI Permissions of your user group always apply. See [DPA & GDPR](https://docs.t3planet.de/en/latest/en/latest/ExtNsT3AI/DPAandGDPR/Index.md).

## Before you start

| Requirement | Where |
| - | - |
| TYPO3 13.4 LTS or 14.x for the AI agent. On TYPO3 v12, all other T3AI features work as usual, only without the AI agent. | Your TYPO3 installation |
| AI Foundation and T3AI installed and active | [Installation](https://docs.t3planet.de/en/latest/en/latest/ExtNsT3AI/Installation/Index.md) |
| An AI provider with a model that supports tool calling | [AI Providers](https://docs.t3planet.de/en/latest/en/latest/ExtNsT3AF/Configuration/AIProviders/Index.md) |
| AI agent access for your backend user group (administrators always have access) | [AI Permissions](https://docs.t3planet.de/en/latest/en/latest/ExtNsT3AF/Configuration/AIPermissions/Index.md) |
| Normal TYPO3 permissions for the pages and records you want to change | Backend user groups |
| Site languages configured (translation) | Site configuration |
| Scheduler tasks for queued work (Mass SEO, Mass Translation) | [Mass SEO](https://docs.t3planet.de/en/latest/en/latest/ExtNsT3AI/MassSEO/Index.md), [Mass Translation](https://docs.t3planet.de/en/latest/en/latest/ExtNsT3AI/Translation/MassTranslation/Index.md) |

Next: [Your first T3AI request](https://docs.t3planet.de/en/latest/en/latest/ExtNsT3AI/AskAiAgent/StepByStep/Index.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.