# Compatibility (/docs/compatibility)

Almost every FiveM script is written for ESX, QBCore or Qbox, so running them is a main goal. AI Core ships no third-party scripts and favours no vendor: you install your own.

## Three layers [#three-layers]

<Steps>
<Step>

### Framework bridge [#framework-bridge]

AI Core provides `es_extended`, `qb-core` and `qbx_core` and answers their exports, core objects and events, so scripts written for ESX, QBCore or Qbox see AI Core as their framework and run unchanged.

</Step>
<Step>

### Integrations [#integrations]

AI Core and the `ai-*` scripts need things other scripts provide: inventory, target, notify, phone, fuel, vehicle keys and more. Each category has one interface and each supported script is one adapter file. AI Core detects the installed script on start, and the admin panel can override the choice per category.

</Step>
<Step>

### Per-script notes [#per-script-notes]

Every tested third-party script gets a note: tested version, status and known limits.

</Step>
</Steps>

See the [compatible scripts](/scripts) list for what AI Core integrates with today.

## Adding a script [#adding-a-script]

Supporting a new script is one small, repeatable job: copy the category's adapter template, fill in its calls, add one line to the registry. You can ask your AI to do it.


# Introduction (/docs)

**AI Core** is a free, open-source FiveM framework built from the ground up with **TypeScript**, designed to make server development easier, smarter and more accessible to everyone.

Inspired by ESX and QBCore, AI Core combines an AI-friendly architecture, cross-framework compatibility, automatic resource integration and in-game management tools. Whether you are an experienced developer or have never written a line of code, you can build your server your way.

## Why AI Core [#why-ai-core]

<Cards>
  <Card title="Built for AI development">
    Dedicated AI instructions, development guidelines and one consistent TypeScript architecture.
  </Card>
  <Card title="ESX & QBCore compatibility">
    Designed to run existing ESX and QBCore scripts, including paid third-party resources.
  </Card>
  <Card title="Automatic script integration">
    Detects supported installed scripts and adapts related systems.
  </Card>
  <Card title="Manage everything in-game">
    Framework settings live in an in-game admin panel, not in config files.
  </Card>
</Cards>

## Next steps [#next-steps]

<Cards>
  <Card title="Installation" href="/docs/installation" />
  <Card title="Working with AI" href="/docs/working-with-ai" />
  <Card title="Compatibility" href="/docs/compatibility" />
</Cards>


# Installation (/docs/installation)

## Requirements [#requirements]

