diff --git a/AGENTS.md b/AGENTS.md
index f9f2b6c..49e420e 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -41,10 +41,11 @@ The bot interface is strictly organized into 5 category hubs:
 4. **`System` (مدیریت سیستم)**: Emergency fleet pause/resume (`/pause`, `/resume`), dynamic release notes (`/changes`), and comprehensive documentation (`/help`).
 5. **`Monitor` (مانیتورینگ و آمار)**: Live queue & channel throughput statistics (`/stats`), unresolved error log review & bulk-fix (`/errors`), and Grafana time-range graphs.
 
-### 3.2 Release Notes Delivery
+### 3.2 Release Notes Delivery & Environment Configuration
+- **Always use app `.env` file**: Always read bot credentials (`BOT_TOKEN`), admin IDs (`ADMIN_USER_IDS`), and configurations directly from `/projects/telegram-bots/copykar/.env`.
 - **Never save release notes to a static file**: Do not create or keep `RELEASE_NOTES.md` on disk.
 - **Dynamic Generation**: Always generate release notes dynamically strictly describing the changes of the current commit.
-- **Direct Admin DMs**: Always send release notes via the Telegram bot directly to admin private DMs (`ADMIN_USER_IDS`), never to the review channel.
+- **Direct Admin DMs Only**: Always dispatch release notes via the Telegram bot directly to admin private DMs (`ADMIN_USER_IDS`) using the `.env` configuration (and proxy `http://127.0.0.1:10809` if needed), never to any public or review channel.
 
 ### 3.3 Target Channel Context History
 - Target channels support injecting recent published history (`context_message_count`) into AI rewriting prompts.
diff --git a/GEMINI.md b/GEMINI.md
index f9f2b6c..49e420e 100644
--- a/GEMINI.md
+++ b/GEMINI.md
@@ -41,10 +41,11 @@ The bot interface is strictly organized into 5 category hubs:
 4. **`System` (مدیریت سیستم)**: Emergency fleet pause/resume (`/pause`, `/resume`), dynamic release notes (`/changes`), and comprehensive documentation (`/help`).
 5. **`Monitor` (مانیتورینگ و آمار)**: Live queue & channel throughput statistics (`/stats`), unresolved error log review & bulk-fix (`/errors`), and Grafana time-range graphs.
 
-### 3.2 Release Notes Delivery
+### 3.2 Release Notes Delivery & Environment Configuration
+- **Always use app `.env` file**: Always read bot credentials (`BOT_TOKEN`), admin IDs (`ADMIN_USER_IDS`), and configurations directly from `/projects/telegram-bots/copykar/.env`.
 - **Never save release notes to a static file**: Do not create or keep `RELEASE_NOTES.md` on disk.
 - **Dynamic Generation**: Always generate release notes dynamically strictly describing the changes of the current commit.
-- **Direct Admin DMs**: Always send release notes via the Telegram bot directly to admin private DMs (`ADMIN_USER_IDS`), never to the review channel.
+- **Direct Admin DMs Only**: Always dispatch release notes via the Telegram bot directly to admin private DMs (`ADMIN_USER_IDS`) using the `.env` configuration (and proxy `http://127.0.0.1:10809` if needed), never to any public or review channel.
 
 ### 3.3 Target Channel Context History
 - Target channels support injecting recent published history (`context_message_count`) into AI rewriting prompts.