> For the complete documentation index, see [llms.txt](https://docs.gta.clothing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gta.clothing/how-to-guides/connect-an-ai-assistant.md).

# Connect an AI Assistant

Let an AI app on your PC work in Durty Cloth Tool while you watch every change in the window

An AI app that supports MCP servers, such as Claude Code, Claude Desktop, Codex, Cursor or VS Code, can work in Durty Cloth Tool for you. You keep DCT open and watch every change it makes in the window. You set it up once, with one click: **Add to** your AI app in **Options > Connected apps**.

{% hint style="info" %}
AI assistants are Experimental. An assistant can look at your project and change it: open it, read its items, findings and previews, change item details, add files, remove items, run the [**Error List**](https://docs.gta.clothing/basics/essential-knowledge/cloth-analysis-report.md)'s Fixes, undo, redo and save, run any action of DCT's menus on the items it names, build, set up your project's settings, restore History, look at clothing in the [3D preview](https://docs.gta.clothing/basics/essential-knowledge/3d-preview-clothes.md) and on the in-game [Clothing Inspector](https://docs.gta.clothing/how-to-guides/test-clothing-in-game-with-the-clothing-inspector.md)'s mannequin, and work in DCT's own windows, such as the [**Texture Optimizer**](https://docs.gta.clothing/basics/essential-knowledge/texture-optimizer.md). It can also search these guides and guide you, step by step, when you are new to DCT. More tools follow in later versions, and this guide grows with them.
{% endhint %}

## Before you start

* Durty Cloth Tool installed, or the portable version unpacked in the folder you keep it in.
* An AI app that can start a local MCP server (a "stdio" server) from its settings or command line.

## What an assistant can see

The section in DCT says it plainly:

> An AI assistant you connect can read and change everything in DCT that you can, including item names, settings, findings, preview images and files you add. What it reads is sent to that assistant's provider under their terms. Documentation searches go to docs.gta.clothing.

AI assistants are off until you turn them on. While they are on, any program you run under your Windows account can connect through `dct.exe`, not only the AI apps you added, so turn the switch off while you do not use an assistant.

While usage data is on, Durty Cloth Tool counts which of its tools an assistant uses and how each use ended, never what the assistant asked or read ([Usage Data & Feedback](https://docs.gta.clothing/basics/good-to-know/usage-data-and-feedback.md#ai-assistants)).

## Add Durty Cloth Tool to your AI app in one click

1. Open **Options > Connected apps** and scroll to **AI assistants**. DCT lists the AI apps it found as rows: Claude Desktop, Claude Code, Codex (the ChatGPT app, the Codex CLI and the Codex IDE extension share one setup), Cursor, VS Code, LM Studio and Gemini CLI. AI apps that are not on your PC are named under **Other apps** at the end of the page.
2. Choose **Set up** on your AI app's row. DCT backs up the app's settings file beside it first, adds a `dct` entry and changes nothing else in the file. Where the app has its own setup command, as Claude Code and the Codex CLI do, DCT uses it.
3. Adding also turns on **AI assistants**: **Let AI assistants control Durty Cloth Tool** is ticked, and the line under it says **On. No AI assistant is connected right now.**
4. If the row says to restart the app, quit it completely and open it again. Claude Code and VS Code pick DCT up in a new chat or session.

<figure><img src="https://2130288373-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRsXe3tqSiAvM8iKYjngE%2Fuploads%2Fgit-blob-1aa9564a6545f35ce4c8ca91ad2cee7f091fe310%2Fconnected-apps-ai-assistants.png?alt=media" alt="Options > Connected apps scrolled to AI assistants: Let AI assistants control Durty Cloth Tool is off, with the warning about what an assistant can read and change, Check again and Copy setup. Below are the AI apps found on this PC: Claude Desktop with Close Claude Desktop first, and Claude Code, Codex, Cursor, VS Code and Gemini CLI, each Not set up with Set up. LM Studio is listed under Other apps."><figcaption><p>AI assistants in Options > Connected apps: one row per AI app on your PC, with its status and Set up.</p></figcaption></figure>

{% hint style="warning" %}
Quit **Claude Desktop** completely, also from the notification area, before you add DCT to it or remove it. Claude Desktop writes its own settings file while it runs and would undo the change, so its row waits until it is closed. Then choose **Check again**.
{% endhint %}

When Claude Desktop, the ChatGPT or Codex app, Cursor or LM Studio is open without DCT's entry, a notice in the corner of the editor offers the same setup: **Use Durty Cloth Tool from ...**, with **Set up**. For Claude Desktop it reads **Set up when Claude Desktop closes** and waits until you quit it. **Not now** hides it until you start DCT again, and **Don't show again for ...** turns it off for that app. See [When Durty Cloth Tool suggests a plugin](https://docs.gta.clothing/plugins/creator-link/install-and-update.md#when-durty-cloth-tool-suggests-a-plugin).

Each row shows one status, such as **Not set up**, **Ready to use**, **Setup needs an update** or **Restart ... to use it**. The arrow at the end of the row shows its details, where the row says where the app stands:

| The row says                                                                                         | What it means                                                                                                                                                                                                                               |
| ---------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Not added yet.**                                                                                   | Choose **Set up** to add DCT.                                                                                                                                                                                                               |
| **Added.**                                                                                           | The app starts this copy of Durty Cloth Tool. **Remove** takes DCT out of its settings again; AI assistants stay on. If the app is open, restart it afterwards.                                                                             |
| **Added. Restart** the app **to load it**                                                            | The app was open when DCT was added. Quit it completely and open it again.                                                                                                                                                                  |
| **Set up for another copy of Durty Cloth Tool on this PC** or **for a copy that is no longer there** | The entry starts another Durty Cloth Tool, for example the installed one while you use the portable one, or a portable folder you moved. **Update setup** points it at this copy and keeps anything else you set for it, such as a timeout. |
| **In Claude Desktop, open Settings > Developer and choose Edit Config once**                         | Claude Desktop has no settings file yet. Make it once there, then choose **Check again**.                                                                                                                                                   |
| **Its settings file is not valid** or **is written in a form Durty Cloth Tool does not change**      | DCT changed nothing. Fix the file, or add the entry yourself with **Copy setup** below.                                                                                                                                                     |
| **Added, but turned off in the app**                                                                 | The entry is there but switched off in the app's own settings. **Update setup** turns it on.                                                                                                                                                |
| **Its settings already hold another server named dct**                                               | A server of your own uses the name `dct`. DCT leaves it alone; rename or remove it in the app, then choose **Check again**.                                                                                                                 |

The entry starts `dct.exe` from Durty Cloth Tool's own folder: `%LocalAppData%\DurtyClothTool\current\dct.exe` when installed, or the `current` folder of your portable copy. The path stays the same when DCT updates. **Check again** looks for AI apps again, for example after you installed one.

### From a terminal

The same setup works from PowerShell or a command prompt, with `dct.exe` from Durty Cloth Tool's folder:

```powershell
& "$env:LOCALAPPDATA\DurtyClothTool\current\dct.exe" mcp install --list
& "$env:LOCALAPPDATA\DurtyClothTool\current\dct.exe" mcp install claude-code
& "$env:LOCALAPPDATA\DurtyClothTool\current\dct.exe" mcp uninstall claude-code
```

`mcp install --list` shows each app and whether DCT is added to it. The app names are `claude-desktop`, `claude-code`, `codex`, `cursor`, `vscode`, `lm-studio` and `gemini`. `mcp install` also turns on AI assistants while DCT is closed; while DCT is open, it tells you to turn them on in **Options > Connected apps**.

## Add Durty Cloth Tool to another AI app

For an AI app that is not in the list, turn on AI assistants yourself and copy the setup:

1. In **Options > Connected apps > AI assistants**, tick **Let AI assistants control Durty Cloth Tool**.
2. Under **Other AI apps**, choose **Copy setup**. DCT puts this entry on the clipboard, with the real path of `dct.exe` on your PC:

```json
"dct": {
  "command": "C:\\Users\\you\\AppData\\Local\\DurtyClothTool\\current\\dct.exe",
  "args": ["mcp"]
}
```

`dct.exe` is the small program your AI app starts. It connects the AI app to the open Durty Cloth Tool, and starts Durty Cloth Tool when it is closed. Paste the entry where your AI app keeps its MCP servers:

{% tabs %}
{% tab title="Apps with a JSON settings file" %}
Most apps keep their MCP servers in a JSON file under `"mcpServers"`. Open that file from the app's settings and paste the entry inside `"mcpServers": { }`, with a comma between it and any server already there:

```json
{
  "mcpServers": {
    "dct": {
      "command": "C:\\Users\\you\\AppData\\Local\\DurtyClothTool\\current\\dct.exe",
      "args": ["mcp"]
    }
  }
}
```

Save the file, then quit the AI app completely and start it again.
{% endtab %}

{% tab title="Codex by hand" %}
Codex keeps its servers in `config.toml` in the `.codex` folder of your user folder. One-click setup writes the first two lines; to give DCT more time to start when it is closed, add the third yourself:

```toml
[mcp_servers.dct]
command = 'C:\Users\you\AppData\Local\DurtyClothTool\current\dct.exe'
args = ["mcp"]
startup_timeout_sec = 60
```

The single quotes keep the backslashes as they are.
{% endtab %}
{% endtabs %}

## Check the connection

Ask your AI app something like "What is the status of Durty Cloth Tool?". It calls the **get\_status** tool and answers with DCT's version, the name of the open project, your plan (free, **Advanced** or **Ultimate**) and whether DCT is idle or busy. While DCT loads a project, builds or is busy with a dialog, it reports busy; the assistant waits and asks again.

While an assistant is connected, the status bar at the bottom of DCT shows **AI assistant connected:** and the AI app's name, and **Options > Connected apps** shows it under the switch. Once it has done something, **Activity** appears beside it (see [See what the assistant did](#see-what-the-assistant-did)).

{% hint style="success" %}
If the status bar shows your AI app's name, the setup works.
{% endhint %}

## Let the assistant guide you

You do not need to know Durty Cloth Tool to start. The assistant can look at where you are, tell you what to do next and do it with you, one step at a time.

### Pick a prompt

Your AI app lists nine prompts from **dct** where it offers prompts, in many apps under the **+** or **/** menu. These four guide you one step at a time; the five in [Let it do a whole goal](#let-it-do-a-whole-goal) do a goal for you from start to end.

| Prompt                                | What the assistant does                                                                                                                                                                                                                    |
| ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Get started with DCT**              | Asks what you want to make, such as clothing for a FiveM server or for single player, then walks you to your first build: opening or creating a project, adding your clothes, fixing what it finds, choosing where to build, and building. |
| **Check my project and fix problems** | Reads the **Error List**, tells you in plain words what it found and what each problem means in game, offers **Fix safe findings** first, then each finding's Fix, and runs a Fix when you say yes.                                        |
| **Build for my server**               | Clears what stops the build first, asks where the resource should go when your project has none, and builds. You can name your server type: FiveM is recommended; alt:V and RageMP still build but are deprecated.                         |
| **Explain this finding**              | Explains a finding of the **Error List**: what is wrong, on which item, what it means in game and how to fix it. Give it the rule or item as the **Error List** shows it, or leave it empty for the most important one.                    |

### Let it do a whole goal

Tell the assistant what you want to end up with, and it does the whole way there for you. It asks the decisions that matter first, all in one message, then works through the plan and tells you what each step did.

| Prompt                                           | What you end up with                                                                                                                                                               |
| ------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Create a clothing resource for my server**     | A built clothing resource for a FiveM server from your clothing files. alt:V and RageMP still build but are deprecated. You can name your server and the folder with your files.   |
| **Make clothing for single player**              | A built single player clothing pack, from your clothing files.                                                                                                                     |
| **Add these files to my project and build**      | Your clothing files added to the project you have open, fixed where something stops the build, and built.                                                                          |
| **Turn my existing resource into a DCT project** | A DCT project made from a clothing resource you already built, checked, and built again into a new folder so you can compare. Adding a built resource needs a licence.             |
| **Share this project with my team**              | Your project as a cloud project shared with your team, or in a Git repository, after an explanation of both and a recommendation. You sign in and confirm sharing yourself in DCT. |

You can also just say it, for example "I want to create a FiveM clothing resource with Durty Cloth Tool. My files are in C:\Clothes\Summer."

#### What the assistant asks first

Before it changes anything, the assistant asks only the decisions that change the result and are hard to change later, each with what it recommends and why. In AI apps that can show forms, they arrive as one form in your AI app, with the recommendation already selected and its reason under each question: change what you want and send it. In other apps the assistant asks in the chat; reply "go with your recommendations" to take them all:

| Decision                                                  | What it recommends                                                                                                                                     |
| --------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Which game or server the clothing is for                  | FiveM, DCT's default target, or single player. alt:V and RageMP still build but are deprecated.                                                        |
| For FiveM, which edition                                  | Legacy, DCT's default edition. Choose Enhanced or both only when your server runs GTA V Enhanced.                                                      |
| What the resource is called                               | The project name in lowercase letters and digits.                                                                                                      |
| Which ped genders the clothes are for                     | Let DCT read it from your file names; it asks about the files that do not say.                                                                         |
| Where your clothing files are                             | The folder that holds your `.ydd` and `.ytd` files. DCT copies them into the project and leaves the originals.                                         |
| Where DCT keeps the project                               | A new, empty folder of its own.                                                                                                                        |
| Where the built resource goes                             | A new folder in your server's resources folder, such as `resources/[clothing]`. Never a folder with other files: a build replaces what it built there. |
| Keep the project on this PC, as a cloud project or in Git | On this PC. A cloud project (it needs Ultimate) or Git can follow later.                                                                               |

Each workflow asks only the decisions it needs. Everything else uses DCT's defaults, and the assistant says which. Then it confirms the whole plan in one message and, once you agree, works through it without asking again, apart from the questions only you answer in DCT's window. When a step needs a plan you do not have, something only you can do, or something DCT cannot do, it says so plainly and carries on with what it can. If DCT is missing something you need, it can offer to tell the DCT team ([Feedback to the DCT team](#feedback-to-the-dct-team)).

### Or just ask

You can also ask in your own words, in your own language. The assistant answers in the language you write in. For example:

* "I am new to Durty Cloth Tool. What should I do first?"
* "I have a folder of .ydd and .ytd files. Make a FiveM clothing resource from them."
* "What stops my project from building?"
* "What does this warning mean in game, and should I fix it?"
* "What should I do next?"

### How the assistant works with you

* **It knows the next step.** DCT tells the assistant what it recommends for your project right now: open your last project or start a new one, add clothes, run **Fix safe findings**, fix an error with its Fix, build (asking you where, when your project has no output folder), then test in game once nothing changed since the build. It works from DCT's own checks, not guesses.
* **Every question comes with a recommendation.** When the assistant asks you something, it says what it recommends and why in one line, so you can answer "go with your recommendation". Where your AI app shows forms, the question comes as a form with the recommendation preselected; you can also decline the form and answer in the chat.
* **You can follow long steps and stop them.** For an import, a Fix, an optimization, a build or a sync, your AI app can show what DCT's window shows of the work, step by step. Stopping the assistant's step in your AI app stops DCT's work as **Cancel** in DCT's window does: what it finished stays, and you can undo it.
* **One step at a time.** It explains each step before it takes it. Without asking, it only reads or shows something, such as the 3D preview; before it changes your project or files, it asks you. Afterwards it checks the result and tells you what is next.
* **Your questions stay yours.** Questions only you answer still appear in DCT's window (see [Questions only you answer](#questions-only-you-answer)).
* **Plans.** When something needs **Advanced** or **Ultimate**, the assistant tells you plainly and carries on with what works on your plan. It never opens the purchase window.
* **It looks at what it changed.** After a Fix, a texture or model change or an add, the assistant puts the item on the 3D preview's ped, takes pictures from the views that matter and tells you what it sees.
* **In game is the real test.** DCT's checks and the 3D preview are not proof of how clothing looks in game. When the Clothing Inspector is connected to your game, the assistant can put the item on its mannequin for you to look at; otherwise it asks you to check it in game and tells you how.

The assistant sees your recent projects on Home by name only, not where they are on your PC.

## What an assistant can do

Your AI app lists these tools under **dct**. You do not call them yourself; ask in your own words, such as "Open my street pack and tell me what stops the build".

| Tool                                     | What it does                                                                                                                                                                                                                                                                                                                                                                                                                                                |
| ---------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **get\_status**                          | Tells the assistant DCT's version, the open project, your plan, whether DCT is busy and the most important next step for you.                                                                                                                                                                                                                                                                                                                               |
| **describe\_capabilities**               | Tells the assistant what it can do for you in DCT, goal by goal: which tools do it, the plan each needs, what only you can confirm and what DCT cannot do, and the decisions to ask you first with DCT's recommendations.                                                                                                                                                                                                                                   |
| **create\_project**                      | Creates a new project as **Project > New** and the first **Project > Save as** do, with the name, folder, target, FiveM edition, resource name and build output folder you agreed on, and opens it. If the open project has unsaved changes, DCT asks you what to do with them, as for **Project > New**.                                                                                                                                                   |
| **ask\_creator**                         | Asks you the assistant's decisions as one form in your AI app, its recommendation preselected with the reason, and gives the assistant your answers. In an AI app without forms the assistant asks in the chat instead. It never asks the questions only you answer in DCT's window.                                                                                                                                                                        |
| **suggest\_next\_steps**                 | Tells the assistant DCT's recommended next steps for your project now, each with why, what it changes and what to ask you first. See [Let the assistant guide you](#let-the-assistant-guide-you).                                                                                                                                                                                                                                                           |
| **open\_project**                        | Opens a project file (`.dctproj`) on this PC the way you would from Explorer, or one of the recent projects Home lists. DCT's own questions, such as saving unsaved changes in the open project, appear in DCT's window for you to answer. A project on a network share is not opened for an assistant: open it yourself.                                                                                                                                   |
| **list\_items**                          | Lists the project's clothing, props, tattoos and facial overlays with their gender, drawable type, number in their collection, texture variation count, open errors and warnings, and tags. The assistant can narrow the list by gender, drawable type, kind of item or tag.                                                                                                                                                                                |
| **get\_item**                            | Reads everything **Item Details** shows for one item, including its texture variations or tattoo placements.                                                                                                                                                                                                                                                                                                                                                |
| **list\_findings**                       | Reads the **Error List**: each finding's severity, item, rule and message, in English whatever language DCT shows. Findings you ignored stay hidden unless the assistant asks for them, and rules you switched off are never listed. Each finding also says what it means in game and which Fixes the **Error List** offers for it.                                                                                                                         |
| **get\_item\_preview**                   | Looks at the preview picture DCT's item list shows for a piece of clothing or a prop.                                                                                                                                                                                                                                                                                                                                                                       |
| **open\_preview** and **close\_preview** | Open or close the 3D preview, as **View > 3D Preview** does.                                                                                                                                                                                                                                                                                                                                                                                                |
| **show\_in\_preview**                    | Puts one item on the 3D preview's ped, as the item list's **Preview** does: clothing or a prop in the texture variation and on the body the assistant chooses, a tattoo or facial overlay on the freemode body. What you selected in the item list stays selected.                                                                                                                                                                                          |
| **set\_preview\_view**                   | Turns the 3D preview's camera to the front, back, left or right of the ped, or to a close-up of the head, torso, legs or feet.                                                                                                                                                                                                                                                                                                                              |
| **capture\_preview**                     | Takes one picture of the 3D preview once it has finished loading. Large pictures are made smaller (1600 pixels on the longest side unless the assistant asks for less), which keeps the cost with your AI provider down.                                                                                                                                                                                                                                    |
| **refresh\_thumbnails**                  | Makes the item list's preview pictures of the items again, for example after a texture changed.                                                                                                                                                                                                                                                                                                                                                             |
| **get\_game\_link\_status**              | Tells the assistant whether your game is connected to DCT through the in-game Clothing Inspector, and whether the game runs the latest build of your project.                                                                                                                                                                                                                                                                                               |
| **show\_in\_game**                       | Puts one item on the Clothing Inspector's mannequin in your game, as **Show in game** does, and tells the assistant whether it was worn.                                                                                                                                                                                                                                                                                                                    |
| **search\_docs**                         | Searches these guides, so the assistant follows DCT's own instructions instead of guessing. It works with no project open and while DCT is busy.                                                                                                                                                                                                                                                                                                            |
| **read\_doc**                            | Reads one page of these guides, such as a page **search\_docs** found. It reads only pages on docs.gta.clothing.                                                                                                                                                                                                                                                                                                                                            |
| **update\_item**                         | Changes what **Item Details** shows for one item: its name, note, tags, gender, number in the list, drawable type, options, behaviour flags, shop values and its texture variations' or tattoo placements' values. Files are not changed here.                                                                                                                                                                                                              |
| **add\_items**                           | Adds files and folders the way you drop them on the item list: clothing models with their textures, texture files, packages, zips, projects, built resources, tattoo images and 3D models. DCT copies what it adds into the project and leaves the originals where they are. The assistant can answer the import review for models whose gender, type or skin DCT cannot tell from their names; anything else the Add asks appears in DCT's window for you. |
| **remove\_items**                        | Removes items the way **Delete** does. Their files stay on disk. When your project replaces removed drawables with reserved dummies (**Project settings**), they stay as dummies and keep their numbers.                                                                                                                                                                                                                                                    |
| **undo** and **redo**                    | Undo or redo the latest change, as **Ctrl+Z** and **Ctrl+Y** do, whether you or the assistant made it.                                                                                                                                                                                                                                                                                                                                                      |
| **fix\_finding**                         | Runs a finding's Fix, as its **Fix** button in the **Error List** does, or its second Fix from the context menu.                                                                                                                                                                                                                                                                                                                                            |
| **fix\_safe\_findings**                  | Runs **Fix safe findings** for the whole project or for the items the assistant names, without the review list: it runs the repairs the review ticks for you, the ones that keep the look. The assistant runs those that can change how clothing looks only when you ask for them.                                                                                                                                                                          |
| **save\_project**                        | Saves the project, as **Ctrl+S** does. A project you never saved, or whose setup is not complete, is left for you to save.                                                                                                                                                                                                                                                                                                                                  |
| **list\_actions**                        | Lists every action of DCT's menus, item and variation menus, toolbars and shortcuts, with what it does, what it works on and the licence it needs, and says which ones an assistant leaves to you.                                                                                                                                                                                                                                                          |
| **run\_action**                          | Runs one of those actions on the items the assistant names, as its menu entry does.                                                                                                                                                                                                                                                                                                                                                                         |
| **build**                                | Builds the open project, as the **Build** button in the Build window does. See [Build](#build).                                                                                                                                                                                                                                                                                                                                                             |
| **get\_window**                          | Looks at DCT's open windows: every button, field, list and question with the words DCT shows, in your language, and a picture of the window. See [DCT's windows](#dcts-windows).                                                                                                                                                                                                                                                                            |
| **ui\_invoke**                           | Clicks a button, ticks a box, picks a tab or list entry, or opens a drop-down in one of DCT's windows, as your click would.                                                                                                                                                                                                                                                                                                                                 |
| **ui\_set\_value**                       | Types into a field, sets a number or a slider, chooses a drop-down entry or ticks a box in one of DCT's windows, as your typing would.                                                                                                                                                                                                                                                                                                                      |
| **get\_project\_settings**               | Reads your project's settings: resource and collection name, target, FiveM edition and game build, the build output folder, the options of **Project settings** and of the Build window, such as the Clothing Inspector, your tags and your saved outfits. See [Project settings, History and projects](#project-settings-history-and-projects).                                                                                                            |
| **update\_project\_settings**            | Changes those settings, as you would in **Project settings** and the Build window. One change is one undo step.                                                                                                                                                                                                                                                                                                                                             |
| **list\_recent\_projects**               | Lists the recent projects Home shows, newest first, with their names, when you last opened them and whether they are still there. It never sees where they are on your PC.                                                                                                                                                                                                                                                                                  |
| **close\_project**                       | Closes the project, as **Project > Close project** does, and DCT shows Home. It can save first; whether to drop unsaved changes is your answer.                                                                                                                                                                                                                                                                                                             |
| **list\_history**                        | Reads **Backups & History**: saves, checkpoints, tools that changed files and restores, newest first, and whether each can be restored.                                                                                                                                                                                                                                                                                                                     |
| **restore\_history**                     | Restores one entry, as **Backups & History** does. DCT first keeps the project as it is as a restore point, so you can go back.                                                                                                                                                                                                                                                                                                                             |
| **save\_checkpoint**                     | Saves a named checkpoint, as **Project > Save checkpoint...** does.                                                                                                                                                                                                                                                                                                                                                                                         |

Each change the assistant makes is one step in **Project > Recent changes**, named as your own changes are, so **Ctrl+Z** takes it back just as well. Changes stay in the open project until the assistant or you save it. A change of gender, type or number renumbers the items, as in **Item Details**; a list that is full keeps the item where it is.

No answer DCT gives an assistant is longer than 40,000 characters, so a large project does not overflow it. A longer answer, such as a long list of items or findings, an item with very many texture variations or a long guide page, stops there with whole entries and tells the assistant how to read the rest, which it then asks for on its own.

### Fixes

**fix\_finding** and **fix\_safe\_findings** work as the **Error List**'s own Fixes, on the finding's item, not on what you have selected. A Fix that opens an editor selects that item in the list first, as the **Error List** does:

* A Fix that rewrites files asks its usual question, which the assistant answers for you because it asked for the Fix. It keeps a restore point in **Backups & History**, and **Ctrl+Z** or the assistant's **undo** takes it back, as long as nothing changed the item since. **Fix safe findings** keeps one restore point for everything it repaired.
* A Fix that changes a setting, such as switching high heels on for a shoe, changes it at once.
* A Fix that opens a tool, such as the **Texture Optimizer**, a model's clean-up plan, the rig options or a file picker, opens it in DCT's window. The assistant is told which one opened, and you or the assistant finish the Fix there (see [DCT's windows](#dcts-windows)). While a window that holds DCT's main window is open, the assistant's changes wait: it is told DCT is busy. The rig options and the rig review stay open beside DCT, and the assistant leaves that item alone until you close them.
* A Fix that needs your sign-in or allowance starts as it does when you click it: with your sign-in, your allowance and its review for you.

After a Fix the assistant gets the findings that are left. When the **Error List** cannot run a Fix right now, for example for a dummy or a file it cannot change, the assistant is told why.

### Any menu action

Beyond the tools above, an assistant can run any action of DCT's menus and shortcuts that you could run yourself: for example **Remove all tags**, **Duplicate**, **Optimize textures...**, **Export as XML**, **Copy name**, **History**, a sort of the item list or a lighting of the 3D preview.

* It runs the action on the items it names, not on what you have selected, and your selection stays as it is. An action that shows or makes something selects it as its menu entry does: **Duplicate** selects the copy, **History** goes to the item.
* The action checks what it checks when you click it. When it does not apply, such as **Remove all tags** on an item without tags, the assistant is told why and nothing changes. An action that needs a licence your plan lacks makes no change, without the purchase window.
* An action's usual question appears in DCT's window for you, unless you asked the assistant to answer it. The questions only you answer stay yours.
* An action that opens a tool, such as the **Texture Optimizer**, opens it in DCT's window, and the assistant is told which one. You or the assistant finish there. A save or open dialog of Windows is yours to finish.
* Some actions are left to you, and the assistant is told why: buying or managing a licence, **Options**, project sync and Git, the **Send feedback** window, publishing and checking for updates. The assistant sends feedback you agreed to in its own way ([Feedback to the DCT team](#feedback-to-the-dct-team)) and sets up cloud and Git projects with its own tools ([Cloud and Git projects](#cloud-and-git-projects)). The tools inside windows, such as **Texture Studio**, **Model Studio** and the 3D preview's controls, are not menu actions: the assistant uses them in their window. For the **Error List**, it uses its own Fix tools.

### Build

An assistant can build the open project with the same checks, questions, licence and output as the Build window. It builds with your project's target, FiveM edition and output folder, or with others for that build only: your project keeps its own. The assistant follows the build's steps as they run, and afterwards it gets the built folders and the warnings the build logged.

* When the build asks something, such as splitting the project into several resources or building clothing for FiveM Enhanced, it stops before anything is written and the assistant gets the question. The assistant should ask you, then build again with your answer.
* When errors in the Error List stop the build, the assistant gets each item with its error. With your yes, it can build without those items for that build only, like **Build without these items** in the Build window; the result lists what it left out, and the next build stops again.
* Replacing an earlier build in the output folder is your answer alone: DCT asks in its window, and the assistant waits for you. If you say no, nothing is replaced.
* A Fix that changes your project's settings, such as **Build for FiveM Legacy**, is yours to choose too: when the assistant asks for it, DCT shows you the build's question in its window.
* DCT never builds into a protected folder, such as a drive's top folder, a Git repository's top folder, your project's own folders or your user, Desktop or Documents folder. The free plan's limits apply, without the purchase window.
* Like the Build window, the assistant builds a saved project only when it has a name and a project folder. A new project you never saved builds without them, as in the Build window: the resource name comes from its first item and the resource goes to `UserData\Builds\<resource name>` unless the assistant names another output folder. See [Build without saving the project first](https://docs.gta.clothing/basics/essential-knowledge/build-options.md#build-without-saving-the-project-first).

To build from a script without an assistant, see [Build from the command line](https://docs.gta.clothing/how-to-guides/build-from-the-command-line.md).

### DCT's windows

Tool windows such as the **Texture Optimizer**, **Model Studio**, **Fit to Body** or **Bulk edit metadata** have no tool of their own, so an assistant can work in them the way you do: it looks at the window, then clicks, ticks, types and chooses there. You see every step happen in the window.

* It sees what the window shows, in the language DCT shows, and a picture of the window. 3D views show empty in that picture; the assistant uses **capture\_preview** for the 3D preview.
* Its clicks and typing do exactly what yours would: the same checks, the same questions, the same licence, and the same steps in **Project > Recent changes**, so **Ctrl+Z** takes them back where it would take yours back.
* After each click it waits until DCT has settled, for up to about 10 seconds, and is told which windows opened or closed.
* When a click opens one of DCT's ordinary questions, such as **Save before optimizing?**, the question stays open in DCT's window and the assistant answers it there, as it would answer any of its own questions. Ask it to check with you first if you prefer.
* A window or question only you answer is shown to the assistant by its name only. When it tries to use one, it is told **Only the creator can answer this**, and the window waits for you. See [Questions only you answer](#questions-only-you-answer).
* The buttons of actions it leaves to you, such as **Disconnect**, **Check for updates**, **Send feedback**, publishing a mod or project sync, stay yours in the windows too.
* It reaches only Durty Cloth Tool's own windows, never another program's. Windows' own file pickers, such as a save dialog, are yours.
* It does not see your account or licence details in DCT's windows, and folders outside your project's folders show to it as `<local path>`.

### Project settings, History and projects

An assistant can set up your project for what you want to make before it builds, and bring back an earlier state when something went wrong.

* It reads and changes your project's settings under the same names: the resource and collection name, the target, FiveM edition and server game build, the build output folder, the options of **Project settings** (automatic saving, dummies, previews, duplicate warnings) and of the Build window (the Clothing Inspector, resource splitting, shop entries, integration files), and your tags. DCT checks every value as the windows do: a resource name single player does not take is refused, and so is an output folder no build may write into, such as a drive's top folder or the project's own folders. Switching on the Clothing Inspector needs a licence; without one the assistant is told so and DCT never shows it the purchase window.
* Each change of settings is one step in **Project > Recent changes**, so **Ctrl+Z** takes it back. Your own changes in **Project settings** are one step too: everything you change between opening the window, or coming back to it, and leaving it or closing it.
* Renaming the project or moving its data folder, the ped target, validation rules, body presets, the **Texture Optimizer** rules and project sync stay in their windows. Saved outfits change in the outfit panel.
* It sees the recent projects Home lists, by their place and name, and can open one by its place. It never sees where they are on your PC.
* It can close the project. When it has unsaved changes, DCT asks you whether to save them; the assistant cannot answer that.
* It lists **Backups & History** and restores an entry as you would there: a checkpoint, a save and a restore bring back the whole project, a tool's change its items. DCT first keeps the project as it is, unsaved edits included, as a restore point, so a restore can always be undone there. It also saves named checkpoints for you. Renaming and deleting checkpoints stay with you, in **Project > Checkpoints**.

{% hint style="info" %}
**A checkpoint before the assistant's first change.** Before an assistant changes a project for the first time while it is connected, DCT saves a checkpoint named after it, such as `Before Claude, 2026-11-09 14:30`. Restore it from **Project > Checkpoints** to undo everything the assistant did. DCT keeps the five newest of these per project and deletes older ones itself, never a checkpoint you saved; renaming one makes it yours. When all 50 checkpoints of a project are your own, DCT keeps a restore point in **Backups & History** instead and tells the assistant. A project you never saved has no History, so it gets none.
{% endhint %}

### 3D preview and in game

An assistant can look at the clothing it added or fixed, the way you would.

* It opens the 3D preview, puts the item on the ped in the texture variation it wants to check, turns the camera to the views that matter and takes a picture of each. It describes what it sees, such as a seam that shows through or a texture on the wrong part.
* The 3D preview reads your game files. If you have not confirmed your GTA V folder yet, the assistant asks you to open the 3D preview once and confirm it.
* Without a licence the 3D preview shows one model per run, for the assistant as for you. A second one needs a licence; DCT never shows the assistant the purchase window.
* The body choices are the ones the 3D preview offers: each item's own body preset, the stock body or one of your project's body presets.
* For a check in game, build your project with the Clothing Inspector, start the resource on your FiveM server, open the inspector with `I` or `/dctinspector`, press **Connect** and allow DCT's question. The assistant then sees that your game is connected and can put an item on the mannequin, as **Show in game** does, for you to look at. It needs a licence, as **Show in game** does. An item of a build the game has not loaded comes back as not loaded: build again and restart the resource.
* Without a connected game the assistant asks you to check the clothing in game and tells you how.

### Cloud and Git projects

An assistant can put your project in the cloud or in Git and keep it syncing, as you do in **Project sync**. It asks you first which one you want: keep the project on this PC, a cloud project, or Git.

* It can tell you whether the project stays on this PC, is a cloud project or a Git project, what sync is doing, which saves have not gone out yet, when it last synced and what stops it, with the fix **Project sync** offers. It also sees whether you are signed in to gta.clothing and GitHub, how many cloud projects your account keeps, and the names of the teams you can share with.
* It can make the open project a cloud project, for **Only me** or for one of your teams ([Share a Cloud Project with Your Team](https://docs.gta.clothing/share-and-sync/share-a-cloud-project-with-your-team.md)). Cloud projects need Ultimate on your gta.clothing account; without it the assistant is told so, and DCT never shows it the purchase window. Git needs no plan.
* It can connect the project to a Git repository you already have ([Sync a Project with GitHub](https://docs.gta.clothing/share-and-sync/sync-a-project-with-github.md), [Sync with Another Git Host](https://docs.gta.clothing/share-and-sync/sync-with-another-git-host.md)), create a new private repository for it on your GitHub account, or clone a Git project and open it ([Clone a Project from Git](https://docs.gta.clothing/share-and-sync/clone-a-project-from-git.md)). DCT never makes a repository public; you can do that on GitHub. Before it uploads your project into a public GitHub repository, DCT asks you.
* It can sync now, pause and resume sync, and for Git commit and push with a message of its own on top of DCT's summary of what changed.
* When a teammate changed the same thing as you, it lists the changes that wait for a choice and, after asking you, keeps yours (**Keep mine**) or takes theirs (**Use theirs**) for each, as **Review changes** and **Apply choices** do ([Review Sync Conflicts](https://docs.gta.clothing/share-and-sync/resolve-project-sync-conflicts.md)).
* Some steps are yours: signing in to gta.clothing or GitHub, letting DCT use a GitHub repository, signing in to another Git host, uploading into a public repository and sharing with a team. DCT asks you in its window, then opens the step for you: the sign-in page in your browser, **Project sync** with the code to enter on GitHub, or GitHub's page where you choose the repositories DCT may use. The assistant waits up to 5 minutes and never sees your sign-in, the code or any token.
* Stopping sync, moving a cloud project to the trash and deleting it stay in **Project sync**, for you. Teammates join your team in your account on gta.clothing.

### Feedback to the DCT team

When DCT cannot do something you asked for, or something goes wrong that the assistant cannot fix, it first checks DCT's guides, so it does not report something DCT already has. Then it tells you and asks whether to send it to the DCT team as a feature request or a problem report, with its recommendation.

* Nothing is sent unless you say yes in the conversation. Once you do, the assistant sends it right away, the same way **Help > Send feedback** does, and shows you the message that was sent.
* The message starts with a line saying an AI assistant sent it, what kind of report it is and which part of DCT it is about. Then come your request or problem in your words and what the assistant tried.
* Folder names in paths, your Windows user name, the name of this PC, e-mail addresses, IDs and keys are removed, as for your own feedback. Your recent log goes with it only when the assistant attaches it; it is told to use the log for problems and to say so when it asks you.
* An assistant sends at most three reports while it stays connected, and never the same report twice. See [Usage Data & Feedback](https://docs.gta.clothing/basics/good-to-know/usage-data-and-feedback.md#where-feedback-goes) for what happens to feedback.

### Questions only you answer

Some of DCT's questions are yours alone. When an assistant's change leads to one of them, DCT shows it in its window as always, with a line under it: **An AI assistant asked for this, and only you can answer it.** The assistant waits for your answer, at most 5 minutes. Then DCT closes the question as cancelled and makes no change, and the assistant is told that nobody answered. If you say no, the assistant is told you declined.

These questions are yours alone:

* replacing or deleting files or folders, build output included;
* creating a new project in a folder that already holds other files;
* closing the project without saving its changes;
* purchases, licences, signing in and your account;
* rights notices;
* the AI assistants switch and the other security settings in **Options**;
* Git access for project sync, signing in to a Git host and letting DCT use a GitHub repository;
* sharing a cloud project with your team;
* publishing something publicly;
* deleting something in the cloud.

Other questions a change raises, such as the import review, the assistant may answer through what it asked for. A question it did not answer appears in DCT's window too, with the line **An AI assistant asked for this and waits up to 5 minutes for your answer.**

The free plan's limits apply to an assistant's changes as to yours. When a change needs a licence or goes over a free limit, DCT makes no change and tells the assistant so; it never shows the assistant, or you, the purchase window for it.

Item numbers are numbers within the item's collection, as DCT's item list shows them, never global GTA drawable IDs. The pictures come from DCT's preview, which is not proof of how clothing looks in game: check it in game before you call it finished.

The assistant sees the project data folder and the build output folder, and file names inside the project, but no other folder on your PC: in DCT's windows, other folders show to it as `<local path>`.

When the assistant searches or reads the guides, DCT sends only the search words or the page address to docs.gta.clothing: nothing about you, your PC or your project.

### Projects and files from other people

Names, notes, creator details and file names in a project, and the text of the guides, reach the assistant as information about the project, never as requests: Durty Cloth Tool tells it that only your own messages ask it to change, delete, build or send anything, and the questions above stay yours whatever such text says. An assistant can still be misled, so when you work on a project someone shared with you or files you received, read what the assistant proposes and say no to a step you did not ask for. If it tells you that an item holds text that reads like an instruction, rename that item before you share or build the project.

## See what the assistant did

Click **Activity** in the status bar (or press **Ctrl+K** and paste `>AI assistant activity`) to open **AI assistant activity**. It lists what AI assistants did since DCT started, newest first: the time, what each step did in plain words, how it ended (done, nothing changed, you said no, cancelled and so on) and which AI app did it. **Show reads too** adds the steps that only read your project.

* **Undo latest change** undoes the newest change, as **Ctrl+Z** does, whoever made it.
* The restore button beside the step before which DCT saved its checkpoint (its tooltip says **Restore to before** and the AI app's name) puts the project back as it was before the assistant's first change. DCT asks you first, and keeps the project as it is now in **Backups & History**, so you can go back.

The list stays after the assistant disconnects and is cleared when DCT closes. Assistants cannot read or click this window.

## Disconnect or turn off

* **Disconnect** in the status bar ends the session of every connected assistant. AI assistants stay on, so your AI app can connect again when it next needs DCT. You can also press **Ctrl+K** and paste `>Disconnect AI assistants`, or give it a shortcut in **Options > Keybindings**.
* Untick **Let AI assistants control Durty Cloth Tool** to disconnect every assistant at once and keep them out until you turn it on again.
* Up to three AI apps can be connected at the same time.

## Troubleshooting

| Your AI app says                                                                                                   | What to do                                                                                                                                                                                                                                                                                                 |
| ------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Turn on AI assistants in DCT: Connected apps**                                                                   | Tick **Let AI assistants control Durty Cloth Tool** in **Options > Connected apps**, then reconnect the server in your AI app or restart it.                                                                                                                                                               |
| **Durty Cloth Tool did not answer within 60 seconds**                                                              | Open Durty Cloth Tool yourself, wait until its window is ready, check that **Let AI assistants control Durty Cloth Tool** is ticked, then reconnect.                                                                                                                                                       |
| The server failed to start or timed out, and DCT was closed                                                        | Some AI apps give a server only a few seconds to start. Open DCT first, or raise the app's startup timeout (for Codex, `startup_timeout_sec` above).                                                                                                                                                       |
| **This AI app runs with other Windows rights than Durty Cloth Tool**                                               | One of them runs as administrator (or in a sandbox) and the other does not. Start your AI app and Durty Cloth Tool the same way, then reconnect.                                                                                                                                                           |
| **Durty Cloth Tool already has 3 AI assistants connected**                                                         | Close an AI app you no longer use, or choose **Disconnect** in DCT's status bar, then reconnect.                                                                                                                                                                                                           |
| **dct.exe could not find the Durty Cloth Tool it belongs to**                                                      | Reinstall Durty Cloth Tool or unpack the portable version again, then choose **Update setup** (or **Add to**) for your AI app in **Options > Connected apps**. For an app without one-click setup, choose **Copy setup** again and replace the old entry.                                                  |
| Nothing happens after you moved the portable folder                                                                | The entry still points at the old folder. Open **Options > Connected apps** in the moved copy and choose **Update setup** for your AI app, or **Copy setup** for an app that is not listed.                                                                                                                |
| **DCT is busy**                                                                                                    | DCT is loading a project, building, saving, running another long step, or a window such as a file picker is open. The assistant waits a few seconds and tries again; close the open window if you are done with it.                                                                                        |
| **This project needs a licence**                                                                                   | The project is over the free plan's limits, so DCT did not open it for the assistant. Open the project yourself in DCT to buy or activate a licence, or remove items until it fits the free plan.                                                                                                          |
| **This goes over the free plan's limits and needs a licence**, **This needs a licence** or **This needs Ultimate** | The change needs a licence, or one with Ultimate. DCT made no change. Buy or activate a licence in DCT, then ask again.                                                                                                                                                                                    |
| **Nobody answered DCT's question**                                                                                 | A question only you can answer waited 5 minutes in DCT's window. DCT closed it and made no change. Ask the assistant to try again when you are at your PC.                                                                                                                                                 |
| **The creator declined DCT's question**                                                                            | You said no to a question the change asked. DCT made no change.                                                                                                                                                                                                                                            |
| **This Fix cannot run now**                                                                                        | The **Error List** cannot run this Fix for that finding, for the reason the message gives. Fix it another way, or ask the assistant for another Fix.                                                                                                                                                       |
| **The open project has no finding with the id**                                                                    | The finding is gone: it was fixed, or its item left the project. The assistant reads the **Error List** again.                                                                                                                                                                                             |
| **DCT added nothing**                                                                                              | The files were already in the project, could not be read or were left out, or a question about them was declined. DCT's status log in its window names each file.                                                                                                                                          |
| **The project was never saved**                                                                                    | Save the project once yourself with **Save As**; the assistant can save it after that.                                                                                                                                                                                                                     |
| **The project has no name yet** or **no project folder yet**                                                       | A saved project lost its name or project folder. Fill them in under **Project settings**, then ask the assistant to build again. The output folder the assistant names does not replace the project folder: that is where your project's own files live. A new project you never saved does not need them. |
| **DCT did not open the project**                                                                                   | You declined one of DCT's questions, or the file could not be read. DCT's status bar says why.                                                                                                                                                                                                             |
| **No preview yet**                                                                                                 | DCT has not made the item's preview picture yet. It makes them in the background while the project is open; ask again later. Tattoos and facial overlays have no stored preview.                                                                                                                           |
| **Open the 3D preview first** or **The 3D preview is not open**                                                    | Ask the assistant to show an item in the 3D preview, or open it in DCT and preview an item on the ped, then ask again.                                                                                                                                                                                     |
| **DCT has no confirmed GTA V folder yet**                                                                          | Open the 3D preview in DCT once and confirm your GTA V folder (or choose it in **Options**), then ask again.                                                                                                                                                                                               |
| **The 3D preview did not show the item in time**                                                                   | The preview was still loading or another item was chosen meanwhile. Ask again once the preview shows the ped.                                                                                                                                                                                              |
| **No game is connected to DCT**                                                                                    | Connect the in-game Clothing Inspector (see [3D preview and in game](#3d-preview-and-in-game)) or check the clothing in game yourself.                                                                                                                                                                     |
| **The creator turned off Let the in-game Clothing Inspector connect**                                              | Tick **Let the in-game Clothing Inspector connect** in **Options > Connected apps**, then connect the inspector again.                                                                                                                                                                                     |
| **Only the creator can answer this**                                                                               | The assistant tried to use a window or question that is yours alone, such as **Options** or a question that replaces files. Answer it yourself in DCT's window.                                                                                                                                            |
| **A window of DCT is open over this element's window**                                                             | A window in front, such as a question, holds the one behind it. Finish or close the window in front first, or let the assistant do it.                                                                                                                                                                     |
| **The element is disabled**                                                                                        | The button or field cannot be used yet, for the reason DCT shows beside it. Do what it asks first, or let the assistant do it.                                                                                                                                                                             |
| **Window automation does not use this element**                                                                    | The button runs something only you decide, such as an update or sending feedback. Use it yourself.                                                                                                                                                                                                         |
| **This element id belongs to another program**                                                                     | The assistant tried to reach another program's window. DCT reaches only its own windows; ask the assistant to read DCT's windows again.                                                                                                                                                                    |
| **Documentation unavailable**                                                                                      | DCT could not reach docs.gta.clothing in time, for example while your PC is offline. The assistant can read the list of every guide at [docs.gta.clothing/llms.txt](https://docs.gta.clothing/llms.txt) instead, or ask again in a moment.                                                                 |

## See also

* [Creator Link plugins](https://docs.gta.clothing/plugins/creator-link.md), for painting and modelling apps that connect to DCT through **Connected apps**.