| Dependency | Version | Why |
| --- | --- | --- |
| FXServer (artifact) | 38039 or newer recommended | Newer builds let the server see player deaths itself. Older builds still run. |
| [Bun](https://bun.sh) | latest | Installs packages and builds the TypeScript resources. |
| MariaDB | latest | The database. |

## Setup [#setup]

<Steps>
<Step>

### Get the server data folder [#get-the-server-data-folder]

Clone [ai-core](https://github.com/aifivem/ai-core) into the folder you will use as your server data folder.

</Step>
<Step>

### Configure secrets [#configure-secrets]

Copy `env.example.cfg` to `env.cfg`, fill in your license key and the database connection, then create the database.

</Step>
<Step>

### Install and build [#install-and-build]

```bash
bun install
bun run build
```

</Step>
<Step>

### Start the server [#start-the-server]

Start FXServer (txAdmin) with this folder as the server data folder.

</Step>
</Steps>

## Layout [#layout]

| Path | What |
| --- | --- |
| `server.cfg`, `security.cfg`, `misc.cfg`, `permission.cfg` | Server config. Secrets go into `env.cfg`. |
| `resources/[ai]/` | AI Core resources, each `ai-*` folder its own git repo. |
| `resources/[standalone]/` | Third-party resources. |
| `packages/` | The `@aicore-fivem/*` npm packages. |
| `template/` | Template for new resources: `bun run new <name> "<description>"`. |


# Working with AI (/docs/working-with-ai)

AI Core is built so that someone who cannot code can ask an AI to change a script or write a new one, and get a result that fits.

Open your server data folder in Claude Code (or another coding agent: it reads `AGENTS.md`) and ask in your own words. The AI finds:

| File | What it holds |
| --- | --- |
| `CLAUDE.md` | Goals, structure, decisions, the build and check process. |
| `.claude/rules/` | Topic rules that load when matching files are edited. |
| `.claude/skills/aicore-fivem`, `aicore-ui`, `aicore-mysql` | FiveM engine, NUI and SQL knowledge. |
| `resources/[ai]/<script>/CLAUDE.md` | What each script does and why. |
| `docs/compat/` | Framework surfaces and notes on third-party scripts. |

<Callout type="warn">
Testing generated code is still recommended before you put it on a live server.
</Callout>

## Do I need AI? [#do-i-need-ai]

No. AI-assisted development is optional. AI Core works as a regular FiveM framework and needs no AI service to run.

## Read these docs with your AI [#read-these-docs-with-your-ai]

Every page here is also available as Markdown: add `.md` to its URL, or use the **Copy Markdown** button at the top of the page. The whole documentation is at [`/llms-full.txt`](/llms-full.txt).


# Uyumluluk (/tr/docs/compatibility)

FiveM scriptlerinin neredeyse hepsi ESX, QBCore ya da Qbox için yazılıyor, bu yüzden onları çalıştırmak ana hedeflerden biri. AI Core hiçbir üçüncü parti scripti içinde getirmez ve hiçbir satıcıyı kayırmaz: scriptlerini sen kurarsın.

## Üç katman [#üç-katman]

<Steps>
<Step>

### Framework köprüsü [#framework-köprüsü]

AI Core `es_extended`, `qb-core` ve `qbx_core` adlarını sağlar ve onların export’larına, core objelerine ve event’lerine cevap verir. Böylece ESX, QBCore ya da Qbox için yazılmış scriptler AI Core’u kendi framework’leri olarak görür ve değişiklik yapmadan çalışır.

</Step>
<Step>

### Entegrasyonlar [#entegrasyonlar]

AI Core ve `ai-*` scriptleri, başka scriptlerin sağladığı şeylere ihtiyaç duyar: envanter, target, bildirim, telefon, yakıt, araç anahtarı ve daha fazlası. Her kategorinin tek bir arayüzü var, desteklenen her script tek bir adapter dosyası. AI Core açılışta kurulu scripti bulur, yönetim panelinden her kategori için seçimi değiştirebilirsin.

</Step>
<Step>

### Script notları [#script-notları]

Test edilen her üçüncü parti script için bir not tutulur: test edilen sürüm, durum ve bilinen sınırlar.

</Step>
</Steps>

AI Core’un bugün hangi scriptlerle entegre olduğunu [uyumlu scriptler](/tr/scripts) listesinde görebilirsin.

## Script eklemek [#script-eklemek]

Yeni bir scripte destek eklemek küçük ve tekrarlanabilir bir iş: kategorinin adapter şablonunu kopyala, çağrılarını doldur, registry’ye bir satır ekle. Bunu yapay zekâna da yaptırabilirsin.


# Giriş (/tr/docs)

**AI Core**, **TypeScript** ile sıfırdan yazılmış, ücretsiz ve açık kaynak bir FiveM framework’ü. Amacı sunucu geliştirmeyi daha kolay, daha akıllı ve herkes için erişilebilir kılmak.

ESX ve QBCore’dan ilham alan AI Core; yapay zekâ dostu mimariyi, framework’ler arası uyumu, otomatik script entegrasyonunu ve oyun içi yönetim araçlarını bir araya getiriyor. İster deneyimli bir geliştirici ol ister hiç kod yazmamış biri, sunucunu istediğin gibi kurabilirsin.

## Neden AI Core [#neden-ai-core]

<Cards>
  <Card title="Yapay zekâyla geliştirme için tasarlandı">
    Yapay zekâ talimatları, geliştirme kuralları ve tutarlı bir TypeScript mimarisi.
  </Card>
  <Card title="ESX ve QBCore uyumu">
    Ücretli üçüncü parti scriptler dahil mevcut ESX ve QBCore scriptlerini çalıştıracak şekilde tasarlandı.
  </Card>
  <Card title="Otomatik script entegrasyonu">
    Kurulu desteklenen scriptleri tanır ve ilgili sistemleri ona göre ayarlar.
  </Card>
  <Card title="Her şeyi oyun içinden yönet">
    Framework ayarları config dosyalarında değil, oyun içi yönetim panelinde.
  </Card>
</Cards>

## Sonraki adımlar [#sonraki-adımlar]

<Cards>
  <Card title="Kurulum" href="/tr/docs/installation" />
  <Card title="Yapay zekâyla çalışmak" href="/tr/docs/working-with-ai" />
  <Card title="Uyumluluk" href="/tr/docs/compatibility" />
</Cards>


# Kurulum (/tr/docs/installation)

## Gereksinimler [#gereksinimler]

| Bağımlılık | Sürüm | Neden |
| --- | --- | --- |
| FXServer (artifact) | 38039 veya daha yenisi önerilir | Yeni sürümlerde sunucu oyuncu ölümlerini kendisi görür. Eski sürümler de çalışır. |
| [Bun](https://bun.sh) | güncel | Paketleri kurar ve TypeScript resource’larını derler. |
| MariaDB | güncel | Veritabanı. |

## Kurulum adımları [#kurulum-adımları]

<Steps>
<Step>

### Sunucu klasörünü al [#sunucu-klasörünü-al]

[ai-core](https://github.com/aifivem/ai-core) reposunu sunucu veri klasörü olarak kullanacağın klasöre klonla.

</Step>
<Step>

### Gizli bilgileri ayarla [#gizli-bilgileri-ayarla]

`env.example.cfg` dosyasını `env.cfg` olarak kopyala, lisans anahtarını ve veritabanı bağlantısını gir, ardından veritabanını oluştur.

</Step>
<Step>

### Paketleri kur ve derle [#paketleri-kur-ve-derle]

```bash
bun install
bun run build
```

</Step>
<Step>

### Sunucuyu başlat [#sunucuyu-başlat]

FXServer’ı (txAdmin) bu klasörü sunucu veri klasörü olarak göstererek başlat.

</Step>
</Steps>

## Klasör yapısı [#klasör-yapısı]

| Yol | Ne |
| --- | --- |
| `server.cfg`, `security.cfg`, `misc.cfg`, `permission.cfg` | Sunucu ayarları. Gizli bilgiler `env.cfg` dosyasına gider. |
| `resources/[ai]/` | AI Core resource’ları, her `ai-*` klasörü ayrı bir git reposu. |
| `resources/[standalone]/` | Üçüncü parti resource’lar. |
| `packages/` | `@aicore-fivem/*` npm paketleri. |
| `template/` | Yeni resource şablonu: `bun run new <isim> "<açıklama>"`. |


# Yapay zekâyla çalışmak (/tr/docs/working-with-ai)

AI Core, kod bilmeyen birinin bir yapay zekâdan script değiştirmesini ya da yeni script yazmasını isteyip projeye uyan bir sonuç alabileceği şekilde kuruldu.

Sunucu veri klasörünü Claude Code’da (ya da `AGENTS.md` dosyasını okuyan başka bir kodlama ajanında) aç ve kendi cümlelerinle iste. Yapay zekâ şunları bulur:

| Dosya | İçinde ne var |
| --- | --- |
| `CLAUDE.md` | Hedefler, yapı, kararlar, derleme ve kontrol süreci. |
| `.claude/rules/` | İlgili dosyalar düzenlenirken yüklenen konu kuralları. |
| `.claude/skills/aicore-fivem`, `aicore-ui`, `aicore-mysql` | FiveM motoru, NUI ve SQL bilgisi. |
| `resources/[ai]/<script>/CLAUDE.md` | Her scriptin ne yaptığı ve neden. |
| `docs/compat/` | Framework yüzeyleri ve üçüncü parti scriptlerle ilgili notlar. |

<Callout type="warn">
Üretilen kodu canlı sunucuya koymadan önce test etmeni öneririz.
</Callout>

## Yapay zekâ şart mı? [#yapay-zekâ-şart-mı]

Hayır. Yapay zekâ destekli geliştirme isteğe bağlı. AI Core normal bir FiveM framework’ü gibi çalışır ve hiçbir yapay zekâ servisine ihtiyaç duymaz.

## Bu dokümanları yapay zekâna okut [#bu-dokümanları-yapay-zekâna-okut]

Buradaki her sayfa Markdown olarak da var: adresin sonuna `.md` ekle ya da sayfanın üstündeki **Markdown’ı kopyala** düğmesini kullan. Dokümanların tamamı [`/llms-full.txt`](/llms-full.txt) adresinde.


# Compatibility (/de/docs/compatibility)

Almost every FiveM script is written for ESX, QBCore or Qbox, so running them is a main goal. AI Core ships no third-party scripts and favours no vendor: you install your own.

## Three layers [#three-layers]

<Steps>
<Step>

### Framework bridge [#framework-bridge]

AI Core provides `es_extended`, `qb-core` and `qbx_core` and answers their exports, core objects and events, so scripts written for ESX, QBCore or Qbox see AI Core as their framework and run unchanged.

</Step>
<Step>

### Integrations [#integrations]

AI Core and the `ai-*` scripts need things other scripts provide: inventory, target, notify, phone, fuel, vehicle keys and more. Each category has one interface and each supported script is one adapter file. AI Core detects the installed script on start, and the admin panel can override the choice per category.

</Step>
<Step>

### Per-script notes [#per-script-notes]

Every tested third-party script gets a note: tested version, status and known limits.

</Step>
</Steps>

See the [compatible scripts](/scripts) list for what AI Core integrates with today.

## Adding a script [#adding-a-script]

Supporting a new script is one small, repeatable job: copy the category's adapter template, fill in its calls, add one line to the registry. You can ask your AI to do it.


# Introduction (/de/docs)

**AI Core** is a free, open-source FiveM framework built from the ground up with **TypeScript**, designed to make server development easier, smarter and more accessible to everyone.

Inspired by ESX and QBCore, AI Core combines an AI-friendly architecture, cross-framework compatibility, automatic resource integration and in-game management tools. Whether you are an experienced developer or have never written a line of code, you can build your server your way.

## Why AI Core [#why-ai-core]

<Cards>
  <Card title="Built for AI development">
    Dedicated AI instructions, development guidelines and one consistent TypeScript architecture.
  </Card>
  <Card title="ESX & QBCore compatibility">
    Designed to run existing ESX and QBCore scripts, including paid third-party resources.
  </Card>
  <Card title="Automatic script integration">
    Detects supported installed scripts and adapts related systems.
  </Card>
  <Card title="Manage everything in-game">
    Framework settings live in an in-game admin panel, not in config files.
  </Card>
</Cards>

## Next steps [#next-steps]

<Cards>
  <Card title="Installation" href="/docs/installation" />
  <Card title="Working with AI" href="/docs/working-with-ai" />
  <Card title="Compatibility" href="/docs/compatibility" />
</Cards>


# Installation (/de/docs/installation)

## Requirements [#requirements]

| Dependency | Version | Why |
| --- | --- | --- |
| FXServer (artifact) | 38039 or newer recommended | Newer builds let the server see player deaths itself. Older builds still run. |
| [Bun](https://bun.sh) | latest | Installs packages and builds the TypeScript resources. |
| MariaDB | latest | The database. |

## Setup [#setup]

<Steps>
<Step>

### Get the server data folder [#get-the-server-data-folder]

Clone [ai-core](https://github.com/aifivem/ai-core) into the folder you will use as your server data folder.

</Step>
<Step>

### Configure secrets [#configure-secrets]

Copy `env.example.cfg` to `env.cfg`, fill in your license key and the database connection, then create the database.

</Step>
<Step>

### Install and build [#install-and-build]

```bash
bun install
bun run build
```

</Step>
<Step>

### Start the server [#start-the-server]

Start FXServer (txAdmin) with this folder as the server data folder.

</Step>
</Steps>

## Layout [#layout]

| Path | What |
| --- | --- |
| `server.cfg`, `security.cfg`, `misc.cfg`, `permission.cfg` | Server config. Secrets go into `env.cfg`. |
| `resources/[ai]/` | AI Core resources, each `ai-*` folder its own git repo. |
| `resources/[standalone]/` | Third-party resources. |
| `packages/` | The `@aicore-fivem/*` npm packages. |
| `template/` | Template for new resources: `bun run new <name> "<description>"`. |


# Working with AI (/de/docs/working-with-ai)

AI Core is built so that someone who cannot code can ask an AI to change a script or write a new one, and get a result that fits.

Open your server data folder in Claude Code (or another coding agent: it reads `AGENTS.md`) and ask in your own words. The AI finds:

| File | What it holds |
| --- | --- |
| `CLAUDE.md` | Goals, structure, decisions, the build and check process. |
| `.claude/rules/` | Topic rules that load when matching files are edited. |
| `.claude/skills/aicore-fivem`, `aicore-ui`, `aicore-mysql` | FiveM engine, NUI and SQL knowledge. |
| `resources/[ai]/<script>/CLAUDE.md` | What each script does and why. |
| `docs/compat/` | Framework surfaces and notes on third-party scripts. |

<Callout type="warn">
Testing generated code is still recommended before you put it on a live server.
</Callout>

## Do I need AI? [#do-i-need-ai]

No. AI-assisted development is optional. AI Core works as a regular FiveM framework and needs no AI service to run.

## Read these docs with your AI [#read-these-docs-with-your-ai]

Every page here is also available as Markdown: add `.md` to its URL, or use the **Copy Markdown** button at the top of the page. The whole documentation is at [`/llms-full.txt`](/llms-full.txt).


# Compatibility (/fr/docs/compatibility)

Almost every FiveM script is written for ESX, QBCore or Qbox, so running them is a main goal. AI Core ships no third-party scripts and favours no vendor: you install your own.

## Three layers [#three-layers]

<Steps>
<Step>

### Framework bridge [#framework-bridge]

AI Core provides `es_extended`, `qb-core` and `qbx_core` and answers their exports, core objects and events, so scripts written for ESX, QBCore or Qbox see AI Core as their framework and run unchanged.

</Step>
<Step>

### Integrations [#integrations]

AI Core and the `ai-*` scripts need things other scripts provide: inventory, target, notify, phone, fuel, vehicle keys and more. Each category has one interface and each supported script is one adapter file. AI Core detects the installed script on start, and the admin panel can override the choice per category.

</Step>
<Step>

### Per-script notes [#per-script-notes]

Every tested third-party script gets a note: tested version, status and known limits.

</Step>
</Steps>

See the [compatible scripts](/scripts) list for what AI Core integrates with today.

## Adding a script [#adding-a-script]

Supporting a new script is one small, repeatable job: copy the category's adapter template, fill in its calls, add one line to the registry. You can ask your AI to do it.


# Introduction (/fr/docs)

**AI Core** is a free, open-source FiveM framework built from the ground up with **TypeScript**, designed to make server development easier, smarter and more accessible to everyone.

Inspired by ESX and QBCore, AI Core combines an AI-friendly architecture, cross-framework compatibility, automatic resource integration and in-game management tools. Whether you are an experienced developer or have never written a line of code, you can build your server your way.

## Why AI Core [#why-ai-core]

<Cards>
  <Card title="Built for AI development">
    Dedicated AI instructions, development guidelines and one consistent TypeScript architecture.
  </Card>
  <Card title="ESX & QBCore compatibility">
    Designed to run existing ESX and QBCore scripts, including paid third-party resources.
  </Card>
  <Card title="Automatic script integration">
    Detects supported installed scripts and adapts related systems.
  </Card>
  <Card title="Manage everything in-game">
    Framework settings live in an in-game admin panel, not in config files.
  </Card>
</Cards>

## Next steps [#next-steps]

<Cards>
  <Card title="Installation" href="/docs/installation" />
  <Card title="Working with AI" href="/docs/working-with-ai" />
  <Card title="Compatibility" href="/docs/compatibility" />
</Cards>


# Installation (/fr/docs/installation)

## Requirements [#requirements]

| Dependency | Version | Why |
| --- | --- | --- |
| FXServer (artifact) | 38039 or newer recommended | Newer builds let the server see player deaths itself. Older builds still run. |
| [Bun](https://bun.sh) | latest | Installs packages and builds the TypeScript resources. |
| MariaDB | latest | The database. |

## Setup [#setup]

<Steps>
<Step>

### Get the server data folder [#get-the-server-data-folder]

Clone [ai-core](https://github.com/aifivem/ai-core) into the folder you will use as your server data folder.

</Step>
<Step>

### Configure secrets [#configure-secrets]

Copy `env.example.cfg` to `env.cfg`, fill in your license key and the database connection, then create the database.

</Step>
<Step>

### Install and build [#install-and-build]

```bash
bun install
bun run build
```

</Step>
<Step>

### Start the server [#start-the-server]

Start FXServer (txAdmin) with this folder as the server data folder.

</Step>
</Steps>

## Layout [#layout]

| Path | What |
| --- | --- |
| `server.cfg`, `security.cfg`, `misc.cfg`, `permission.cfg` | Server config. Secrets go into `env.cfg`. |
| `resources/[ai]/` | AI Core resources, each `ai-*` folder its own git repo. |
| `resources/[standalone]/` | Third-party resources. |
| `packages/` | The `@aicore-fivem/*` npm packages. |
| `template/` | Template for new resources: `bun run new <name> "<description>"`. |


# Working with AI (/fr/docs/working-with-ai)

AI Core is built so that someone who cannot code can ask an AI to change a script or write a new one, and get a result that fits.

Open your server data folder in Claude Code (or another coding agent: it reads `AGENTS.md`) and ask in your own words. The AI finds:

| File | What it holds |
| --- | --- |
| `CLAUDE.md` | Goals, structure, decisions, the build and check process. |
| `.claude/rules/` | Topic rules that load when matching files are edited. |
| `.claude/skills/aicore-fivem`, `aicore-ui`, `aicore-mysql` | FiveM engine, NUI and SQL knowledge. |
| `resources/[ai]/<script>/CLAUDE.md` | What each script does and why. |
| `docs/compat/` | Framework surfaces and notes on third-party scripts. |

<Callout type="warn">
Testing generated code is still recommended before you put it on a live server.
</Callout>

## Do I need AI? [#do-i-need-ai]

No. AI-assisted development is optional. AI Core works as a regular FiveM framework and needs no AI service to run.

## Read these docs with your AI [#read-these-docs-with-your-ai]

Every page here is also available as Markdown: add `.md` to its URL, or use the **Copy Markdown** button at the top of the page. The whole documentation is at [`/llms-full.txt`](/llms-full.txt).


# Compatibility (/es/docs/compatibility)

Almost every FiveM script is written for ESX, QBCore or Qbox, so running them is a main goal. AI Core ships no third-party scripts and favours no vendor: you install your own.

## Three layers [#three-layers]

<Steps>
<Step>

### Framework bridge [#framework-bridge]

AI Core provides `es_extended`, `qb-core` and `qbx_core` and answers their exports, core objects and events, so scripts written for ESX, QBCore or Qbox see AI Core as their framework and run unchanged.

</Step>
<Step>

### Integrations [#integrations]

AI Core and the `ai-*` scripts need things other scripts provide: inventory, target, notify, phone, fuel, vehicle keys and more. Each category has one interface and each supported script is one adapter file. AI Core detects the installed script on start, and the admin panel can override the choice per category.

</Step>
<Step>

### Per-script notes [#per-script-notes]

Every tested third-party script gets a note: tested version, status and known limits.

</Step>
</Steps>

See the [compatible scripts](/scripts) list for what AI Core integrates with today.

## Adding a script [#adding-a-script]

Supporting a new script is one small, repeatable job: copy the category's adapter template, fill in its calls, add one line to the registry. You can ask your AI to do it.


# Introduction (/es/docs)

**AI Core** is a free, open-source FiveM framework built from the ground up with **TypeScript**, designed to make server development easier, smarter and more accessible to everyone.

Inspired by ESX and QBCore, AI Core combines an AI-friendly architecture, cross-framework compatibility, automatic resource integration and in-game management tools. Whether you are an experienced developer or have never written a line of code, you can build your server your way.

## Why AI Core [#why-ai-core]

<Cards>
  <Card title="Built for AI development">
    Dedicated AI instructions, development guidelines and one consistent TypeScript architecture.
  </Card>
  <Card title="ESX & QBCore compatibility">
    Designed to run existing ESX and QBCore scripts, including paid third-party resources.
  </Card>
  <Card title="Automatic script integration">
    Detects supported installed scripts and adapts related systems.
  </Card>
  <Card title="Manage everything in-game">
    Framework settings live in an in-game admin panel, not in config files.
  </Card>
</Cards>

## Next steps [#next-steps]

<Cards>
  <Card title="Installation" href="/docs/installation" />
  <Card title="Working with AI" href="/docs/working-with-ai" />
  <Card title="Compatibility" href="/docs/compatibility" />
</Cards>


# Installation (/es/docs/installation)

## Requirements [#requirements]

| Dependency | Version | Why |
| --- | --- | --- |
| FXServer (artifact) | 38039 or newer recommended | Newer builds let the server see player deaths itself. Older builds still run. |
| [Bun](https://bun.sh) | latest | Installs packages and builds the TypeScript resources. |
| MariaDB | latest | The database. |

## Setup [#setup]

<Steps>
<Step>

### Get the server data folder [#get-the-server-data-folder]

Clone [ai-core](https://github.com/aifivem/ai-core) into the folder you will use as your server data folder.

</Step>
<Step>

### Configure secrets [#configure-secrets]

Copy `env.example.cfg` to `env.cfg`, fill in your license key and the database connection, then create the database.

</Step>
<Step>

### Install and build [#install-and-build]

```bash
bun install
bun run build
```

</Step>
<Step>

### Start the server [#start-the-server]

Start FXServer (txAdmin) with this folder as the server data folder.

</Step>
</Steps>

## Layout [#layout]

| Path | What |
| --- | --- |
| `server.cfg`, `security.cfg`, `misc.cfg`, `permission.cfg` | Server config. Secrets go into `env.cfg`. |
| `resources/[ai]/` | AI Core resources, each `ai-*` folder its own git repo. |
| `resources/[standalone]/` | Third-party resources. |
| `packages/` | The `@aicore-fivem/*` npm packages. |
| `template/` | Template for new resources: `bun run new <name> "<description>"`. |


# Working with AI (/es/docs/working-with-ai)

AI Core is built so that someone who cannot code can ask an AI to change a script or write a new one, and get a result that fits.

Open your server data folder in Claude Code (or another coding agent: it reads `AGENTS.md`) and ask in your own words. The AI finds:

| File | What it holds |
| --- | --- |
| `CLAUDE.md` | Goals, structure, decisions, the build and check process. |
| `.claude/rules/` | Topic rules that load when matching files are edited. |
| `.claude/skills/aicore-fivem`, `aicore-ui`, `aicore-mysql` | FiveM engine, NUI and SQL knowledge. |
| `resources/[ai]/<script>/CLAUDE.md` | What each script does and why. |
| `docs/compat/` | Framework surfaces and notes on third-party scripts. |

<Callout type="warn">
Testing generated code is still recommended before you put it on a live server.
</Callout>

## Do I need AI? [#do-i-need-ai]

No. AI-assisted development is optional. AI Core works as a regular FiveM framework and needs no AI service to run.

## Read these docs with your AI [#read-these-docs-with-your-ai]

Every page here is also available as Markdown: add `.md` to its URL, or use the **Copy Markdown** button at the top of the page. The whole documentation is at [`/llms-full.txt`](/llms-full.txt).


# Compatibility (/pt/docs/compatibility)

Almost every FiveM script is written for ESX, QBCore or Qbox, so running them is a main goal. AI Core ships no third-party scripts and favours no vendor: you install your own.

## Three layers [#three-layers]

<Steps>
<Step>

### Framework bridge [#framework-bridge]

AI Core provides `es_extended`, `qb-core` and `qbx_core` and answers their exports, core objects and events, so scripts written for ESX, QBCore or Qbox see AI Core as their framework and run unchanged.

</Step>
<Step>

### Integrations [#integrations]

AI Core and the `ai-*` scripts need things other scripts provide: inventory, target, notify, phone, fuel, vehicle keys and more. Each category has one interface and each supported script is one adapter file. AI Core detects the installed script on start, and the admin panel can override the choice per category.

</Step>
<Step>

### Per-script notes [#per-script-notes]

Every tested third-party script gets a note: tested version, status and known limits.

</Step>
</Steps>

See the [compatible scripts](/scripts) list for what AI Core integrates with today.

## Adding a script [#adding-a-script]

Supporting a new script is one small, repeatable job: copy the category's adapter template, fill in its calls, add one line to the registry. You can ask your AI to do it.


# Introduction (/pt/docs)

**AI Core** is a free, open-source FiveM framework built from the ground up with **TypeScript**, designed to make server development easier, smarter and more accessible to everyone.

Inspired by ESX and QBCore, AI Core combines an AI-friendly architecture, cross-framework compatibility, automatic resource integration and in-game management tools. Whether you are an experienced developer or have never written a line of code, you can build your server your way.

## Why AI Core [#why-ai-core]

<Cards>
  <Card title="Built for AI development">
    Dedicated AI instructions, development guidelines and one consistent TypeScript architecture.
  </Card>
  <Card title="ESX & QBCore compatibility">
    Designed to run existing ESX and QBCore scripts, including paid third-party resources.
  </Card>
  <Card title="Automatic script integration">
    Detects supported installed scripts and adapts related systems.
  </Card>
  <Card title="Manage everything in-game">
    Framework settings live in an in-game admin panel, not in config files.
  </Card>
</Cards>

## Next steps [#next-steps]

<Cards>
  <Card title="Installation" href="/docs/installation" />
  <Card title="Working with AI" href="/docs/working-with-ai" />
  <Card title="Compatibility" href="/docs/compatibility" />
</Cards>


# Installation (/pt/docs/installation)

## Requirements [#requirements]

| Dependency | Version | Why |
| --- | --- | --- |
| FXServer (artifact) | 38039 or newer recommended | Newer builds let the server see player deaths itself. Older builds still run. |
| [Bun](https://bun.sh) | latest | Installs packages and builds the TypeScript resources. |
| MariaDB | latest | The database. |

## Setup [#setup]

<Steps>
<Step>

### Get the server data folder [#get-the-server-data-folder]

Clone [ai-core](https://github.com/aifivem/ai-core) into the folder you will use as your server data folder.

</Step>
<Step>

### Configure secrets [#configure-secrets]

Copy `env.example.cfg` to `env.cfg`, fill in your license key and the database connection, then create the database.

</Step>
<Step>

### Install and build [#install-and-build]

```bash
bun install
bun run build
```

</Step>
<Step>

### Start the server [#start-the-server]

Start FXServer (txAdmin) with this folder as the server data folder.

</Step>
</Steps>

## Layout [#layout]

| Path | What |
| --- | --- |
| `server.cfg`, `security.cfg`, `misc.cfg`, `permission.cfg` | Server config. Secrets go into `env.cfg`. |
| `resources/[ai]/` | AI Core resources, each `ai-*` folder its own git repo. |
| `resources/[standalone]/` | Third-party resources. |
| `packages/` | The `@aicore-fivem/*` npm packages. |
| `template/` | Template for new resources: `bun run new <name> "<description>"`. |


# Working with AI (/pt/docs/working-with-ai)

AI Core is built so that someone who cannot code can ask an AI to change a script or write a new one, and get a result that fits.

Open your server data folder in Claude Code (or another coding agent: it reads `AGENTS.md`) and ask in your own words. The AI finds:

| File | What it holds |
| --- | --- |
| `CLAUDE.md` | Goals, structure, decisions, the build and check process. |
| `.claude/rules/` | Topic rules that load when matching files are edited. |
| `.claude/skills/aicore-fivem`, `aicore-ui`, `aicore-mysql` | FiveM engine, NUI and SQL knowledge. |
| `resources/[ai]/<script>/CLAUDE.md` | What each script does and why. |
| `docs/compat/` | Framework surfaces and notes on third-party scripts. |

<Callout type="warn">
Testing generated code is still recommended before you put it on a live server.
</Callout>

## Do I need AI? [#do-i-need-ai]

No. AI-assisted development is optional. AI Core works as a regular FiveM framework and needs no AI service to run.

## Read these docs with your AI [#read-these-docs-with-your-ai]

Every page here is also available as Markdown: add `.md` to its URL, or use the **Copy Markdown** button at the top of the page. The whole documentation is at [`/llms-full.txt`](/llms-full.txt).


# Compatibility (/pl/docs/compatibility)

Almost every FiveM script is written for ESX, QBCore or Qbox, so running them is a main goal. AI Core ships no third-party scripts and favours no vendor: you install your own.

## Three layers [#three-layers]

<Steps>
<Step>

### Framework bridge [#framework-bridge]

AI Core provides `es_extended`, `qb-core` and `qbx_core` and answers their exports, core objects and events, so scripts written for ESX, QBCore or Qbox see AI Core as their framework and run unchanged.

</Step>
<Step>

### Integrations [#integrations]

AI Core and the `ai-*` scripts need things other scripts provide: inventory, target, notify, phone, fuel, vehicle keys and more. Each category has one interface and each supported script is one adapter file. AI Core detects the installed script on start, and the admin panel can override the choice per category.

</Step>
<Step>

### Per-script notes [#per-script-notes]

Every tested third-party script gets a note: tested version, status and known limits.

</Step>
</Steps>

See the [compatible scripts](/scripts) list for what AI Core integrates with today.

## Adding a script [#adding-a-script]

Supporting a new script is one small, repeatable job: copy the category's adapter template, fill in its calls, add one line to the registry. You can ask your AI to do it.


# Introduction (/pl/docs)

**AI Core** is a free, open-source FiveM framework built from the ground up with **TypeScript**, designed to make server development easier, smarter and more accessible to everyone.

Inspired by ESX and QBCore, AI Core combines an AI-friendly architecture, cross-framework compatibility, automatic resource integration and in-game management tools. Whether you are an experienced developer or have never written a line of code, you can build your server your way.

## Why AI Core [#why-ai-core]

<Cards>
  <Card title="Built for AI development">
    Dedicated AI instructions, development guidelines and one consistent TypeScript architecture.
  </Card>
  <Card title="ESX & QBCore compatibility">
    Designed to run existing ESX and QBCore scripts, including paid third-party resources.
  </Card>
  <Card title="Automatic script integration">
    Detects supported installed scripts and adapts related systems.
  </Card>
  <Card title="Manage everything in-game">
    Framework settings live in an in-game admin panel, not in config files.
  </Card>
</Cards>

## Next steps [#next-steps]

<Cards>
  <Card title="Installation" href="/docs/installation" />
  <Card title="Working with AI" href="/docs/working-with-ai" />
  <Card title="Compatibility" href="/docs/compatibility" />
</Cards>


# Installation (/pl/docs/installation)

## Requirements [#requirements]

| Dependency | Version | Why |
| --- | --- | --- |
| FXServer (artifact) | 38039 or newer recommended | Newer builds let the server see player deaths itself. Older builds still run. |
| [Bun](https://bun.sh) | latest | Installs packages and builds the TypeScript resources. |
| MariaDB | latest | The database. |

## Setup [#setup]

<Steps>
<Step>

### Get the server data folder [#get-the-server-data-folder]

Clone [ai-core](https://github.com/aifivem/ai-core) into the folder you will use as your server data folder.

</Step>
<Step>

### Configure secrets [#configure-secrets]

Copy `env.example.cfg` to `env.cfg`, fill in your license key and the database connection, then create the database.

</Step>
<Step>

### Install and build [#install-and-build]

```bash
bun install
bun run build
```

</Step>
<Step>

### Start the server [#start-the-server]

Start FXServer (txAdmin) with this folder as the server data folder.

</Step>
</Steps>

## Layout [#layout]

| Path | What |
| --- | --- |
| `server.cfg`, `security.cfg`, `misc.cfg`, `permission.cfg` | Server config. Secrets go into `env.cfg`. |
| `resources/[ai]/` | AI Core resources, each `ai-*` folder its own git repo. |
| `resources/[standalone]/` | Third-party resources. |
| `packages/` | The `@aicore-fivem/*` npm packages. |
| `template/` | Template for new resources: `bun run new <name> "<description>"`. |


# Working with AI (/pl/docs/working-with-ai)

AI Core is built so that someone who cannot code can ask an AI to change a script or write a new one, and get a result that fits.

Open your server data folder in Claude Code (or another coding agent: it reads `AGENTS.md`) and ask in your own words. The AI finds:

| File | What it holds |
| --- | --- |
| `CLAUDE.md` | Goals, structure, decisions, the build and check process. |
| `.claude/rules/` | Topic rules that load when matching files are edited. |
| `.claude/skills/aicore-fivem`, `aicore-ui`, `aicore-mysql` | FiveM engine, NUI and SQL knowledge. |
| `resources/[ai]/<script>/CLAUDE.md` | What each script does and why. |
| `docs/compat/` | Framework surfaces and notes on third-party scripts. |

<Callout type="warn">
Testing generated code is still recommended before you put it on a live server.
</Callout>

## Do I need AI? [#do-i-need-ai]

No. AI-assisted development is optional. AI Core works as a regular FiveM framework and needs no AI service to run.

## Read these docs with your AI [#read-these-docs-with-your-ai]

Every page here is also available as Markdown: add `.md` to its URL, or use the **Copy Markdown** button at the top of the page. The whole documentation is at [`/llms-full.txt`](/llms-full.txt).


# Compatibility (/ru/docs/compatibility)

Almost every FiveM script is written for ESX, QBCore or Qbox, so running them is a main goal. AI Core ships no third-party scripts and favours no vendor: you install your own.

## Three layers [#three-layers]

<Steps>
<Step>

### Framework bridge [#framework-bridge]

AI Core provides `es_extended`, `qb-core` and `qbx_core` and answers their exports, core objects and events, so scripts written for ESX, QBCore or Qbox see AI Core as their framework and run unchanged.

</Step>
<Step>

### Integrations [#integrations]

AI Core and the `ai-*` scripts need things other scripts provide: inventory, target, notify, phone, fuel, vehicle keys and more. Each category has one interface and each supported script is one adapter file. AI Core detects the installed script on start, and the admin panel can override the choice per category.

</Step>
<Step>

### Per-script notes [#per-script-notes]

Every tested third-party script gets a note: tested version, status and known limits.

</Step>
</Steps>

See the [compatible scripts](/scripts) list for what AI Core integrates with today.

## Adding a script [#adding-a-script]

Supporting a new script is one small, repeatable job: copy the category's adapter template, fill in its calls, add one line to the registry. You can ask your AI to do it.


# Introduction (/ru/docs)

**AI Core** is a free, open-source FiveM framework built from the ground up with **TypeScript**, designed to make server development easier, smarter and more accessible to everyone.

Inspired by ESX and QBCore, AI Core combines an AI-friendly architecture, cross-framework compatibility, automatic resource integration and in-game management tools. Whether you are an experienced developer or have never written a line of code, you can build your server your way.

## Why AI Core [#why-ai-core]

<Cards>
  <Card title="Built for AI development">
    Dedicated AI instructions, development guidelines and one consistent TypeScript architecture.
  </Card>
  <Card title="ESX & QBCore compatibility">
    Designed to run existing ESX and QBCore scripts, including paid third-party resources.
  </Card>
  <Card title="Automatic script integration">
    Detects supported installed scripts and adapts related systems.
  </Card>
  <Card title="Manage everything in-game">
    Framework settings live in an in-game admin panel, not in config files.
  </Card>
</Cards>

## Next steps [#next-steps]

<Cards>
  <Card title="Installation" href="/docs/installation" />
  <Card title="Working with AI" href="/docs/working-with-ai" />
  <Card title="Compatibility" href="/docs/compatibility" />
</Cards>


# Installation (/ru/docs/installation)

## Requirements [#requirements]

| Dependency | Version | Why |
| --- | --- | --- |
| FXServer (artifact) | 38039 or newer recommended | Newer builds let the server see player deaths itself. Older builds still run. |
| [Bun](https://bun.sh) | latest | Installs packages and builds the TypeScript resources. |
| MariaDB | latest | The database. |

## Setup [#setup]

<Steps>
<Step>

### Get the server data folder [#get-the-server-data-folder]

Clone [ai-core](https://github.com/aifivem/ai-core) into the folder you will use as your server data folder.

</Step>
<Step>

### Configure secrets [#configure-secrets]

Copy `env.example.cfg` to `env.cfg`, fill in your license key and the database connection, then create the database.

</Step>
<Step>

### Install and build [#install-and-build]

```bash
bun install
bun run build
```

</Step>
<Step>

### Start the server [#start-the-server]

Start FXServer (txAdmin) with this folder as the server data folder.

</Step>
</Steps>

## Layout [#layout]

| Path | What |
| --- | --- |
| `server.cfg`, `security.cfg`, `misc.cfg`, `permission.cfg` | Server config. Secrets go into `env.cfg`. |
| `resources/[ai]/` | AI Core resources, each `ai-*` folder its own git repo. |
| `resources/[standalone]/` | Third-party resources. |
| `packages/` | The `@aicore-fivem/*` npm packages. |
| `template/` | Template for new resources: `bun run new <name> "<description>"`. |


# Working with AI (/ru/docs/working-with-ai)

AI Core is built so that someone who cannot code can ask an AI to change a script or write a new one, and get a result that fits.

Open your server data folder in Claude Code (or another coding agent: it reads `AGENTS.md`) and ask in your own words. The AI finds:

| File | What it holds |
| --- | --- |
| `CLAUDE.md` | Goals, structure, decisions, the build and check process. |
| `.claude/rules/` | Topic rules that load when matching files are edited. |
| `.claude/skills/aicore-fivem`, `aicore-ui`, `aicore-mysql` | FiveM engine, NUI and SQL knowledge. |
| `resources/[ai]/<script>/CLAUDE.md` | What each script does and why. |
| `docs/compat/` | Framework surfaces and notes on third-party scripts. |

<Callout type="warn">
Testing generated code is still recommended before you put it on a live server.
</Callout>

## Do I need AI? [#do-i-need-ai]

No. AI-assisted development is optional. AI Core works as a regular FiveM framework and needs no AI service to run.

## Read these docs with your AI [#read-these-docs-with-your-ai]

Every page here is also available as Markdown: add `.md` to its URL, or use the **Copy Markdown** button at the top of the page. The whole documentation is at [`/llms-full.txt`](/llms-full.txt).