From 738bc3dea8c1b691e0df4fccc4e60587538ab479 Mon Sep 17 00:00:00 2001
From: thePR0M3TH3AN <53631862+PR0M3TH3AN@users.noreply.github.com>
Date: Sat, 31 May 2025 10:17:49 -0400
Subject: [PATCH] Clarify usage of `startup.sh` in AGENTS.md documentation

Updated the instructions to emphasize that after invoking `./startup.sh`, users should not run `python scripts/<script>.py` directly, as it will lead to import errors. Removed outdated example and reinforced the importance of the `startup.sh` wrapper for module execution.
---
 AGENTS.md | 7 +------
 1 file changed, 1 insertion(+), 6 deletions(-)

diff --git a/AGENTS.md b/AGENTS.md
index e0fb706..4c2ea0a 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -13,12 +13,7 @@
 
 * Running a script this way ensures that `import scripts.common` (and other `scripts.*` imports) resolve correctly.
 
-* If you ever need to call a different script, still invoke it under `./startup.sh`, for example:
-
-  ```bash
-  # Custom-chart example:
-  ./startup.sh python -m scripts.custom_chart --series UNRATE DCOILWTICO --start 2000-01-01 --end 2020-12-31
-  ```
+* **Do not** follow a `./startup.sh` invocation by running `python scripts/<script>.py` on the next line. The `startup.sh` wrapper already executed the module; any additional direct invocation will fail because Python will not find the `scripts` package in that context.
 
 * **Never** call `refresh_data.py` from within a Task Command. This environment has **no internet access**, so attempts to fetch external data will fail. Data in `data/fred.db` must already be present. If you need to refresh data, run it only in an internet-connected shell: