docs(environments): explain building RL environments with REA

2026-10-26 17:35:11 +00:00 · 2026-10-26 00:16:52 +08:00
1 parent 5d42839099
commit 447907f280
@@ -20,7 +20,7 @@

 **[Website](https://rea.tools/) · [Guides](https://rea.tools/guides/) · [Showcases](https://rea.tools/showcase/)**

-[Quick start](#quick-start) · [How REA works](#how-rea-works) · [What you can analyze](#what-you-can-analyze) · [Showcases](#showcases) · [FAQ](#faq) · [Documentation](#documentation)
+[Quick start](#quick-start) · [How REA works](#how-rea-works) · [What you can analyze](#what-you-can-analyze) · [Build RL environments](#build-rl-environments) · [Showcases](#showcases) · [FAQ](#faq) · [Documentation](#documentation)

 <code>npx rea-agents setup</code>

@@ -242,6 +242,26 @@ For provider selection, see the [CLI guide](docs/cli.md#choose-a-provider).
 Check [release availability](docs/installation.md#released-package-and-main)
 for features added since the latest npm release.

+## Build RL environments
+
+Give an AI agent a local environment to practice tasks such as finding an issue or creating a folder, without running the original app. Use it for reinforcement learning (RL) or to test how well an agent completes tasks.
+
+REA turns recorded API requests and responses into tools the agent can call. The environment uses the recorded data and supports changes only when the recording confirms their effects.
+
+Ask your agent to use REA to record a session on a test instance where it may create, edit, and delete data. You can also start with a HAR file, a recording of browser network requests and responses.
+
+Build with REA, then run with the separately installed AgentEnv framework and Docker:
+
+```sh
+rea environment-build ./session.har ./my-env --name my-env --json
+agent-env run ./my-env
+```
+
+REA exports a runnable environment with a basic test to check that it starts and responds. Use it with your RL framework to define task goals, add reward checks, and run training.
+
+[Build an environment](docs/agent-environments-quickstart.md) ·
+[Environment reference](docs/agent-environments.md)
+
 ## Showcases

 <a href="https://rea.tools/showcase/">
@@ -53,7 +53,11 @@ export default defineConfig({
            text: "Web network captures",
            link: "/web-network-captures",
          },
-          { text: "Agent environments", link: "/agent-environments" },
+          {
+            text: "Build RL environments",
+            link: "/agent-environments-quickstart",
+          },
+          { text: "Environment reference", link: "/agent-environments" },
          { text: "Electron observation", link: "/electron-observation" },
          { text: "Electron fuses", link: "/electron-fuses" },
          { text: "Process capture", link: "/process-capture" },
@@ -0,0 +1,204 @@
+# Build RL environments with REA
+
+REA turns a recorded web app session into a runnable environment for training
+and testing AI agents. An agent can practice tasks such as finding an issue,
+creating a folder, or editing a record without running the original app.
+
+REA builds the tools the agent calls, the local data those tools use, and a
+test that checks the environment starts and responds. It supports changes
+when the recording confirms their effects. You can then use the environment
+with your RL framework to set task goals, check rewards, and run training.
+
+## Before you start
+
+Install [REA and its agent integration](installation.md). To record an app,
+you also need a running test instance and a Chrome-family browser. Choose an
+instance where the agent is allowed to create, edit, and delete data. REA
+records the app you provide; you start it and prepare its test data.
+
+To run the exported environment, install the
+[AgentEnv framework](https://github.com/scaleapi/agentenv-framework#install)
+and start Docker. REA's [compatibility check](testing.md#exported-environment-bundles)
+uses AgentEnv version `0.9.1334` with Python 3.12.
+
+There are two ways to build an environment: ask your agent to record the app,
+or start from a recording you already have.
+
+## 1. Record and build with your agent
+
+Give your agent the app URL, the operations you need, your browser's executable
+path, and an output directory. For an app with folders, adapt this prompt:
+
+```text
+Use REA to build an AgentEnv environment from my test web app at
+http://127.0.0.1:3000. Cover listing, creating, renaming, and deleting folders.
+You may create and remove test folders. Leave the existing data unchanged.
+
+Sign in as admin using the password in APP_PASSWORD. Use the browser at
+/absolute/path/to/chromium. Save the environment to
+/absolute/path/to/my-env, which does not exist yet.
+
+Record the session, check which operations the environment supports, and
+export it. Report any unsupported operations and what is missing.
+```
+
+Replace the URL, account, paths, and folder operations with your own. Set
+`APP_PASSWORD` in the environment that starts REA's MCP server so REA can use
+it without putting the password in the prompt.
+
+Your agent inspects the app, records a session, checks the result, and exports
+a folder containing the runnable environment. It reports which operations
+work and which need more evidence. The app is used during recording; the
+exported environment runs from the saved data.
+
+After your agent exports the folder, skip to
+[run the environment](#3-run-the-environment). The next section is an
+alternative for an existing recording.
+
+## 2. Or build from a saved recording
+
+A HAR file records a browser's network requests and responses. Export one
+with API response bodies from your browser's network panel, or use a
+recording you already have. To include create, edit, and delete operations,
+record those actions and the reads that show their results.
+
+Build the environment into a new or empty directory:
+
+```sh
+rea environment-build ./session.har ./my-env --name my-env --json
+```
+
+You can also pass capture Evidence JSON saved by REA's
+`capture-browser-scenario` or `inspect-web-network-capture` commands. Here,
+Evidence means REA's saved recording with its source information. The build
+accepts HAR files and those JSON recordings. It reads local data and writes
+the environment folder without contacting the app.
+
+Add `--dry-run` to review the build report without writing the folder. For an
+unreleased REA checkout, use `--package-tarball` with its packed package so
+the exported environment runs the same implementation.
+
+The build report tells you what the environment supports:
+
+| Report field      | What to check                                                                                                            |
+| ----------------- | ------------------------------------------------------------------------------------------------------------------------ |
+| `state`           | Whether the environment can answer from local state or uses recorded-response replay.                                    |
+| `coverage.reads`  | Which read operations use state and which replay recorded answers.                                                       |
+| `coverage.writes` | Which create, edit, and delete operations are supported. Each withheld operation includes a reason and a recording hint. |
+| `warnings`        | Recorded content or local paths to review before sharing the folder.                                                     |
+
+A successful build means the folder was created. Check the report to confirm
+it supports the operations your tasks need. `coverage: null` means the build
+could not prepare state for this environment and it will use replay.
+
+## 3. Run the environment
+
+Whether your agent exported the folder or you built it from a HAR, run it
+with AgentEnv:
+
+```sh
+agent-env run ./my-env
+```
+
+Use the folder path your agent reported if it differs. The first run builds
+the container image, so it needs access to the image and package sources.
+
+REA includes a basic test, called the smoke task. It checks the expected tool
+count and, when a suitable read tool exists, calls it and checks its response
+status. Passing this test shows the environment starts and responds in the
+tested setup. It does not yet score an agent on an application task.
+
+The folder contains the recording, a tool manifest describing the available
+operations, a Dockerfile, environment configuration, and the test. The
+[export reference](agent-environments.md#export-a-bundle) describes each file.
+
+## 4. Add tasks and reward checks
+
+Start with one task the exported tools support. Give it a clear goal and a
+checkable result. For example, if folder creation is supported, ask your
+agent:
+
+```text
+Use this exported environment to add an AgentEnv task that asks an agent
+to create a folder named Practice. Check the saved environment state to
+confirm the folder exists with that name, and use that check to score the
+result. Reset the environment before each run so attempts start with the
+same data. Use the AgentEnv task and verifier formats.
+```
+
+This asks your agent to help build the task and its grading check around the
+environment REA generated. A retrieval task might check an answer against a
+recorded value. A task that changes data should check the resulting state.
+When state is available, the environment supports reset, load, and read-back
+operations for repeatable runs.
+
+Use the [AgentEnv documentation](https://www.agentenvframework.com/docs) for
+task configuration, agent connections, scoring, and execution. Connect the
+resulting tasks to your chosen RL training workflow.
+
+## Improve an operation that is missing
+
+For REA to support a change, the recording needs to show what happened before
+and after it. When recording against your test app:
+
+1. Read the list and an existing item before making changes. Repeat the
+   initial reads to show which values change independently.
+2. Create a test item, read it back, and read the list before the next change.
+   Repeat with a second item and different text.
+3. Edit each test item, then read the item and list again. Leave more than a
+   second between creation and the first edit to show time-dependent changes.
+4. Delete the test items, then read them back and read the list to confirm
+   their removal.
+
+Also record filters, searches, sorting, and paging if your tasks need them.
+The agent should check that every recording step completed before using it.
+The [recording workflow](https://github.com/morluto/rea/blob/main/.agents/skills/reverse-engineer-anything/references/environments.md)
+has the detailed browser instructions, including timeouts and handling IDs
+assigned by the app.
+
+Use the report's hints to decide what to record next:
+
+| Reason                          | Next step                                                                                |
+| ------------------------------- | ---------------------------------------------------------------------------------------- |
+| `unconfirmed`                   | Read the item and its list after the change.                                             |
+| `no-state-target`               | Record reads of the collection or item the operation changes.                            |
+| `no-observation`                | Read back a created item. For an edit or delete, also read it before changing it.        |
+| `contradicted` or `side-effect` | Inspect the reported disagreement. The operation may need behavior REA cannot model yet. |
+
+See the [full reason table](agent-environments.md#build-a-bundle-in-one-step)
+for the other cases. Rebuild from the new recording and check the report
+again. A new recording replaces the build input; combining separate recording
+sessions is not supported.
+
+## Compare with the original app
+
+For a stronger check, record a separate sequence of calls against the real
+app, starting from the same test data as the original recording. This is a
+probe. Restore that starting data before each probe sequence, then compare
+the saved probe recordings with the environment:
+
+```sh
+rea environment-compare ./my-env/envs/my-env/manifest.json \
+  --evidence ./my-env/envs/my-env/evidence.json \
+  --probe ./probe-create-edit-delete.json --probe ./probe-reads.json --json
+```
+
+Each probe file must be capture Evidence JSON from REA. The comparison runs
+offline and reports differences in responses, unsupported calls, and missing
+observations. It accounts for supported differences in IDs, times, and
+modeled generated values. Agreement applies to the calls those probes check.
+See the [comparison reference](agent-environments.md#measure-fidelity-against-the-application)
+for the exact rules.
+
+## Before sharing the environment
+
+The exported folder includes retained response bodies and local source paths.
+Standard authentication headers are excluded, but custom headers, query
+values, and body tokens can remain. Review the content you plan to share.
+Credential-name warnings point to values worth reviewing; they do not remove
+those values or establish that the recording contains no credentials.
+
+For direct MCP serving, replay behavior, state controls, and resource limits,
+see the [environment reference](agent-environments.md). The
+[implementation index](specs/agent-environments/README.md) links the contributing
+PRs and their verification records.
@@ -1,5 +1,12 @@
 # Agent environments from recorded captures

+For a first environment, start with the
+[quickstart](agent-environments-quickstart.md): record an app or use a saved
+session, build and run the environment, and add tasks and reward checks.
+The [implementation index](specs/agent-environments/README.md) links
+the contributing PRs and their verification records. This page is the detailed
+command and behavior reference.
+
 Use `rea environment-build` to turn one recorded capture into an agent
 environment bundle in one offline step: a folder `agent-env run` builds and
 runs, whose MCP server answers from what the capture observed. See
@@ -20,7 +20,7 @@

 **[الموقع](https://rea.tools/ar/) · [الأدلة](https://rea.tools/ar/guides/) · [دراسات الحالة](https://rea.tools/ar/showcase/)**

-[البدء السريع](#البدء-السريع) · [كيف يعمل REA](#كيف-يعمل-rea) · [ما الذي يمكنك تحليله](#ما-الذي-يمكنك-تحليله) · [دراسات الحالة](#دراسات-الحالة) · [الأسئلة الشائعة](#الأسئلة-الشائعة) · [أدوات GNU objdump وRizin](../reverse-engineering-tools.md) · [التوثيق](#التوثيق)
+[البدء السريع](#البدء-السريع) · [كيف يعمل REA](#كيف-يعمل-rea) · [ما الذي يمكنك تحليله](#ما-الذي-يمكنك-تحليله) · [إنشاء بيئات التعلم المعزز](#build-rl-environments) · [دراسات الحالة](#دراسات-الحالة) · [الأسئلة الشائعة](#الأسئلة-الشائعة) · [أدوات GNU objdump وRizin](../reverse-engineering-tools.md) · [التوثيق](#التوثيق)

 <code>npx rea-agents setup</code>

@@ -196,6 +196,28 @@ npx rea-agents@latest setup

 تختلف صيغ ملفات الشيفرة الأصلية والأنظمة المضيفة المدعومة باختلاف الموفّر. راجع [إعداد Hopper وGhidra](../installation.md#hopper)، و[دليل IDA](../ida-provider.md)، [Kuna](../kuna-provider.md)، و[دعم Ghidra التجريبي على Windows](../windows-ghidra-p0.md). يدعم Ghidra أيضًا [تحليل DOS ذي 16 بت](../ghidra-dos.md). لاختيار الموفّر، راجع [دليل CLI](../cli.md#choose-a-provider). تحقّق من [توفر الميزات في الإصدارات](../installation.md#released-package-and-main) للميزات المضافة بعد أحدث إصدار على npm.

+<a id="build-rl-environments"></a>
+
+## إنشاء بيئات التعلم المعزز
+
+أنشئ بيئة محلية يتدرب فيها وكيل الذكاء الاصطناعي على مهام مثل البحث عن مشكلة أو إنشاء مجلد، دون تشغيل التطبيق الأصلي. استخدمها للتعلم المعزز (RL) أو لاختبار قدرة الوكيل على إنجاز المهام.
+
+يحوّل REA طلبات API والردود المسجلة إلى أدوات يمكن للوكيل استدعاؤها. تستخدم البيئة البيانات المسجلة ولا تدعم التغييرات إلا عندما يؤكد التسجيل آثارها.
+
+اطلب من وكيلك استخدام REA لتسجيل جلسة على نسخة اختبار يُسمح له فيها بإنشاء البيانات وتعديلها وحذفها. يمكنك أيضًا البدء بملف HAR، وهو تسجيل لطلبات الشبكة وردودها في المتصفح.
+
+أنشئ البيئة باستخدام REA، ثم شغّلها باستخدام إطار AgentEnv وDocker المثبتين بشكل منفصل:
+
+```sh
+rea environment-build ./session.har ./my-env --name my-env --json
+agent-env run ./my-env
+```
+
+يصدّر REA بيئة قابلة للتشغيل مع اختبار أساسي يتحقق من بدء تشغيلها واستجابتها. استخدمها مع إطار التعلم المعزز لتحديد أهداف المهام وإضافة فحوص المكافآت وتشغيل التدريب.
+
+[دليل إنشاء بيئة](../agent-environments-quickstart.md) ·
+[مرجع البيئات](../agent-environments.md)
+
 ## دراسات الحالة

 <a href="https://rea.tools/ar/showcase/">
@@ -20,7 +20,7 @@

 **[Website](https://rea.tools/de/) · [Anleitungen](https://rea.tools/de/guides/) · [Fallstudien](https://rea.tools/de/showcase/)**

-[Schnellstart](#schnellstart) · [So funktioniert REA](#so-funktioniert-rea) · [Was du analysieren kannst](#was-du-analysieren-kannst) · [Fallstudien](#fallstudien) · [Häufige Fragen](#häufige-fragen) · [GNU-objdump- und Rizin-Tools](../reverse-engineering-tools.md) · [Dokumentation](#dokumentation)
+[Schnellstart](#schnellstart) · [So funktioniert REA](#so-funktioniert-rea) · [Was du analysieren kannst](#was-du-analysieren-kannst) · [RL-Umgebungen erstellen](#build-rl-environments) · [Fallstudien](#fallstudien) · [Häufige Fragen](#häufige-fragen) · [GNU-objdump- und Rizin-Tools](../reverse-engineering-tools.md) · [Dokumentation](#dokumentation)

 <code>npx rea-agents setup</code>

@@ -196,6 +196,28 @@ Bei großen Binärdateien kannst du die Startfrist mit `REA_GHIDRA_STARTUP_TIMEO

 Native Formate und unterstützte Hostsysteme unterscheiden sich je nach Provider. Siehe [Hopper- und Ghidra-Einrichtung](../installation.md#hopper), den [IDA-Leitfaden](../ida-provider.md), [Kuna](../kuna-provider.md) und die [experimentelle Ghidra-Unterstützung unter Windows](../windows-ghidra-p0.md). Ghidra unterstützt auch [16-Bit-DOS-Analyse](../ghidra-dos.md). Die Provider-Auswahl beschreibt der [CLI-Leitfaden](../cli.md#choose-a-provider). Prüfe die [Verfügbarkeit in Releases](../installation.md#released-package-and-main) für Funktionen, die seit der neuesten npm-Version hinzugekommen sind.

+<a id="build-rl-environments"></a>
+
+## RL-Umgebungen erstellen
+
+Erstelle eine lokale Umgebung, in der ein KI-Agent Aufgaben wie das Finden eines Issues oder das Anlegen eines Ordners üben kann, ohne die ursprüngliche App auszuführen. Nutze sie für Reinforcement Learning (RL) oder um zu testen, wie gut ein Agent Aufgaben erledigt.
+
+REA wandelt aufgezeichnete API-Anfragen und Antworten in Werkzeuge um, die der Agent aufrufen kann. Die Umgebung nutzt die aufgezeichneten Daten und unterstützt Änderungen nur, wenn die Aufzeichnung deren Wirkung bestätigt.
+
+Bitte deinen Agenten, mit REA eine Sitzung auf einer Testinstanz aufzuzeichnen, auf der er Daten anlegen, bearbeiten und löschen darf. Du kannst auch mit einer HAR-Datei beginnen, die Netzwerkanfragen und Antworten des Browsers aufzeichnet.
+
+Erstelle die Umgebung mit REA und starte sie mit dem separat installierten AgentEnv-Framework und Docker:
+
+```sh
+rea environment-build ./session.har ./my-env --name my-env --json
+agent-env run ./my-env
+```
+
+REA exportiert eine lauffähige Umgebung mit einem einfachen Test, der prüft, ob sie startet und antwortet. Nutze sie mit deinem RL-Framework, um Aufgabenziele und Belohnungsprüfungen festzulegen und das Training auszuführen.
+
+[Anleitung zum Erstellen einer Umgebung](../agent-environments-quickstart.md) ·
+[Umgebungsreferenz](../agent-environments.md)
+
 ## Fallstudien

 <a href="https://rea.tools/de/showcase/">
@@ -19,7 +19,7 @@

 **[Ιστότοπος](https://rea.tools/) · [Οδηγοί](https://rea.tools/guides/) · [Μελέτες περίπτωσης](https://rea.tools/showcase/)**

-[Γρήγορη εκκίνηση](#γρήγορη-εκκίνηση) · [Πώς λειτουργεί το REA](#πώς-λειτουργεί-το-rea) · [Τι μπορείς να αναλύσεις](#τι-μπορείς-να-αναλύσεις) · [Μελέτες περίπτωσης](#μελέτες-περίπτωσης) · [Συχνές ερωτήσεις](#συχνές-ερωτήσεις) · [Τεκμηρίωση](#τεκμηρίωση)
+[Γρήγορη εκκίνηση](#γρήγορη-εκκίνηση) · [Πώς λειτουργεί το REA](#πώς-λειτουργεί-το-rea) · [Τι μπορείς να αναλύσεις](#τι-μπορείς-να-αναλύσεις) · [Δημιουργία περιβαλλόντων RL](#build-rl-environments) · [Μελέτες περίπτωσης](#μελέτες-περίπτωσης) · [Συχνές ερωτήσεις](#συχνές-ερωτήσεις) · [Τεκμηρίωση](#τεκμηρίωση)

 <code>npx rea-agents setup</code>

@@ -200,6 +200,28 @@ npx rea-agents@latest setup

 Οι μορφές κώδικα μηχανής και τα υποστηριζόμενα συστήματα διαφέρουν ανά πάροχο ανάλυσης. Δες τη [ρύθμιση Hopper και Ghidra](../installation.md#hopper), τον [οδηγό IDA](../ida-provider.md) (που περιλαμβάνει προαιρετική γέφυρα MCP για κώδικα μηχανής), [Kuna](../kuna-provider.md) και την [πειραματική υποστήριξη Ghidra στα Windows](../windows-ghidra-p0.md). Το Ghidra υποστηρίζει επίσης [ανάλυση DOS 16 bit](../ghidra-dos.md). Για μεγάλα δυαδικά αρχεία, αύξησε το χρονικό όριο εκκίνησης του παρόχου με `REA_GHIDRA_STARTUP_TIMEOUT_MS` ή `REA_HOPPER_STARTUP_TIMEOUT_MS`. Για την επιλογή παρόχου, δες τον [οδηγό CLI](../cli.md#choose-a-provider). Έλεγξε τη [διαθεσιμότητα ανά έκδοση](../installation.md#released-package-and-main) για λειτουργίες που προστέθηκαν μετά την τελευταία έκδοση στο npm.

+<a id="build-rl-environments"></a>
+
+## Δημιουργία περιβαλλόντων RL
+
+Δημιουργήστε ένα τοπικό περιβάλλον όπου ένας πράκτορας AI εξασκείται σε εργασίες όπως η εύρεση ενός issue ή η δημιουργία φακέλου, χωρίς να εκτελείται η αρχική εφαρμογή. Χρησιμοποιήστε το για ενισχυτική μάθηση (RL) ή για να ελέγξετε πόσο καλά ολοκληρώνει εργασίες ο πράκτορας.
+
+Το REA μετατρέπει καταγεγραμμένα αιτήματα και απαντήσεις API σε εργαλεία που μπορεί να καλεί ο πράκτορας. Το περιβάλλον χρησιμοποιεί τα καταγεγραμμένα δεδομένα και υποστηρίζει αλλαγές μόνο όταν η καταγραφή επιβεβαιώνει τα αποτελέσματά τους.
+
+Ζητήστε από τον πράκτορα να χρησιμοποιήσει το REA για να καταγράψει μια συνεδρία σε δοκιμαστική εγκατάσταση όπου επιτρέπεται να δημιουργεί, να επεξεργάζεται και να διαγράφει δεδομένα. Μπορείτε επίσης να ξεκινήσετε από αρχείο HAR, που καταγράφει τα αιτήματα και τις απαντήσεις δικτύου του προγράμματος περιήγησης.
+
+Δημιουργήστε με το REA και εκτελέστε με το πλαίσιο AgentEnv και το Docker, εγκατεστημένα ξεχωριστά:
+
+```sh
+rea environment-build ./session.har ./my-env --name my-env --json
+agent-env run ./my-env
+```
+
+Το REA εξάγει ένα εκτελέσιμο περιβάλλον με μια βασική δοκιμή εκκίνησης και απόκρισης. Συνδέστε το στο πλαίσιο RL για να ορίσετε στόχους, να προσθέσετε ελέγχους ανταμοιβής και να εκτελέσετε εκπαίδευση.
+
+[Οδηγός δημιουργίας περιβάλλοντος](../agent-environments-quickstart.md) ·
+[Αναφορά περιβαλλόντων](../agent-environments.md)
+
 ## Μελέτες περίπτωσης

 <a href="https://rea.tools/showcase/">
@@ -20,7 +20,7 @@

 **[Sitio web](https://rea.tools/es/) · [Guías](https://rea.tools/es/guides/) · [Casos prácticos](https://rea.tools/es/showcase/)**

-[Inicio rápido](#inicio-rápido) · [Cómo funciona REA](#cómo-funciona-rea) · [Qué puedes analizar](#qué-puedes-analizar) · [Casos prácticos](#casos-prácticos) · [Preguntas frecuentes](#preguntas-frecuentes) · [Herramientas GNU objdump y Rizin](../reverse-engineering-tools.md) · [Documentación](#documentación)
+[Inicio rápido](#inicio-rápido) · [Cómo funciona REA](#cómo-funciona-rea) · [Qué puedes analizar](#qué-puedes-analizar) · [Crear entornos de RL](#build-rl-environments) · [Casos prácticos](#casos-prácticos) · [Preguntas frecuentes](#preguntas-frecuentes) · [Herramientas GNU objdump y Rizin](../reverse-engineering-tools.md) · [Documentación](#documentación)

 <code>npx rea-agents setup</code>

@@ -196,6 +196,28 @@ Para binarios grandes, aumenta el plazo de inicio mediante `REA_GHIDRA_STARTUP_T

 Los formatos nativos y los sistemas anfitriones compatibles varían según el proveedor. Consulta [configuración de Hopper y Ghidra](../installation.md#hopper), la [guía de IDA](../ida-provider.md), [Kuna](../kuna-provider.md) y la [compatibilidad experimental de Ghidra en Windows](../windows-ghidra-p0.md). Ghidra también admite [análisis de DOS de 16 bits](../ghidra-dos.md). Para elegir un proveedor, consulta la [guía de CLI](../cli.md#choose-a-provider). Comprueba la [disponibilidad por versión](../installation.md#released-package-and-main) de las funciones añadidas después de la última versión publicada en npm.

+<a id="build-rl-environments"></a>
+
+## Crear entornos de RL
+
+Crea un entorno local donde un agente de IA pueda practicar tareas como buscar un issue o crear una carpeta, sin ejecutar la aplicación original. Úsalo para aprendizaje por refuerzo (RL) o para comprobar cómo completa las tareas un agente.
+
+REA convierte las solicitudes y respuestas de API grabadas en herramientas que el agente puede llamar. El entorno usa los datos grabados y solo admite cambios cuyos efectos confirma la grabación.
+
+Pide a tu agente que use REA para grabar una sesión en una instancia de prueba donde pueda crear, editar y borrar datos. También puedes empezar con un archivo HAR, que registra las solicitudes y respuestas de red del navegador.
+
+Construye con REA y ejecuta con el framework AgentEnv y Docker instalados por separado:
+
+```sh
+rea environment-build ./session.har ./my-env --name my-env --json
+agent-env run ./my-env
+```
+
+REA exporta un entorno ejecutable con una prueba básica que comprueba que arranca y responde. Úsalo con tu framework de RL para definir objetivos, añadir comprobaciones de recompensa y ejecutar el entrenamiento.
+
+[Guía para crear un entorno](../agent-environments-quickstart.md) ·
+[Referencia de entornos](../agent-environments.md)
+
 ## Casos prácticos

 <a href="https://rea.tools/es/showcase/">
@@ -20,7 +20,7 @@

 **[وب‌سایت](https://rea.tools/fa/) · [راهنماها](https://rea.tools/fa/guides/) · [نمونه‌های عملی](https://rea.tools/fa/showcase/)**

-[شروع سریع](#شروع-سریع) · [REA چگونه کار می‌کند؟](#rea-چگونه-کار-می‌کند) · [چه چیزهایی را میتوان تحلیل کرد؟](#چه-چیزهایی-را-می‌توان-تحلیل-کرد) · [نمونه‌های عملی](#نمونه‌های-عملی) · [پرسش‌های متداول](#پرسش‌های-متداول) · [ابزارهای GNU objdump و Rizin](../reverse-engineering-tools.md) · [مستندات](#مستندات)
+[شروع سریع](#شروع-سریع) · [REA چگونه کار می‌کند؟](#rea-چگونه-کار-می‌کند) · [چه چیزهایی را میتوان تحلیل کرد؟](#چه-چیزهایی-را-می‌توان-تحلیل-کرد) · [ساخت محیط‌های RL](#build-rl-environments) · [نمونه‌های عملی](#نمونه‌های-عملی) · [پرسش‌های متداول](#پرسش‌های-متداول) · [ابزارهای GNU objdump و Rizin](../reverse-engineering-tools.md) · [مستندات](#مستندات)

 <code>npx rea-agents setup</code>

@@ -188,6 +188,28 @@ REA به Node.js 22.x (>=22.23.4)، 24.x (>=24.22.1) یا 26+ (>=26.12.1)، به

 فرمت‌های بومی و پشتیبانی سیستم میزبان بر اساس ارائه‌دهنده متفاوت‌اند. [راه‌اندازی Hopper و Ghidra](../installation.md#hopper)، [راهنمای IDA](../ida-provider.md)، [Kuna](../kuna-provider.md) و [پشتیبانی آزمایشی Ghidra در ویندوز](../windows-ghidra-p0.md) را ببینید. Ghidra همچنین از [تحلیل DOS شانزده‌بیتی](../ghidra-dos.md) پشتیبانی می‌کند. برای انتخاب ارائه‌دهنده، به [راهنمای CLI](../cli.md#choose-a-provider) مراجعه کنید. برای قابلیت‌هایی که پس از آخرین انتشار npm اضافه شده‌اند، [وضعیت انتشار](../installation.md#released-package-and-main) را بررسی کنید.

+<a id="build-rl-environments"></a>
+
+## ساخت محیط‌های RL
+
+محیطی محلی بسازید تا عامل هوش مصنوعی بدون اجرای برنامهٔ اصلی، کارهایی مثل پیدا کردن یک مسئله یا ساخت پوشه را تمرین کند. از آن برای یادگیری تقویتی (RL) یا سنجش توانایی عامل در انجام کارها استفاده کنید.
+
+REA درخواست‌ها و پاسخ‌های ضبط‌شدهٔ API را به ابزارهایی تبدیل می‌کند که عامل می‌تواند فراخوانی کند. محیط از داده‌های ضبط‌شده استفاده می‌کند و فقط تغییراتی را پشتیبانی می‌کند که اثرشان در ضبط تأیید شده باشد.
+
+از عامل بخواهید با REA یک نشست را روی نمونهٔ آزمایشی ضبط کند که در آن اجازهٔ ایجاد، ویرایش و حذف داده دارد. می‌توانید از یک فایل HAR هم شروع کنید که درخواست‌ها و پاسخ‌های شبکهٔ مرورگر را ثبت می‌کند.
+
+محیط را با REA بسازید و سپس با چارچوب AgentEnv و Docker که جداگانه نصب شده‌اند اجرا کنید:
+
+```sh
+rea environment-build ./session.har ./my-env --name my-env --json
+agent-env run ./my-env
+```
+
+REA محیطی آمادهٔ اجرا همراه با یک آزمون ساده برای بررسی شروع به کار و پاسخ‌گویی آن صادر می‌کند. آن را به چارچوب RL متصل کنید تا اهداف کارها و بررسی پاداش را تعریف و آموزش را اجرا کنید.
+
+[راهنمای ساخت محیط](../agent-environments-quickstart.md) ·
+[مرجع محیط‌ها](../agent-environments.md)
+
 ## نمونه‌های عملی

 <a href="https://rea.tools/fa/showcase/">
@@ -20,7 +20,7 @@

 **[Site web](https://rea.tools/fr/) · [Guides](https://rea.tools/fr/guides/) · [Études de cas](https://rea.tools/fr/showcase/)**

-[Démarrage rapide](#démarrage-rapide) · [Comment fonctionne REA](#comment-fonctionne-rea) · [Ce que vous pouvez analyser](#ce-que-vous-pouvez-analyser) · [Études de cas](#études-de-cas) · [Questions fréquentes](#questions-fréquentes) · [Outils GNU objdump et Rizin](../reverse-engineering-tools.md) · [Documentation](#documentation)
+[Démarrage rapide](#démarrage-rapide) · [Comment fonctionne REA](#comment-fonctionne-rea) · [Ce que vous pouvez analyser](#ce-que-vous-pouvez-analyser) · [Créer des environnements RL](#build-rl-environments) · [Études de cas](#études-de-cas) · [Questions fréquentes](#questions-fréquentes) · [Outils GNU objdump et Rizin](../reverse-engineering-tools.md) · [Documentation](#documentation)

 <code>npx rea-agents setup</code>

@@ -193,6 +193,28 @@ L'inspection statique JavaScript et .NET lit les fichiers fournis sans exécuter

 Les formats natifs et les hôtes pris en charge varient selon le fournisseur. Consultez [la configuration de Hopper et Ghidra](../installation.md#hopper), le [guide IDA](../ida-provider.md), [Kuna](../kuna-provider.md) et [la prise en charge expérimentale de Ghidra sous Windows](../windows-ghidra-p0.md). Ghidra prend aussi en charge [l'analyse DOS 16 bits](../ghidra-dos.md). Pour les gros binaires, augmentez son délai de démarrage avec `REA_GHIDRA_STARTUP_TIMEOUT_MS` / `REA_HOPPER_STARTUP_TIMEOUT_MS`. Pour le choix du fournisseur, consultez le [guide CLI](../cli.md#choose-a-provider). Vérifiez la [disponibilité dans les versions publiées](../installation.md#released-package-and-main) pour les fonctionnalités ajoutées depuis la dernière version npm.

+<a id="build-rl-environments"></a>
+
+## Créer des environnements RL
+
+Créez un environnement local où un agent IA peut s’exercer à des tâches comme trouver un ticket ou créer un dossier, sans exécuter l’application d’origine. Utilisez-le pour l’apprentissage par renforcement (RL) ou pour tester la capacité d’un agent à accomplir des tâches.
+
+REA transforme les requêtes et réponses API enregistrées en outils que l’agent peut appeler. L’environnement utilise les données enregistrées et ne prend en charge des modifications que si l’enregistrement confirme leurs effets.
+
+Demandez à votre agent d’utiliser REA pour enregistrer une session sur une instance de test où il peut créer, modifier et supprimer des données. Vous pouvez aussi partir d’un fichier HAR, qui enregistre les requêtes et réponses réseau du navigateur.
+
+Construisez avec REA, puis exécutez avec le framework AgentEnv et Docker, installés séparément :
+
+```sh
+rea environment-build ./session.har ./my-env --name my-env --json
+agent-env run ./my-env
+```
+
+REA exporte un environnement exécutable avec un test de base qui vérifie qu’il démarre et répond. Utilisez-le avec votre framework RL pour définir les objectifs, ajouter les vérifications de récompense et lancer l’entraînement.
+
+[Guide de création d’un environnement](../agent-environments-quickstart.md) ·
+[Référence des environnements](../agent-environments.md)
+
 ## Études de cas

 <a href="https://rea.tools/fr/showcase/">
@@ -20,7 +20,7 @@

 **[Situs Web](https://rea.tools/id/) · [Panduan](https://rea.tools/id/guides/) · [Contoh Penggunaan](https://rea.tools/id/showcase/)**

-[Mulai Cepat](#mulai-cepat) · [Cara Kerja REA](#cara-kerja-rea) · [Hal yang Dapat Anda Analisis](#hal-yang-dapat-anda-analisis) · [Contoh Penggunaan](#contoh-penggunaan) · [FAQ](#faq) · [Alat GNU objdump dan Rizin](../reverse-engineering-tools.md) · [Dokumentasi](#dokumentasi)
+[Mulai Cepat](#mulai-cepat) · [Cara Kerja REA](#cara-kerja-rea) · [Hal yang Dapat Anda Analisis](#hal-yang-dapat-anda-analisis) · [Membangun lingkungan RL](#build-rl-environments) · [Contoh Penggunaan](#contoh-penggunaan) · [FAQ](#faq) · [Alat GNU objdump dan Rizin](../reverse-engineering-tools.md) · [Dokumentasi](#dokumentasi)

 <code>npx rea-agents setup</code>

@@ -204,6 +204,28 @@ Untuk memilih penyedia, lihat [panduan CLI](../cli.md#choose-a-provider).

 Periksa [ketersediaan rilis](../installation.md#released-package-and-main) untuk mengetahui fitur yang ditambahkan setelah rilis npm terbaru.

+<a id="build-rl-environments"></a>
+
+## Membangun lingkungan RL
+
+Buat lingkungan lokal agar agen AI dapat berlatih tugas seperti mencari issue atau membuat folder tanpa menjalankan aplikasi aslinya. Gunakan untuk pembelajaran penguatan (RL) atau menguji kemampuan agen menyelesaikan tugas.
+
+REA mengubah permintaan dan respons API yang direkam menjadi alat yang dapat dipanggil agen. Lingkungan memakai data rekaman dan hanya mendukung perubahan yang dampaknya dikonfirmasi oleh rekaman.
+
+Minta agen menggunakan REA untuk merekam sesi pada instans uji yang mengizinkannya membuat, mengedit, dan menghapus data. Anda juga dapat mulai dari file HAR, rekaman permintaan dan respons jaringan browser.
+
+Bangun dengan REA, lalu jalankan dengan framework AgentEnv dan Docker yang diinstal terpisah:
+
+```sh
+rea environment-build ./session.har ./my-env --name my-env --json
+agent-env run ./my-env
+```
+
+REA mengekspor lingkungan yang dapat dijalankan dengan uji dasar untuk memeriksa bahwa lingkungan mulai dan merespons. Hubungkan ke framework RL untuk menetapkan tujuan tugas, menambahkan pemeriksaan reward, dan menjalankan pelatihan.
+
+[Panduan membangun lingkungan](../agent-environments-quickstart.md) ·
+[Referensi lingkungan](../agent-environments.md)
+
 ## Contoh Penggunaan

 <a href="https://rea.tools/id/showcase/">
@@ -20,7 +20,7 @@

 **[Sito web](https://rea.tools/it/) · [Guide](https://rea.tools/it/guides/) · [Showcase](https://rea.tools/it/showcase/)**

-[Avvio rapido](#avvio-rapido) · [Come funziona REA](#come-funziona-rea) · [Cosa puoi analizzare](#cosa-puoi-analizzare) · [Showcase](#showcase) · [FAQ](#faq) · [Strumenti GNU objdump e Rizin](../reverse-engineering-tools.md) · [Documentazione](#documentazione)
+[Avvio rapido](#avvio-rapido) · [Come funziona REA](#come-funziona-rea) · [Cosa puoi analizzare](#cosa-puoi-analizzare) · [Creare ambienti RL](#build-rl-environments) · [Showcase](#showcase) · [FAQ](#faq) · [Strumenti GNU objdump e Rizin](../reverse-engineering-tools.md) · [Documentazione](#documentazione)

 <code>npx rea-agents setup</code>

@@ -193,6 +193,28 @@ L'ispezione statica di JavaScript e .NET legge i file forniti senza eseguire l'a

 I formati nativi e il supporto host variano in base al provider. Vedi la [configurazione di Hopper e Ghidra](../installation.md#hopper), la [guida IDA](../ida-provider.md), [Kuna](../kuna-provider.md) e il [supporto sperimentale Windows Ghidra](../windows-ghidra-p0.md). Ghidra supporta anche l'[analisi DOS a 16 bit](../ghidra-dos.md). Per binari di grandi dimensioni, aumenta il timeout di avvio con `REA_GHIDRA_STARTUP_TIMEOUT_MS` / `REA_HOPPER_STARTUP_TIMEOUT_MS`. Per la selezione del provider, vedi la [guida CLI](../cli.md#choose-a-provider). Controlla la [disponibilità delle release](../installation.md#released-package-and-main) per le funzionalità aggiunte dall'ultima release npm.

+<a id="build-rl-environments"></a>
+
+## Creare ambienti RL
+
+Crea un ambiente locale in cui un agente IA possa esercitarsi in attività come cercare una issue o creare una cartella, senza eseguire l’app originale. Usalo per l’apprendimento per rinforzo (RL) o per verificare come l’agente completa le attività.
+
+REA trasforma le richieste e le risposte API registrate in strumenti che l’agente può chiamare. L’ambiente usa i dati registrati e supporta modifiche solo quando la registrazione ne conferma gli effetti.
+
+Chiedi all’agente di usare REA per registrare una sessione su un’istanza di prova in cui possa creare, modificare ed eliminare dati. Puoi anche partire da un file HAR, che registra le richieste e le risposte di rete del browser.
+
+Crea con REA, poi esegui con il framework AgentEnv e Docker, installati separatamente:
+
+```sh
+rea environment-build ./session.har ./my-env --name my-env --json
+agent-env run ./my-env
+```
+
+REA esporta un ambiente eseguibile con un test di base che ne verifica l’avvio e le risposte. Usalo con il tuo framework RL per definire gli obiettivi, aggiungere controlli sulle ricompense ed eseguire l’addestramento.
+
+[Guida alla creazione di un ambiente](../agent-environments-quickstart.md) ·
+[Riferimento degli ambienti](../agent-environments.md)
+
 ## Showcase

 <a href="https://rea.tools/it/showcase/">
@@ -20,7 +20,7 @@

 **[ウェブサイト](https://rea.tools/ja/) · [ガイド](https://rea.tools/ja/guides/) · [事例](https://rea.tools/ja/showcase/)**

-[クイックスタート](#クイックスタート) · [REA の仕組み](#rea-の仕組み) · [分析できる対象](#分析できる対象) · [事例](#事例) · [よくある質問](#よくある質問) · [GNU objdump・Rizin ツール](../reverse-engineering-tools.md) · [ドキュメント](#ドキュメント)
+[クイックスタート](#クイックスタート) · [REA の仕組み](#rea-の仕組み) · [分析できる対象](#分析できる対象) · [RL 環境を構築する](#build-rl-environments) · [事例](#事例) · [よくある質問](#よくある質問) · [GNU objdump・Rizin ツール](../reverse-engineering-tools.md) · [ドキュメント](#ドキュメント)

 <code>npx rea-agents setup</code>

@@ -196,6 +196,28 @@ REA には Node.js 22.x（>=22.23.4）、24.x（>=24.22.1）、または 26+ (>=

 対応するネイティブ形式とホストは、プロバイダーによって異なります。[Hopper と Ghidra のセットアップ](../installation.md#hopper)、[IDA ガイド](../ida-provider.md)、[Kuna](../kuna-provider.md)、[Windows 向け Ghidra の実験的対応](../windows-ghidra-p0.md)を参照してください。Ghidra は [16 ビット DOS 分析](../ghidra-dos.md)にも対応しています。プロバイダーの選択は [CLI ガイド](../cli.md#choose-a-provider)を参照してください。最新の npm リリース以降に追加された機能については、[リリースでの利用可否](../installation.md#released-package-and-main)を確認してください。

+<a id="build-rl-environments"></a>
+
+## RL 環境を構築する
+
+元のアプリを動かさずに、AI エージェントが issue の検索やフォルダーの作成などを練習できるローカル環境を構築します。強化学習（RL）や、エージェントのタスク遂行能力のテストに使えます。
+
+REA は記録した API のリクエストと応答を、エージェントが呼び出せるツールに変換します。環境は記録したデータを使い、記録で効果が確認された変更だけをサポートします。
+
+データの作成、編集、削除を許可したテスト環境で、REA を使ってセッションを記録するようエージェントに依頼してください。ブラウザーのネットワークリクエストと応答を記録した HAR ファイルから始めることもできます。
+
+REA で構築し、別途インストールした AgentEnv フレームワークと Docker で実行します。
+
+```sh
+rea environment-build ./session.har ./my-env --name my-env --json
+agent-env run ./my-env
+```
+
+REA は実行可能な環境と、起動して応答することを確認する基本テストをエクスポートします。RL フレームワークに接続して、タスクの目標や報酬のチェックを定義し、学習を実行できます。
+
+[環境構築ガイド](../agent-environments-quickstart.md) ·
+[環境リファレンス](../agent-environments.md)
+
 ## 事例

 <a href="https://rea.tools/ja/showcase/">
@@ -20,7 +20,7 @@

 **[웹사이트](https://rea.tools/ko/) · [가이드](https://rea.tools/ko/guides/) · [사례](https://rea.tools/ko/showcase/)**

-[빠른 시작](#빠른-시작) · [REA의 작동 방식](#rea의-작동-방식) · [분석할 수 있는 대상](#분석할-수-있는-대상) · [사례](#사례) · [자주 묻는 질문](#자주-묻는-질문) · [문서](#문서)
+[빠른 시작](#빠른-시작) · [REA의 작동 방식](#rea의-작동-방식) · [분석할 수 있는 대상](#분석할-수-있는-대상) · [RL 환경 만들기](#build-rl-environments) · [사례](#사례) · [자주 묻는 질문](#자주-묻는-질문) · [문서](#문서)

 <code>npx rea-agents setup</code>

@@ -196,6 +196,28 @@ REA에는 Node.js 22.x(>=22.23.4), 24.x(>=24.22.1) 또는 26+ (>=26.12.1)와 npm

 지원하는 네이티브 형식과 호스트는 제공자마다 다릅니다. [Hopper 및 Ghidra 설정](../installation.md#hopper), [IDA 가이드](../ida-provider.md)(선택 사항인 네이티브 MCP 브리지 포함), [Kuna](../kuna-provider.md), [실험적 Windows Ghidra 지원](../windows-ghidra-p0.md)을 참고하세요. Ghidra는 [16비트 DOS 분석](../ghidra-dos.md)도 지원합니다. 큰 바이너리를 분석할 때는 `REA_GHIDRA_STARTUP_TIMEOUT_MS` 또는 `REA_HOPPER_STARTUP_TIMEOUT_MS`로 제공자의 시작 제한 시간을 늘리세요. 제공자 선택은 [CLI 가이드](../cli.md#choose-a-provider)를 참고하세요. 최신 npm 릴리스 이후 추가된 기능은 [릴리스에서의 사용 가능 여부](../installation.md#released-package-and-main)를 확인하세요.

+<a id="build-rl-environments"></a>
+
+## RL 환경 만들기
+
+원래 앱을 실행하지 않고도 AI 에이전트가 이슈 찾기나 폴더 만들기 같은 작업을 연습할 수 있는 로컬 환경을 만듭니다. 강화 학습(RL)이나 에이전트의 작업 수행 능력 평가에 사용할 수 있습니다.
+
+REA는 기록한 API 요청과 응답을 에이전트가 호출할 수 있는 도구로 바꿉니다. 환경은 기록된 데이터를 사용하며, 기록에서 효과가 확인된 변경만 지원합니다.
+
+데이터 생성, 편집, 삭제를 허용한 테스트 인스턴스에서 REA로 세션을 기록하도록 에이전트에게 요청하세요. 브라우저의 네트워크 요청과 응답을 기록한 HAR 파일로 시작할 수도 있습니다.
+
+REA로 빌드한 뒤 별도로 설치한 AgentEnv 프레임워크와 Docker로 실행하세요.
+
+```sh
+rea environment-build ./session.har ./my-env --name my-env --json
+agent-env run ./my-env
+```
+
+REA는 실행 가능한 환경과 시작 및 응답 여부를 확인하는 기본 테스트를 내보냅니다. RL 프레임워크에 연결해 작업 목표와 보상 검사를 정의하고 학습을 실행할 수 있습니다.
+
+[환경 만들기 가이드](../agent-environments-quickstart.md) ·
+[환경 참조 문서](../agent-environments.md)
+
 ## 사례

 <a href="https://rea.tools/ko/showcase/">
@@ -20,7 +20,7 @@

 **[വെബ്സൈറ്റ്](https://rea.tools/) · [ഗൈഡുകൾ](https://rea.tools/guides/) · [ഉദാഹരണങ്ങൾ](https://rea.tools/showcase/)**

-[ദ്രുതാരംഭം](#ദ്രുതാരംഭം) · [REA എങ്ങനെ പ്രവർത്തിക്കുന്നു](#rea-എങ്ങനെ-പ്രവർത്തിക്കുന്നു) · [എന്തൊക്കെ വിശകലനം ചെയ്യാം](#എന്തൊക്കെ-വിശകലനം-ചെയ്യാം) · [ഉദാഹരണങ്ങൾ](#ഉദാഹരണങ്ങൾ) · [പതിവുചോദ്യങ്ങൾ](#പതിവുചോദ്യങ്ങൾ) · [ഡോക്യുമെന്റേഷൻ](#ഡോക്യുമെന്റേഷൻ)
+[ദ്രുതാരംഭം](#ദ്രുതാരംഭം) · [REA എങ്ങനെ പ്രവർത്തിക്കുന്നു](#rea-എങ്ങനെ-പ്രവർത്തിക്കുന്നു) · [എന്തൊക്കെ വിശകലനം ചെയ്യാം](#എന്തൊക്കെ-വിശകലനം-ചെയ്യാം) · [RL പരിതസ്ഥിതികൾ നിർമ്മിക്കുക](#build-rl-environments) · [ഉദാഹരണങ്ങൾ](#ഉദാഹരണങ്ങൾ) · [പതിവുചോദ്യങ്ങൾ](#പതിവുചോദ്യങ്ങൾ) · [ഡോക്യുമെന്റേഷൻ](#ഡോക്യുമെന്റേഷൻ)

 <code>npx rea-agents setup</code>

@@ -200,6 +200,28 @@ Ghidra, [16-bit DOS analysis](../ghidra-dos.md)-ഉം പിന്തുണയ
 Provider തിരഞ്ഞെടുക്കാൻ [CLI guide](../cli.md#choose-a-provider) കാണുക.
 ഏറ്റവും പുതിയ npm release-നുശേഷം ചേർത്ത features അറിയാൻ [release availability](../installation.md#released-package-and-main) പരിശോധിക്കുക.

+<a id="build-rl-environments"></a>
+
+## RL പരിതസ്ഥിതികൾ നിർമ്മിക്കുക
+
+യഥാർഥ ആപ്പ് പ്രവർത്തിപ്പിക്കാതെ issue കണ്ടെത്തൽ, ഫോൾഡർ സൃഷ്ടിക്കൽ തുടങ്ങിയ ജോലികൾ AI ഏജന്റിന് പരിശീലിക്കാൻ ഒരു പ്രാദേശിക പരിതസ്ഥിതി നിർമ്മിക്കുക. റീഇൻഫോഴ്‌സ്‌മെന്റ് ലേണിംഗിനോ (RL) ഏജന്റ് ജോലികൾ എത്ര നന്നായി പൂർത്തിയാക്കുന്നു എന്ന് പരിശോധിക്കാനോ ഇത് ഉപയോഗിക്കാം.
+
+REA റെക്കോർഡ് ചെയ്ത API അഭ്യർത്ഥനകളും പ്രതികരണങ്ങളും ഏജന്റിന് വിളിക്കാവുന്ന ടൂളുകളാക്കുന്നു. പരിതസ്ഥിതി റെക്കോർഡ് ചെയ്ത ഡാറ്റ ഉപയോഗിക്കുന്നു. റെക്കോർഡ് ഫലം സ്ഥിരീകരിക്കുന്ന മാറ്റങ്ങൾ മാത്രമാണ് പിന്തുണയ്ക്കുന്നത്.
+
+ഡാറ്റ സൃഷ്ടിക്കാനും തിരുത്താനും ഇല്ലാതാക്കാനും അനുമതിയുള്ള ഒരു പരീക്ഷണ ഇൻസ്റ്റൻസിൽ REA ഉപയോഗിച്ച് സെഷൻ റെക്കോർഡ് ചെയ്യാൻ ഏജന്റിനോട് ആവശ്യപ്പെടുക. ബ്രൗസറിന്റെ നെറ്റ്‌വർക്ക് അഭ്യർത്ഥനകളും പ്രതികരണങ്ങളും റെക്കോർഡ് ചെയ്യുന്ന HAR ഫയലിൽ നിന്നും തുടങ്ങാം.
+
+REA ഉപയോഗിച്ച് നിർമ്മിച്ച ശേഷം പ്രത്യേകം ഇൻസ്റ്റാൾ ചെയ്ത AgentEnv ഫ്രെയിംവർക്കും Docker-ഉം ഉപയോഗിച്ച് പ്രവർത്തിപ്പിക്കുക:
+
+```sh
+rea environment-build ./session.har ./my-env --name my-env --json
+agent-env run ./my-env
+```
+
+പ്രവർത്തനം തുടങ്ങുന്നതും പ്രതികരിക്കുന്നതും പരിശോധിക്കുന്ന അടിസ്ഥാന ടെസ്റ്റിനൊപ്പം പ്രവർത്തിപ്പിക്കാവുന്ന പരിതസ്ഥിതി REA എക്‌സ്‌പോർട്ട് ചെയ്യുന്നു. ടാസ്‌ക് ലക്ഷ്യങ്ങളും റിവാർഡ് പരിശോധനകളും നിർവചിക്കാനും പരിശീലനം നടത്താനും RL ഫ്രെയിംവർക്കുമായി ബന്ധിപ്പിക്കുക.
+
+[പരിതസ്ഥിതി നിർമ്മാണ മാർഗ്ഗദർശി](../agent-environments-quickstart.md) ·
+[പരിതസ്ഥിതി റഫറൻസ്](../agent-environments.md)
+
 ## ഉദാഹരണങ്ങൾ

 <a href="https://rea.tools/showcase/">
@@ -20,7 +20,7 @@

 **[Strona internetowa](https://rea.tools/pl/) · [Przewodniki](https://rea.tools/pl/guides/) · [Przykłady zastosowań](https://rea.tools/pl/showcase/)**

-[Szybki start](#szybki-start) · [Jak działa REA](#jak-działa-rea) · [Co możesz analizować](#co-możesz-analizować) · [Przykłady zastosowań](#przykłady-zastosowań) · [FAQ](#faq) · [Narzędzia GNU objdump i Rizin](../reverse-engineering-tools.md) · [Dokumentacja](#dokumentacja)
+[Szybki start](#szybki-start) · [Jak działa REA](#jak-działa-rea) · [Co możesz analizować](#co-możesz-analizować) · [Tworzenie środowisk RL](#build-rl-environments) · [Przykłady zastosowań](#przykłady-zastosowań) · [FAQ](#faq) · [Narzędzia GNU objdump i Rizin](../reverse-engineering-tools.md) · [Dokumentacja](#dokumentacja)

 <code>npx rea-agents setup</code>

@@ -196,6 +196,28 @@ Dla dużych plików zwiększ czas uruchomienia przez `REA_GHIDRA_STARTUP_TIMEOUT

 Obsługiwane formaty natywne i platformy zależą od dostawcy analizy. Zobacz [konfigurację Hoppera i Ghidry](../installation.md#hopper), [przewodnik IDA](../ida-provider.md), [Kuna](../kuna-provider.md) oraz [eksperymentalną obsługę Ghidry w systemie Windows](../windows-ghidra-p0.md). Ghidra obsługuje też [analizę 16-bitowego DOS-a](../ghidra-dos.md). Wybór dostawcy opisuje [przewodnik CLI](../cli.md#choose-a-provider). Sprawdź [dostępność w wydaniach](../installation.md#released-package-and-main) dla funkcji dodanych po najnowszym wydaniu npm.

+<a id="build-rl-environments"></a>
+
+## Tworzenie środowisk RL
+
+Stwórz lokalne środowisko, w którym agent AI może ćwiczyć zadania, takie jak wyszukiwanie zgłoszenia lub tworzenie folderu, bez uruchamiania oryginalnej aplikacji. Użyj go do uczenia ze wzmocnieniem (RL) lub sprawdzania, jak agent wykonuje zadania.
+
+REA zamienia nagrane żądania i odpowiedzi API w narzędzia, które agent może wywoływać. Środowisko używa nagranych danych i obsługuje zmiany tylko wtedy, gdy nagranie potwierdza ich efekty.
+
+Poproś agenta, aby za pomocą REA nagrał sesję na instancji testowej, na której może tworzyć, edytować i usuwać dane. Możesz też zacząć od pliku HAR, który zapisuje żądania i odpowiedzi sieciowe przeglądarki.
+
+Zbuduj środowisko za pomocą REA, a następnie uruchom je z osobno zainstalowanymi AgentEnv i Dockerem:
+
+```sh
+rea environment-build ./session.har ./my-env --name my-env --json
+agent-env run ./my-env
+```
+
+REA eksportuje gotowe do uruchomienia środowisko z podstawowym testem uruchamiania i odpowiedzi. Połącz je ze swoim frameworkiem RL, aby określić cele zadań, dodać sprawdzanie nagród i uruchomić trening.
+
+[Przewodnik tworzenia środowiska](../agent-environments-quickstart.md) ·
+[Dokumentacja środowisk](../agent-environments.md)
+
 ## Przykłady zastosowań

 <a href="https://rea.tools/pl/showcase/">
@@ -20,7 +20,7 @@

 **[Site](https://rea.tools/pt-BR/) · [Guias](https://rea.tools/pt-BR/guides/) · [Casos de uso](https://rea.tools/pt-BR/showcase/)**

-[Início rápido](#início-rápido) · [Como o REA funciona](#como-o-rea-funciona) · [O que você pode analisar](#o-que-você-pode-analisar) · [Casos de uso](#casos-de-uso) · [Perguntas frequentes](#perguntas-frequentes) · [Ferramentas GNU objdump e Rizin](../reverse-engineering-tools.md) · [Documentação](#documentação)
+[Início rápido](#início-rápido) · [Como o REA funciona](#como-o-rea-funciona) · [O que você pode analisar](#o-que-você-pode-analisar) · [Criar ambientes de RL](#build-rl-environments) · [Casos de uso](#casos-de-uso) · [Perguntas frequentes](#perguntas-frequentes) · [Ferramentas GNU objdump e Rizin](../reverse-engineering-tools.md) · [Documentação](#documentação)

 <code>npx rea-agents setup</code>

@@ -196,6 +196,28 @@ Para binários grandes, aumente o prazo de inicialização com `REA_GHIDRA_START

 Os formatos nativos e os sistemas anfitriões compatíveis variam por provedor. Consulte [configuração do Hopper e Ghidra](../installation.md#hopper), o [guia do IDA](../ida-provider.md), [Kuna](../kuna-provider.md) e o [suporte experimental ao Ghidra no Windows](../windows-ghidra-p0.md). O Ghidra também oferece [análise de DOS de 16 bits](../ghidra-dos.md). Para selecionar um provedor, consulte o [guia da CLI](../cli.md#choose-a-provider). Verifique a [disponibilidade nas versões](../installation.md#released-package-and-main) das funcionalidades adicionadas após a versão mais recente no npm.

+<a id="build-rl-environments"></a>
+
+## Criar ambientes de RL
+
+Crie um ambiente local onde um agente de IA possa praticar tarefas como encontrar uma issue ou criar uma pasta, sem executar o aplicativo original. Use para aprendizado por reforço (RL) ou para testar como o agente conclui tarefas.
+
+O REA transforma requisições e respostas de API gravadas em ferramentas que o agente pode chamar. O ambiente usa os dados gravados e só aceita alterações cujos efeitos sejam confirmados pela gravação.
+
+Peça ao agente para usar o REA e gravar uma sessão em uma instância de teste onde ele possa criar, editar e excluir dados. Você também pode começar com um arquivo HAR, que registra as requisições e respostas de rede do navegador.
+
+Crie com o REA e execute com o framework AgentEnv e o Docker instalados separadamente:
+
+```sh
+rea environment-build ./session.har ./my-env --name my-env --json
+agent-env run ./my-env
+```
+
+O REA exporta um ambiente executável com um teste básico para verificar se ele inicia e responde. Use com seu framework de RL para definir objetivos, adicionar verificações de recompensa e executar o treinamento.
+
+[Guia para criar um ambiente](../agent-environments-quickstart.md) ·
+[Referência de ambientes](../agent-environments.md)
+
 ## Casos de uso

 <a href="https://rea.tools/pt-BR/showcase/">
@@ -20,7 +20,7 @@

 **[Site web](https://rea.tools/) · [Ghiduri](https://rea.tools/guides/) · [Studii de caz](https://rea.tools/showcase/)**

-[Pornire rapidă](#pornire-rapidă) · [Cum funcționează REA](#cum-funcționează-rea) · [Ce poți analiza](#ce-poți-analiza) · [Studii de caz](#studii-de-caz) · [Întrebări frecvente](#întrebări-frecvente) · [Documentație](#documentație)
+[Pornire rapidă](#pornire-rapidă) · [Cum funcționează REA](#cum-funcționează-rea) · [Ce poți analiza](#ce-poți-analiza) · [Construiește medii RL](#build-rl-environments) · [Studii de caz](#studii-de-caz) · [Întrebări frecvente](#întrebări-frecvente) · [Documentație](#documentație)

 <code>npx rea-agents setup</code>

@@ -247,6 +247,28 @@ Pentru selectarea motorului, consultă [ghidul CLI](../cli.md#choose-a-provider)
 Verifică [disponibilitatea în versiunile publicate](../installation.md#released-package-and-main)
 pentru funcționalitățile adăugate după cea mai recentă versiune npm.

+<a id="build-rl-environments"></a>
+
+## Construiește medii RL
+
+Creează un mediu local în care un agent AI să exerseze sarcini precum găsirea unui issue sau crearea unui dosar, fără a rula aplicația originală. Folosește-l pentru învățare prin recompensă (RL) sau pentru a testa cât de bine îndeplinește agentul sarcinile.
+
+REA transformă cererile și răspunsurile API înregistrate în instrumente pe care agentul le poate apela. Mediul folosește datele înregistrate și permite modificări doar când înregistrarea le confirmă efectele.
+
+Cere agentului să folosească REA pentru a înregistra o sesiune pe o instanță de test unde poate crea, edita și șterge date. Poți începe și cu un fișier HAR, care înregistrează cererile și răspunsurile de rețea ale browserului.
+
+Construiește cu REA, apoi rulează cu frameworkul AgentEnv și Docker, instalate separat:
+
+```sh
+rea environment-build ./session.har ./my-env --name my-env --json
+agent-env run ./my-env
+```
+
+REA exportă un mediu executabil cu un test de bază care verifică pornirea și răspunsurile. Conectează-l la frameworkul RL pentru a defini obiectivele, a adăuga verificări de recompensă și a rula antrenarea.
+
+[Ghid pentru construirea unui mediu](../agent-environments-quickstart.md) ·
+[Referință pentru medii](../agent-environments.md)
+
 ## Studii de caz

 <a href="https://rea.tools/showcase/">
@@ -20,7 +20,7 @@

 **[Сайт](https://rea.tools/ru/) · [Руководства](https://rea.tools/ru/guides/) · [Примеры](https://rea.tools/ru/showcase/)**

-[Быстрый старт](#быстрый-старт) · [Как работает REA](#как-работает-rea) · [Что можно анализировать](#что-можно-анализировать) · [Примеры](#примеры) · [Частые вопросы](#частые-вопросы) · [Инструменты GNU objdump и Rizin](../reverse-engineering-tools.md) · [Документация](#документация)
+[Быстрый старт](#быстрый-старт) · [Как работает REA](#как-работает-rea) · [Что можно анализировать](#что-можно-анализировать) · [Создание RL-окружений](#build-rl-environments) · [Примеры](#примеры) · [Частые вопросы](#частые-вопросы) · [Инструменты GNU objdump и Rizin](../reverse-engineering-tools.md) · [Документация](#документация)

 <code>npx rea-agents setup</code>

@@ -196,6 +196,28 @@ REA требует Node.js 22.x (>=22.23.4), 24.x (>=24.22.1) или 26+ (>=26.1

 Нативные форматы и поддерживаемые системы различаются у разных провайдеров. См. [настройку Hopper и Ghidra](../installation.md#hopper), [руководство по IDA](../ida-provider.md), [Kuna](../kuna-provider.md) и [экспериментальную поддержку Ghidra в Windows](../windows-ghidra-p0.md). Ghidra также поддерживает [анализ 16-битного DOS](../ghidra-dos.md). Выбор провайдера описан в [руководстве по CLI](../cli.md#choose-a-provider). Для функций, добавленных после последней версии в npm, проверьте [доступность в релизах](../installation.md#released-package-and-main).

+<a id="build-rl-environments"></a>
+
+## Создание RL-окружений
+
+Создайте локальное окружение, где ИИ-агент сможет выполнять пробные задания, например искать задачу в трекере или создавать папку, без запуска исходного приложения. Используйте его для обучения с подкреплением (RL) или проверки того, как агент справляется с заданиями.
+
+REA превращает записанные API-запросы и ответы в инструменты, которые может вызывать агент. Окружение использует записанные данные и поддерживает изменения только тогда, когда запись подтверждает их эффект.
+
+Попросите агента использовать REA для записи сеанса на тестовом экземпляре, где ему разрешено создавать, редактировать и удалять данные. Можно начать и с HAR-файла, в котором записаны сетевые запросы и ответы браузера.
+
+Соберите окружение с REA, затем запустите его с отдельно установленными AgentEnv и Docker:
+
+```sh
+rea environment-build ./session.har ./my-env --name my-env --json
+agent-env run ./my-env
+```
+
+REA экспортирует готовое к запуску окружение с базовым тестом запуска и ответов. Подключите его к своему RL-фреймворку, чтобы задать цели, добавить проверки наград и запустить обучение.
+
+[Руководство по созданию окружения](../agent-environments-quickstart.md) ·
+[Справочник окружений](../agent-environments.md)
+
 ## Примеры

 <a href="https://rea.tools/ru/showcase/">
@@ -20,7 +20,7 @@

 **[เว็บไซต์](https://rea.tools/th/) · [คู่มือ](https://rea.tools/th/guides/) · [ตัวอย่างการใช้งาน](https://rea.tools/th/showcase/)**

-[เริ่มต้นอย่างรวดเร็ว](#เริ่มต้นอย่างรวดเร็ว) · [REA ทำงานอย่างไร](#rea-ทำงานอย่างไร) · [สิ่งที่วิเคราะห์ได้](#สิ่งที่วิเคราะห์ได้) · [ตัวอย่างการใช้งาน](#ตัวอย่างการใช้งาน) · [คำถามที่พบบ่อย](#คำถามที่พบบ่อย) · [เครื่องมือ GNU objdump และ Rizin](../reverse-engineering-tools.md) · [เอกสาร](#เอกสาร)
+[เริ่มต้นอย่างรวดเร็ว](#เริ่มต้นอย่างรวดเร็ว) · [REA ทำงานอย่างไร](#rea-ทำงานอย่างไร) · [สิ่งที่วิเคราะห์ได้](#สิ่งที่วิเคราะห์ได้) · [สร้างสภาพแวดล้อม RL](#build-rl-environments) · [ตัวอย่างการใช้งาน](#ตัวอย่างการใช้งาน) · [คำถามที่พบบ่อย](#คำถามที่พบบ่อย) · [เครื่องมือ GNU objdump และ Rizin](../reverse-engineering-tools.md) · [เอกสาร](#เอกสาร)

 <code>npx rea-agents setup</code>

@@ -196,6 +196,28 @@ REA ต้องใช้ Node.js 22.x (>=22.23.4), 24.x (>=24.22.1) หรื

 รูปแบบไบนารีเนทีฟและแพลตฟอร์มที่รองรับแตกต่างกันตามผู้ให้บริการวิเคราะห์ ดู[การตั้งค่า Hopper และ Ghidra](../installation.md#hopper), [คู่มือ IDA](../ida-provider.md) [Kuna](../kuna-provider.md) และ[การรองรับ Ghidra บน Windows แบบทดลอง](../windows-ghidra-p0.md) Ghidra ยังรองรับ[การวิเคราะห์ DOS แบบ 16 บิต](../ghidra-dos.md) สำหรับการเลือกผู้ให้บริการ ดู[คู่มือ CLI](../cli.md#choose-a-provider) ตรวจสอบ[ความพร้อมใช้งานในแต่ละรุ่น](../installation.md#released-package-and-main) สำหรับฟีเจอร์ที่เพิ่มหลังรุ่นล่าสุดบน npm

+<a id="build-rl-environments"></a>
+
+## สร้างสภาพแวดล้อม RL
+
+สร้างสภาพแวดล้อมในเครื่องให้เอเจนต์ AI ฝึกทำงาน เช่น ค้นหา issue หรือสร้างโฟลเดอร์ โดยไม่ต้องรันแอปต้นฉบับ ใช้สำหรับการเรียนรู้แบบเสริมกำลัง (RL) หรือทดสอบว่าเอเจนต์ทำงานได้ดีเพียงใด
+
+REA เปลี่ยนคำขอและคำตอบ API ที่บันทึกไว้เป็นเครื่องมือที่เอเจนต์เรียกใช้ได้ สภาพแวดล้อมใช้ข้อมูลที่บันทึกไว้และรองรับการเปลี่ยนแปลงเฉพาะเมื่อข้อมูลบันทึกยืนยันผลของการเปลี่ยนแปลงนั้น
+
+ขอให้เอเจนต์ใช้ REA บันทึกเซสชันบนระบบทดสอบที่อนุญาตให้สร้าง แก้ไข และลบข้อมูลได้ หรือเริ่มจากไฟล์ HAR ซึ่งบันทึกคำขอและคำตอบเครือข่ายของเบราว์เซอร์
+
+สร้างด้วย REA แล้วรันด้วยเฟรมเวิร์ก AgentEnv และ Docker ที่ติดตั้งแยกต่างหาก:
+
+```sh
+rea environment-build ./session.har ./my-env --name my-env --json
+agent-env run ./my-env
+```
+
+REA ส่งออกสภาพแวดล้อมที่รันได้พร้อมการทดสอบพื้นฐานว่าเริ่มทำงานและตอบสนองได้ เชื่อมต่อกับเฟรมเวิร์ก RL เพื่อกำหนดเป้าหมายงาน เพิ่มการตรวจสอบรางวัล และฝึกเอเจนต์
+
+[คู่มือสร้างสภาพแวดล้อม](../agent-environments-quickstart.md) ·
+[เอกสารอ้างอิงสภาพแวดล้อม](../agent-environments.md)
+
 ## ตัวอย่างการใช้งาน

 <a href="https://rea.tools/th/showcase/">
@@ -20,7 +20,7 @@

 **[Web sitesi](https://rea.tools/tr/) · [Rehberler](https://rea.tools/tr/guides/) · [Örnek çalışmalar](https://rea.tools/tr/showcase/)**

-[Hızlı başlangıç](#hızlı-başlangıç) · [REA nasıl çalışır](#rea-nasıl-çalışır) · [Neleri analiz edebilirsiniz](#neleri-analiz-edebilirsiniz) · [Örnek çalışmalar](#örnek-çalışmalar) · [Sık sorulan sorular](#sık-sorulan-sorular) · [GNU objdump ve Rizin araçları](../reverse-engineering-tools.md) · [Belgeler](#belgeler)
+[Hızlı başlangıç](#hızlı-başlangıç) · [REA nasıl çalışır](#rea-nasıl-çalışır) · [Neleri analiz edebilirsiniz](#neleri-analiz-edebilirsiniz) · [RL ortamları oluşturun](#build-rl-environments) · [Örnek çalışmalar](#örnek-çalışmalar) · [Sık sorulan sorular](#sık-sorulan-sorular) · [GNU objdump ve Rizin araçları](../reverse-engineering-tools.md) · [Belgeler](#belgeler)

 <code>npx rea-agents setup</code>

@@ -192,6 +192,28 @@ Statik JavaScript ve .NET incelemesi, uygulamayı çalıştırmadan sağlanan do

 Yerel makine kodu içeren ikili dosya biçimleri ve ana bilgisayar desteği sağlayıcıya göre değişir. [Hopper ve Ghidra kurulumu](../installation.md#hopper), isteğe bağlı native MCP bridge'i de açıklayan [IDA rehberi](../ida-provider.md), [Kuna](../kuna-provider.md) ve [Windows için deneysel Ghidra desteği](../windows-ghidra-p0.md) belgelerine bakın. Ghidra ayrıca [16 bit DOS analizini](../ghidra-dos.md) destekler. Büyük ikili dosyalar için sağlayıcının başlatma zaman aşımını `REA_GHIDRA_STARTUP_TIMEOUT_MS` veya `REA_HOPPER_STARTUP_TIMEOUT_MS` ile artırın. Sağlayıcı seçimi için [CLI rehberine](../cli.md#choose-a-provider) bakın. En son npm sürümünden sonra eklenen özellikler için [sürümlerde kullanılabilirliği](../installation.md#released-package-and-main) kontrol edin.

+<a id="build-rl-environments"></a>
+
+## RL ortamları oluşturun
+
+Asıl uygulamayı çalıştırmadan, yapay zekâ ajanının sorun bulma veya klasör oluşturma gibi görevleri deneyeceği yerel bir ortam oluşturun. Bunu pekiştirmeli öğrenme (RL) veya ajanın görevleri ne kadar iyi tamamladığını test etmek için kullanın.
+
+REA, kaydedilmiş API isteklerini ve yanıtlarını ajanın çağırabileceği araçlara dönüştürür. Ortam kayıtlı verileri kullanır ve yalnızca etkisi kayıtla doğrulanan değişiklikleri destekler.
+
+Ajanınızdan, veri oluşturma, düzenleme ve silme izni verdiğiniz bir test ortamında REA ile bir oturum kaydetmesini isteyin. Tarayıcının ağ isteklerini ve yanıtlarını kaydeden bir HAR dosyasıyla da başlayabilirsiniz.
+
+REA ile oluşturun, ardından ayrıca kurulan AgentEnv çerçevesi ve Docker ile çalıştırın:
+
+```sh
+rea environment-build ./session.har ./my-env --name my-env --json
+agent-env run ./my-env
+```
+
+REA, çalıştırılabilir bir ortamı ve başlayıp yanıt verdiğini kontrol eden temel bir testi dışa aktarır. Görev hedeflerini ve ödül kontrollerini tanımlamak, ardından eğitim çalıştırmak için RL çerçevenizle kullanın.
+
+[Ortam oluşturma rehberi](../agent-environments-quickstart.md) ·
+[Ortam referansı](../agent-environments.md)
+
 ## Örnek çalışmalar

 <a href="https://rea.tools/tr/showcase/">
@@ -20,7 +20,7 @@

 **[Сайт](https://rea.tools/uk/) · [Посібники](https://rea.tools/uk/guides/) · [Приклади](https://rea.tools/uk/showcase/)**

-[Швидкий старт](#швидкий-старт) · [Як працює REA](#як-працює-rea) · [Що можна аналізувати](#що-можна-аналізувати) · [Приклади](#приклади) · [Поширені запитання](#поширені-запитання) · [Інструменти GNU objdump і Rizin](../reverse-engineering-tools.md) · [Документація](#документація)
+[Швидкий старт](#швидкий-старт) · [Як працює REA](#як-працює-rea) · [Що можна аналізувати](#що-можна-аналізувати) · [Створення RL-середовищ](#build-rl-environments) · [Приклади](#приклади) · [Поширені запитання](#поширені-запитання) · [Інструменти GNU objdump і Rizin](../reverse-engineering-tools.md) · [Документація](#документація)

 <code>npx rea-agents setup</code>

@@ -196,6 +196,28 @@ REA потребує Node.js 22.x (>=22.23.4), 24.x (>=24.22.1) або 26+ (>=26

 Нативні формати й підтримка систем відрізняються залежно від провайдера. Дивіться [налаштування Hopper і Ghidra](../installation.md#hopper), [посібник IDA](../ida-provider.md), [Kuna](../kuna-provider.md) та [експериментальну підтримку Ghidra у Windows](../windows-ghidra-p0.md). Ghidra також підтримує [аналіз 16-бітного DOS](../ghidra-dos.md). Для вибору провайдера дивіться [посібник CLI](../cli.md#choose-a-provider). Для функцій, доданих після найновішої версії в npm, перевірте [доступність у випусках](../installation.md#released-package-and-main).

+<a id="build-rl-environments"></a>
+
+## Створення RL-середовищ
+
+Створіть локальне середовище, де ШІ-агент може тренуватися виконувати завдання, як-от пошук issue або створення папки, без запуску початкового застосунку. Використовуйте його для навчання з підкріпленням (RL) або перевірки того, як агент виконує завдання.
+
+REA перетворює записані API-запити й відповіді на інструменти, які може викликати агент. Середовище використовує записані дані й підтримує зміни лише тоді, коли запис підтверджує їхні ефекти.
+
+Попросіть агента використати REA для запису сеансу на тестовому екземплярі, де йому дозволено створювати, редагувати й видаляти дані. Можна також почати з HAR-файлу, що містить мережеві запити й відповіді браузера.
+
+Створіть середовище з REA, а потім запустіть його з окремо встановленими AgentEnv і Docker:
+
+```sh
+rea environment-build ./session.har ./my-env --name my-env --json
+agent-env run ./my-env
+```
+
+REA експортує готове до запуску середовище з базовим тестом запуску й відповідей. Підключіть його до свого RL-фреймворку, щоб задати цілі, додати перевірки винагород і запустити навчання.
+
+[Посібник зі створення середовища](../agent-environments-quickstart.md) ·
+[Довідник середовищ](../agent-environments.md)
+
 ## Приклади

 <a href="https://rea.tools/uk/showcase/">
@@ -20,7 +20,7 @@

 **[Website](https://rea.tools/) · [Guides](https://rea.tools/guides/) · [Showcases](https://rea.tools/showcase/)**

-[Jaldi shuru karein](#jaldi-shuru-karein) · [REA kaise kaam karta hai](#rea-kaise-kaam-karta-hai) · [Kya kuch analyze kar sakte hain](#kya-kuch-analyze-kar-sakte-hain) · [Amli misaalein](#amli-misaalein) · [FAQ](#faq) · [Documentation](#documentation)
+[Jaldi shuru karein](#jaldi-shuru-karein) · [REA kaise kaam karta hai](#rea-kaise-kaam-karta-hai) · [Kya kuch analyze kar sakte hain](#kya-kuch-analyze-kar-sakte-hain) · [RL environments banayein](#build-rl-environments) · [Amli misaalein](#amli-misaalein) · [FAQ](#faq) · [Documentation](#documentation)

 <code>npx rea-agents setup</code>

@@ -246,6 +246,28 @@ Provider select karne ke liye [CLI guide](../cli.md#choose-a-provider) dekhein.
 Latest npm release ke baad add hone wale features ki
 [release availability](../installation.md#released-package-and-main) check karein.

+<a id="build-rl-environments"></a>
+
+## RL environments banayein
+
+AI agent ke liye local environment banayein jahan woh asal app chalaye baghair issue dhoondhne ya folder banane jaise kaam ki mashq kar sake. Ise reinforcement learning (RL) ya agent ke kaam poore karne ki salahiyat jaanchne ke liye istemal karein.
+
+REA record kiye hue API requests aur responses ko aise tools mein badalta hai jinhein agent call kar sakta hai. Environment recorded data istemal karta hai aur sirf woh tabdeeliyan support karta hai jin ke asraat recording tasdeeq karti hai.
+
+Agent se kahein ke REA ke zariye test instance par session record kare jahan use data banane, edit karne aur delete karne ki ijazat ho. Aap HAR file se bhi shuru kar sakte hain, jo browser ke network requests aur responses ka record hoti hai.
+
+REA se banayein, phir alag se install kiye hue AgentEnv framework aur Docker ke saath chalayein:
+
+```sh
+rea environment-build ./session.har ./my-env --name my-env --json
+agent-env run ./my-env
+```
+
+REA chalne ke liye tayyar environment aur aik bunyadi test export karta hai jo us ka shuru hona aur jawab dena check karta hai. Apne RL framework ke saath task goals aur reward checks tay karein aur training chalayein.
+
+[Environment banane ki rehnumai](../agent-environments-quickstart.md) ·
+[Environment reference](../agent-environments.md)
+
 ## Amli misaalein

 <a href="https://rea.tools/showcase/">
@@ -20,7 +20,7 @@

 **[Trang web](https://rea.tools/vi/) · [Hướng dẫn](https://rea.tools/vi/guides/) · [Các nghiên cứu điển hình](https://rea.tools/vi/showcase/)**

-[Bắt đầu nhanh](#bắt-đầu-nhanh) · [Cách REA hoạt động](#cách-rea-hoạt-động) · [Những gì bạn có thể phân tích](#những-gì-bạn-có-thể-phân-tích) · [Các nghiên cứu điển hình](#các-nghiên-cứu-điển-hình) · [Câu hỏi thường gặp](#câu-hỏi-thường-gặp) · [Công cụ GNU objdump và Rizin](../reverse-engineering-tools.md) · [Tài liệu](#tài-liệu)
+[Bắt đầu nhanh](#bắt-đầu-nhanh) · [Cách REA hoạt động](#cách-rea-hoạt-động) · [Những gì bạn có thể phân tích](#những-gì-bạn-có-thể-phân-tích) · [Xây dựng môi trường RL](#build-rl-environments) · [Các nghiên cứu điển hình](#các-nghiên-cứu-điển-hình) · [Câu hỏi thường gặp](#câu-hỏi-thường-gặp) · [Công cụ GNU objdump và Rizin](../reverse-engineering-tools.md) · [Tài liệu](#tài-liệu)

 <code>npx rea-agents setup</code>

@@ -196,6 +196,28 @@ Với tệp nhị phân lớn, tăng hạn khởi động bằng `REA_GHIDRA_STA

 Định dạng mã máy và nền tảng chạy REA được hỗ trợ khác nhau tùy trình phân tích. Xem [thiết lập Hopper và Ghidra](../installation.md#hopper), [hướng dẫn IDA](../ida-provider.md), [Kuna](../kuna-provider.md) và [hỗ trợ Ghidra thử nghiệm trên Windows](../windows-ghidra-p0.md). Ghidra cũng hỗ trợ [phân tích DOS 16 bit](../ghidra-dos.md). Để chọn trình phân tích, xem [hướng dẫn CLI](../cli.md#choose-a-provider). Kiểm tra [khả năng sử dụng theo bản phát hành](../installation.md#released-package-and-main) đối với tính năng được bổ sung sau phiên bản npm mới nhất.

+<a id="build-rl-environments"></a>
+
+## Xây dựng môi trường RL
+
+Tạo môi trường cục bộ để tác tử AI luyện các tác vụ như tìm issue hoặc tạo thư mục mà không cần chạy ứng dụng gốc. Dùng môi trường này cho học tăng cường (RL) hoặc để kiểm tra khả năng hoàn thành tác vụ của tác tử.
+
+REA biến các yêu cầu và phản hồi API đã ghi thành công cụ mà tác tử có thể gọi. Môi trường dùng dữ liệu đã ghi và chỉ hỗ trợ thay đổi khi bản ghi xác nhận tác động của thay đổi đó.
+
+Yêu cầu tác tử dùng REA ghi một phiên trên bản thử nghiệm mà tác tử được phép tạo, sửa và xóa dữ liệu. Bạn cũng có thể bắt đầu với tệp HAR, bản ghi các yêu cầu và phản hồi mạng của trình duyệt.
+
+Xây dựng bằng REA, sau đó chạy với AgentEnv và Docker được cài riêng:
+
+```sh
+rea environment-build ./session.har ./my-env --name my-env --json
+agent-env run ./my-env
+```
+
+REA xuất môi trường chạy được cùng bài kiểm tra cơ bản để xác nhận môi trường khởi động và phản hồi. Kết nối với framework RL để đặt mục tiêu tác vụ, thêm kiểm tra phần thưởng và chạy huấn luyện.
+
+[Hướng dẫn xây dựng môi trường](../agent-environments-quickstart.md) ·
+[Tài liệu tham chiếu môi trường](../agent-environments.md)
+
 ## Các nghiên cứu điển hình

 <a href="https://rea.tools/vi/showcase/">
@@ -20,7 +20,7 @@

 **[網站](https://rea.tools/zh-TW/) · [指南](https://rea.tools/zh-TW/guides/) · [案例](https://rea.tools/zh-TW/showcase/)**

-[快速開始](#快速開始) · [REA 的工作原理](#rea-的工作原理) · [可以分析什麼](#可以分析什麼) · [案例](#案例) · [常見問題](#常見問題) · [GNU objdump 與 Rizin 工具](../reverse-engineering-tools.md) · [文件](#文件)
+[快速開始](#快速開始) · [REA 的工作原理](#rea-的工作原理) · [可以分析什麼](#可以分析什麼) · [建立 RL 環境](#build-rl-environments) · [案例](#案例) · [常見問題](#常見問題) · [GNU objdump 與 Rizin 工具](../reverse-engineering-tools.md) · [文件](#文件)

 <code>npx rea-agents setup</code>

@@ -194,6 +194,28 @@ REA 需要 Node.js 22.x（>=22.23.4）、24.x（>=24.22.1）或 26+ (>=26.12.1)

 不同提供者支援的原生格式和主機系統有所不同。請參閱 [Hopper 與 Ghidra 設定](../installation.md#hopper)、[IDA 指南](../ida-provider.md)、[Kuna](../kuna-provider.md)和[實驗性 Windows Ghidra 支援](../windows-ghidra-p0.md)。Ghidra 也支援 [16 位 DOS 分析](../ghidra-dos.md)。提供者選擇見 [CLI 指南](../cli.md#choose-a-provider)。對於最新 npm 版本發佈後新增的功能，請查看[發佈可用性](../installation.md#released-package-and-main)。

+<a id="build-rl-environments"></a>
+
+## 建立 RL 環境
+
+為 AI 代理建立本機練習環境，讓它練習尋找 issue、建立資料夾等任務，無需執行原應用程式。這個環境可用於強化學習（RL），也可用於測試代理完成任務的能力。
+
+REA 將錄製的 API 請求與回應轉為代理可呼叫的工具。環境使用錄製的資料，只有錄製證據確認了某項修改的效果，才會支援該修改。
+
+請代理使用 REA 在測試執行個體上錄製一次工作階段，並明確允許它建立、編輯和刪除資料。也可從 HAR 檔案開始，它記錄了瀏覽器的網路請求與回應。
+
+用 REA 建立，再透過另行安裝的 AgentEnv 框架與 Docker 執行：
+
+```sh
+rea environment-build ./session.har ./my-env --name my-env --json
+agent-env run ./my-env
+```
+
+REA 匯出可直接執行的環境，並附帶基本測試，檢查環境能否啟動與回應。將它接入 RL 框架，即可設定任務目標、加入獎勵檢查並執行訓練。
+
+[建立環境指南](../agent-environments-quickstart.md) ·
+[環境參考文件](../agent-environments.md)
+
 ## 案例

 <a href="https://rea.tools/zh-TW/showcase/">
@@ -20,7 +20,7 @@

 **[网站](https://rea.tools/zh-CN/) · [指南](https://rea.tools/zh-CN/guides/) · [案例](https://rea.tools/zh-CN/showcase/)**

-[快速开始](#快速开始) · [REA 的工作原理](#rea-的工作原理) · [可以分析什么](#可以分析什么) · [案例](#案例) · [常见问题](#常见问题) · [GNU objdump 和 Rizin 工具](../reverse-engineering-tools.md) · [文档](#文档)
+[快速开始](#快速开始) · [REA 的工作原理](#rea-的工作原理) · [可以分析什么](#可以分析什么) · [构建 RL 环境](#build-rl-environments) · [案例](#案例) · [常见问题](#常见问题) · [GNU objdump 和 Rizin 工具](../reverse-engineering-tools.md) · [文档](#文档)

 <code>npx rea-agents setup</code>

@@ -194,6 +194,28 @@ REA 需要 Node.js 22.x（>=22.23.4）、24.x（>=24.22.1）或 26+ (>=26.12.1)

 不同提供方支持的原生格式和主机系统有所不同。请参阅 [Hopper 与 Ghidra 设置](../installation.md#hopper)、[IDA 指南](../ida-provider.md)、[Kuna](../kuna-provider.md)和[实验性 Windows Ghidra 支持](../windows-ghidra-p0.md)。Ghidra 也支持 [16 位 DOS 分析](../ghidra-dos.md)。提供方选择见 [CLI 指南](../cli.md#choose-a-provider)。对于最新 npm 版本发布后新增的功能，请查看[发布可用性](../installation.md#released-package-and-main)。

+<a id="build-rl-environments"></a>
+
+## 构建 RL 环境
+
+为 AI 智能体构建本地练习环境，让它练习查找 issue、创建文件夹等任务，无需运行原应用。这个环境可用于强化学习（RL），也可用于测试智能体完成任务的能力。
+
+REA 将录制的 API 请求和响应转为智能体可调用的工具。环境使用录制的数据，只有录制证据确认了某项修改的效果，才会支持该修改。
+
+让智能体使用 REA 在测试实例上录制一次会话，并明确允许它创建、编辑和删除数据。也可以从 HAR 文件开始，它记录了浏览器的网络请求和响应。
+
+用 REA 构建，再通过单独安装的 AgentEnv 框架和 Docker 运行：
+
+```sh
+rea environment-build ./session.har ./my-env --name my-env --json
+agent-env run ./my-env
+```
+
+REA 导出可直接运行的环境，并附带基本测试，检查环境能否启动和响应。将它接入 RL 框架，即可设置任务目标、添加奖励检查并运行训练。
+
+[构建环境指南](../agent-environments-quickstart.md) ·
+[环境参考文档](../agent-environments.md)
+
 ## 案例

 <a href="https://rea.tools/zh-CN/showcase/">
@@ -0,0 +1,83 @@
+# Agent environment implementation index
+
+This index covers all 26 PRs authored by
+[earakely-scale](https://github.com/morluto/rea/pulls?q=is%3Apr+author%3Aearakely-scale)
+in `morluto/rea`, checked on 2026-10-25 against main
+`5d428390996498bc4dcca4da934641557f9109bc`. Twenty-five were merged; #5722
+was closed without merging. The table describes the resulting work rather
+than treating each original PR proposal as the current contract.
+
+Start with the [quickstart](../../agent-environments-quickstart.md) for a
+user workflow or the [reference](../../agent-environments.md) for current
+contracts. [Design issue #4933](https://github.com/morluto/rea/issues/4933)
+records the original four-part proposal. Its stateless replay description
+predates state serving and confirmed writes.
+
+## PR map
+
+All entries are merged unless marked otherwise. Verification links point
+to the corresponding slice's recorded checks, with their original versions,
+platforms, failures, and limitations.
+
+| PR                                                                   | Contribution                                                                                                                                                                                  | Verification                                                                                                                     |
+| -------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| [#4954](https://github.com/morluto/rea/pull/4954)                    | Project HAR Evidence into an environment manifest with inferred tool templates and explicit unknowns.                                                                                         | [Manifest view](manifest-view/verification.md)                                                                                   |
+| [#4955](https://github.com/morluto/rea/pull/4955)                    | Add explicit streamable HTTP serving for REA MCP; stdio remains the default.                                                                                                                  | [HTTP transport](http-transport/verification.md)                                                                                 |
+| [#4975](https://github.com/morluto/rea/pull/4975)                    | Serve retained exchanges as MCP tools, with the environment card and replay data-plane stub.                                                                                                  | [Environment serve](environment-serve/verification.md)                                                                           |
+| [#4999](https://github.com/morluto/rea/pull/4999)                    | Export authenticated capture/manifest pairs as pinned AgentEnv bundles with a verifier and smoke task.                                                                                        | [Environment export](environment-export/verification.md)                                                                         |
+| [#5182](https://github.com/morluto/rea/pull/5182)                    | Accept browser-scenario Evidence as a manifest, serve, and export input.                                                                                                                      | [Scenario capture](scenario-capture/verification.md)                                                                             |
+| [#5293](https://github.com/morluto/rea/pull/5293)                    | Accept Evidence-file sources for richer captures and add opt-in sibling-pair path templating.                                                                                                 | [Rich captures](rich-captures/verification.md)                                                                                   |
+| [#5319](https://github.com/morluto/rea/pull/5319)                    | Extract initial entities, documents, and checked read plans with the environment-state view.                                                                                                  | [State view](state-view/verification.md)                                                                                         |
+| [#5351](https://github.com/morluto/rea/pull/5351)                    | Make state serving the default; add reset/load/get operations, replay fallback, and `--replay-only`.                                                                                          | [State serve](state-serve/verification.md)                                                                                       |
+| [#5352](https://github.com/morluto/rea/pull/5352)                    | Back more read shapes with state and describe tool responses and annotations.                                                                                                                 | [State coverage](state-coverage/verification.md)                                                                                 |
+| [#5600](https://github.com/morluto/rea/pull/5600)                    | Apply create, update, delete, and document effects only when later reads confirm them without contradiction.                                                                                  | [State writes](state-writes/verification.md)                                                                                     |
+| [#5664](https://github.com/morluto/rea/pull/5664)                    | Share inferred path positions across tools with opt-in `prefix-variance`, connecting literal writes to templated reads.                                                                       | [Prefix variance](prefix-variance/verification.md)                                                                               |
+| [#5699](https://github.com/morluto/rea/pull/5699)                    | Compare the environment offline against separately recorded probe sequences from the application.                                                                                             | [Fidelity compare](fidelity-compare/verification.md)                                                                             |
+| [#5722 (closed, unmerged)](https://github.com/morluto/rea/pull/5722) | Proposed independently reset recording sessions. The author closed it after six applications showed no held-out agreement gain; identified model gaps took priority.                          | [Closure explanation](https://github.com/morluto/rea/pull/5722#issuecomment-6305512072)                                          |
+| [#5787](https://github.com/morluto/rea/pull/5787)                    | Decide whole-list membership per request line so mixed filtered/unfiltered tools can show new entities.                                                                                       | [List lines](list-lines/verification.md)                                                                                         |
+| [#5800](https://github.com/morluto/rea/pull/5800)                    | Learn supported list filters, substring search, sorting, paging, and counters from recordings.                                                                                                | [List queries](list-queries/verification.md)                                                                                     |
+| [#6136](https://github.com/morluto/rea/pull/6136)                    | Explain copied or renamed values and regenerated scalar or nested UUIDs while withholding unsupported links.                                                                                  | [Assigned values](write-assigned-values/verification.md)                                                                         |
+| [#6138](https://github.com/morluto/rea/pull/6138)                    | Preserve the clock spelling and precision each read view shows after a write.                                                                                                                 | [View clock spelling](view-clock-spelling/verification.md)                                                                       |
+| [#6169](https://github.com/morluto/rea/pull/6169)                    | Handle bodiless write replies, proven omitted fields, projected reads, and digit-group sequences.                                                                                             | [Write coverage](write-coverage/verification.md)                                                                                 |
+| [#6385](https://github.com/morluto/rea/pull/6385)                    | Find more state targets, distinguish read-only POSTs, and handle variant views and differing create/read paths.                                                                               | [State targets](state-targets/verification.md)                                                                                   |
+| [#6897](https://github.com/morluto/rea/pull/6897)                    | Extend evidence-gated rules for bulk writes, item actions, generated values, query constraints, and ordering.                                                                                 | [Write rules](write-rules/verification.md)                                                                                       |
+| [#6929](https://github.com/morluto/rea/pull/6929)                    | Bound create learning and invalidate stale write proofs. The original branch also developed the one-step builder and coverage report, integrated through stacked #6946 before this PR merged. | [Build workflow and verification](environment-build/verification.md), [final PR scope](https://github.com/morluto/rea/pull/6929) |
+| [#6946](https://github.com/morluto/rea/pull/6946)                    | Complete the agent workflow with same-origin scenario request actions, `export_environment_bundle`, and recording instructions; integrate `environment-build` and coverage from its stack.    | [Environment from a prompt](environment-prompt/verification.md)                                                                  |
+| [#6967](https://github.com/morluto/rea/pull/6967)                    | Retain browser request timing so scenario-derived environments can learn write clocks.                                                                                                        | [Scenario timing](scenario-timing/verification.md)                                                                               |
+| [#7025](https://github.com/morluto/rea/pull/7025)                    | Explain composed response strings, trimmed fractional clocks, and generated integer identities.                                                                                               | [Derived values](write-derived-values/verification.md)                                                                           |
+| [#7034](https://github.com/morluto/rea/pull/7034)                    | Learn compatible create variations across calls, sorted echoes, referenced entities, and nested view projections.                                                                             | [Create calls](write-create-calls/verification.md)                                                                               |
+| [#7080](https://github.com/morluto/rea/pull/7080)                    | Reconcile lighter create responses with read-backs and learn re-derived slugs and clocks in whole-object updates.                                                                             | [Write views](write-views/verification.md)                                                                                       |
+
+Multi-session capture fusion from #5722 is not a shipped capability. Repeated
+calls inside one supported capture, as learned by #7034, are a separate feature.
+
+## Evidence to use when describing the feature
+
+The contributor's [example repository](https://github.com/earakely-scale/rea-environments)
+contains the original capture/export/evaluation pipeline and links to published
+bundles. Its Grafana row records 105 exchanges and 48 manifest tools, matching
+the capture count in the demo. The README describes an earlier replay workflow;
+its counts and model scores should remain attributed to that snapshot.
+
+The [prompt workflow verification](environment-prompt/verification.md) records
+five applications built by an agent from individual prompts: every exported
+bundle passed smoke, while three of the five served writes. Later
+[timing](scenario-timing/verification.md),
+[derived-value](write-derived-values/verification.md), and
+[create-call](write-create-calls/verification.md) work addresses specific gaps
+found in those recordings. The earlier write counts are not current limits.
+
+The [write-view verification](write-views/verification.md) records a later
+held-out round where 10 of 20 targeted write tools were served, up from 8.
+Its original census retained 132 served writes across 69 existing captures.
+These are source-reported measurements at the recorded revisions. The
+[merged PR's review follow-up](https://github.com/morluto/rea/pull/7080)
+explicitly says its real-application census and agent tasks were not rerun
+after the final fixes; the local CLI/MCP regressions cover those fixes.
+
+Smoke checks demonstrate bundle/framework compatibility for the tested
+configuration. Retrieval rewards demonstrate particular task outcomes.
+`environment-compare` measures agreement on recorded probes, with explicit
+normalizations and omissions. Keep these claims separate, and retain the
+version and coverage limits when quoting any result. This index is a source
+and PR review; it does not constitute a new real-application or benchmark run.